From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [PATCH] I2C fixes for 2.6.10-rc1
Date: Fri, 12 Nov 2004 15:26:45 -0800 [thread overview]
Message-ID: <11003020054093@kroah.com> (raw)
In-Reply-To: <20041112232604.GA17203@kroah.com>
ChangeSet 1.2093, 2004/11/12 11:39:51-08:00, greg@kroah.com
I2C: fix up some out of date Documentation
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
Documentation/i2c/dev-interface | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -Nru a/Documentation/i2c/dev-interface b/Documentation/i2c/dev-interface
--- a/Documentation/i2c/dev-interface 2004-11-12 15:22:53 -08:00
+++ b/Documentation/i2c/dev-interface 2004-11-12 15:22:53 -08:00
@@ -3,7 +3,7 @@
the /dev interface. You need to load module i2c-dev for this.
Each registered i2c adapter gets a number, counting from 0. You can
-examine /proc/bus/i2c to see what number corresponds to which adapter.
+examine /sys/class/i2c-dev/ to see what number corresponds to which adapter.
I2C device files are character device files with major device number 89
and a minor device number corresponding to the number assigned as
explained above. They should be called "i2c-%d" (i2c-0, i2c-1, ...,
@@ -19,7 +19,7 @@
knows about i2c, there is not much choice.
Now, you have to decide which adapter you want to access. You should
-inspect /proc/bus/i2c to decide this. Adapter numbers are assigned
+inspect /sys/class/i2c-dev/ to decide this. Adapter numbers are assigned
somewhat dynamically, so you can not even assume /dev/i2c-0 is the
first adapter.
next prev parent reply other threads:[~2004-11-12 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 23:26 [BK PATCH] " Greg KH
2004-11-12 23:26 ` Greg KH [this message]
2004-11-12 23:26 ` [PATCH] " Greg KH
2004-11-12 23:26 ` Greg KH
2004-11-12 23:26 ` Greg KH
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=11003020054093@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
/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
Powered by JetHome