public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Gibbons <jim@gibbons.com>
To: linux-kernel@vger.kernel.org
Subject: request for ioctl range for private devices
Date: Fri, 15 Sep 2006 16:05:35 -0700	[thread overview]
Message-ID: <450B31BF.4050604@gibbons.com> (raw)

I'm involved in the construction of a Linux based device that needs to 
use ioctl's to communicate between its kernel module and its daemons.  
The device is an embedded product.  We should never have any need to 
distribute this driver interface.

I would like to use an ioctl range that would be safe, now and in the 
future.  Given that we won't be putting this driver on any general 
computing platforms, it seems inappropriate to reserve an ioctl range 
for this device.

I would really like to use an ioctl range that is reserved for the class 
of private embedded devices.  That way, I could be sure that I would 
never conflict with any peripheral that we might use without a 
reservation specific to our device.

Would you consider reserving space for such ioctl's?

p.s. I am not a kernel developer and hence not a member of this mailing 
list.  Please cc me on any replies.

p.p.s. I first sent this request to Michael Chastain, who remains listed 
in Documentation/ioctl-number.txt.  He replied that he is no longer 
involved and referred me to this e-mail list.  Perhaps that document 
should be updated.



             reply	other threads:[~2006-09-15 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 23:05 Jim Gibbons [this message]
2006-09-16  0:26 ` request for ioctl range for private devices Miguel Ojeda
2006-09-16  0:43   ` Jim Gibbons
2006-09-16  1:01     ` Miguel Ojeda
2006-09-16  4:44     ` Stephen Hemminger
2006-09-16 15:40       ` Lee Revell

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=450B31BF.4050604@gibbons.com \
    --to=jim@gibbons.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox