All of lore.kernel.org
 help / color / mirror / Atom feed
From: js@convergence.de (Johannes Stezenbach)
To: Greg KH <greg@kroah.com>
Cc: sensors@stimpy.netroedge.com, linux-kernel@vger.kernel.org
Subject: 2.6.0-test11: i2c-dev.h for userspace
Date: Thu, 19 May 2005 06:24:29 +0000	[thread overview]
Message-ID: <20031212185357.GB32169@convergence.de> (raw)
In-Reply-To: <20031212175656.GA2933@kroah.com>

On Fri, Dec 12, 2003 at 09:56:57AM -0800, Greg KH wrote:
> On Fri, Dec 12, 2003 at 03:56:52PM +0100, Johannes Stezenbach wrote:
> > 
> > I had some trouble compiling a userspace application
> > which uses the I2C device interface (the DirectFB
> > Matrox driver). Apparently some stuff has been removed
> > from i2c-dev.h
> 
> Yes it has.  Do not use the kernel headers in your userspace
> application.  If you need this interface, use the updated i2c-dev.h that
> is in the lmsensors release.  That is the proper file.

I think you create a mess here. Other drivers have usable
API include files in /usr/include/linux, why are i2c.h and i2c-dev.h
special?

While I can understand why the ioctl wrappers have been removed
from the kernel include file i2c-dev.h I fail to see the logic
in having a different i2c-dev.h for userspace, or generally breaking
the kernel includes for userspace.

It seems to me that there is no package that I could install to make
the correct i2c-dev.h available for userspace programs, and the only
way to fix the DirectFB Matrox driver so it compiles with 2.4 and
2.6 kernel headers is to copy the correct i2c-dev.h into the
DirectFB source tree.

I think that sucks.


Johannes

WARNING: multiple messages have this Message-ID (diff)
From: Johannes Stezenbach <js@convergence.de>
To: Greg KH <greg@kroah.com>
Cc: sensors@stimpy.netroedge.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11: i2c-dev.h for userspace
Date: Fri, 12 Dec 2003 19:53:57 +0100	[thread overview]
Message-ID: <20031212185357.GB32169@convergence.de> (raw)
In-Reply-To: <20031212175656.GA2933@kroah.com>

On Fri, Dec 12, 2003 at 09:56:57AM -0800, Greg KH wrote:
> On Fri, Dec 12, 2003 at 03:56:52PM +0100, Johannes Stezenbach wrote:
> > 
> > I had some trouble compiling a userspace application
> > which uses the I2C device interface (the DirectFB
> > Matrox driver). Apparently some stuff has been removed
> > from i2c-dev.h
> 
> Yes it has.  Do not use the kernel headers in your userspace
> application.  If you need this interface, use the updated i2c-dev.h that
> is in the lmsensors release.  That is the proper file.

I think you create a mess here. Other drivers have usable
API include files in /usr/include/linux, why are i2c.h and i2c-dev.h
special?

While I can understand why the ioctl wrappers have been removed
from the kernel include file i2c-dev.h I fail to see the logic
in having a different i2c-dev.h for userspace, or generally breaking
the kernel includes for userspace.

It seems to me that there is no package that I could install to make
the correct i2c-dev.h available for userspace programs, and the only
way to fix the DirectFB Matrox driver so it compiles with 2.4 and
2.6 kernel headers is to copy the correct i2c-dev.h into the
DirectFB source tree.

I think that sucks.


Johannes

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 14:56 2.6.0-test11: i2c-dev.h for userspace Johannes Stezenbach
2005-05-19  6:24 ` Johannes Stezenbach
2003-12-12 17:56 ` Greg KH
2005-05-19  6:24   ` Greg KH
2003-12-12 18:53   ` Johannes Stezenbach [this message]
2005-05-19  6:24     ` Johannes Stezenbach
2003-12-12 19:01     ` Greg KH
2005-05-19  6:24       ` Greg KH
2003-12-12 19:21       ` Johannes Stezenbach
2005-05-19  6:24         ` Johannes Stezenbach
2003-12-12 19:45         ` Greg KH
2005-05-19  6:24           ` Greg KH
2003-12-14  1:57       ` bill davidsen

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=20031212185357.GB32169@convergence.de \
    --to=js@convergence.de \
    --cc=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 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.