From: Michael Ellerman <michaelellerman@internode.on.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] PowerMac11,2 i2c-bus@0 duplicate dev-tree workaround
Date: Thu, 30 Mar 2006 17:28:39 +1100 [thread overview]
Message-ID: <1143700119.23392.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1143631816.9481.5.camel@localhost>
On Wed, 2006-03-29 at 13:30 +0200, Johannes Berg wrote:
> On a PowerMac11,2, there are two i2c-bus@0 nodes of which only the first
> is correct. This patch makes the device tree unflattening code ignore
> the second one on those machines.
>
> Signed-Off-By: Johannes Berg <johannes@sipsolutions.net>
>
> ---
> I'm not sure this is the right way to do it. Maybe we should have some
> 'dev-tree quirks fixer' that makes a third pass through the device tree
> after the allnodes chain has been set up, and fixes it up. On the other
> hand, as long as there aren't too many workarounds, this works fine.
>
> The patch looks longer than it is because some code changed indentation
> level.
I don't understand why we need this patch? If we care about getting the
"right" node why not check for that where we care?
cheers
--
Michael Ellerman
IBM OzLabs
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
next prev parent reply other threads:[~2006-03-30 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 11:30 [PATCH] PowerMac11,2 i2c-bus@0 duplicate dev-tree workaround Johannes Berg
2006-03-30 4:26 ` Benjamin Herrenschmidt
2006-03-30 13:04 ` Johannes Berg
2006-03-30 6:28 ` Michael Ellerman [this message]
2006-03-30 22:38 ` Johannes Berg
2006-03-31 5:37 ` Michael Ellerman
2006-03-31 9:42 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1143700119.23392.27.camel@localhost.localdomain \
--to=michaelellerman@internode.on.net \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).