Re: request for ioctl range for private devices

[Lee Revell <rlrevell@joe-job.com>]

On Sat, 2006-09-16 at 13:44 +0900, Stephen Hemminger wrote:
> On Fri, 15 Sep 2006 17:43:56 -0700
> Jim Gibbons <jim@gibbons.com> wrote:
> 
> > I can see that I wasn't as clear as I should have been.  Thank you for 
> > trying to figure it out anyway.
> > 
> > Please let me try again to explain.  We are using a driver interface to 
> > our kernel level code.  Our kernel level code is a loadable module.  We 
> > have no intention of modifying the kernel or of releasing our code.  We 
> > accept the implied maintenance responsibility on this private, embedded 
> > platform.
> 
> Then why should the main kernel developers do anything to help you
> with your private effort?

I think the request is valid, even for those planning to comply with the
GPL.  I'm working on an embedded device that has a similar requirement.
The code will not be submitted upstream, as the hardware is customized,
but of course we will provide driver sources to those who buy the
hardware as the GPL requires.  It would be useful to have a private
ioctl range for this.  And please don't tell me not to use an ioctl()
interface - it's the simplest way to communicate between kernel and
userspace, and since the code is not going upstream it's our choice.

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/