From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: i2c-bus@0 twice?
Date: Fri, 17 Mar 2006 10:52:25 +1100 [thread overview]
Message-ID: <1142553145.14988.37.camel@localhost.localdomain> (raw)
In-Reply-To: <1142447397.4670.12.camel@localhost>
On Wed, 2006-03-15 at 19:29 +0100, Johannes Berg wrote:
> johannes@quad:/proc/device-tree/ht@0,f2000000/pci@8/mac-io@7/i2c@18000$ ls
> AAPL,address built-in i2c-bus@0 linux,phandle
> AAPL,address-step compatible interrupt-parent name
> AAPL,i2c-rate device_type interrupts reg
> #address-cells i2c-bus@0 linux,device #size-cells
>
> Somewhat odd that i2c-bus@0 exists twice :) Anyone have an explanation?
It's a bug in OF on these machines. We need to workaround that,
especially since only one of them contains all the useful infos
Ben
prev parent reply other threads:[~2006-03-16 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 18:29 i2c-bus@0 twice? Johannes Berg
2006-03-16 22:53 ` Michael Ellerman
2006-03-16 23:52 ` Benjamin Herrenschmidt [this message]
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=1142553145.14988.37.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--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).