From: Johannes Berg <johannes@sipsolutions•net>
To: linuxppc-dev@ozlabs•org
Subject: i2c-bus@0 twice?
Date: Wed, 15 Mar 2006 19:29:57 +0100 [thread overview]
Message-ID: <1142447397.4670.12.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 402 bytes --]
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?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
next reply other threads:[~2006-03-16 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 18:29 Johannes Berg [this message]
2006-03-16 22:53 ` i2c-bus@0 twice? Michael Ellerman
2006-03-16 23:52 ` Benjamin Herrenschmidt
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=1142447397.4670.12.camel@localhost \
--to=johannes@sipsolutions$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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