All of lore.kernel.org
 help / color / mirror / Atom feed
From: nroeder@inf.ed.ac.uk (Nils Roeder)
To: lm-sensors@vger.kernel.org
Subject: userspace  dev-interface linux-2.6.7
Date: Thu, 19 May 2005 06:25:57 +0000	[thread overview]
Message-ID: <427F4202.60601@inf.ed.ac.uk> (raw)
In-Reply-To: <42775670.5070709@inf.ed.ac.uk>

hi,

here is an updated version of Documentation/i2c/dev_interface
which just adds that there are two versions of i2c-dev.h
and that the userspace version is distributed with lm_sensors.

   nils
-------------- next part --------------
--- Documentation/i2c/dev-interface.orig	2005-05-09 11:47:22.000000000 +0100
+++ Documentation/i2c/dev-interface	2005-05-09 11:50:18.000000000 +0100
@@ -16,7 +16,9 @@ C example
 So let's say you want to access an i2c adapter from a C program. The
 first thing to do is `#include <linux/i2c.h>" and "#include <linux/i2c-dev.h>. 
 Yes, I know, you should never include kernel header files, but until glibc 
-knows about i2c, there is not much choice.
+knows about i2c, there is not much choice. For this purpose there are two 
+i2c-dev.h files, one for kernel-space and one for user-space. The user-space 
+version of i2c-dev.h is distributed with lm_sensors for historical reasons.
 
 Now, you have to decide which adapter you want to access. You should
 inspect /sys/class/i2c-dev/ to decide this. Adapter numbers are assigned

  parent reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 userspace dev-interface linux-2.6.7 Nils Roeder
2005-05-19  6:25 ` Nils Roeder
2005-05-19  6:25 ` Nils Roeder
2005-05-19  6:25 ` Rudolf Marek
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Nils Roeder
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Nils Roeder [this message]
2005-06-25 11:25 ` [lm-sensors] " Jean Delvare

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=427F4202.60601@inf.ed.ac.uk \
    --to=nroeder@inf.ed.ac.uk \
    --cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.