public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Nizette <bn@niasdigital.com>
To: joakim.tjernlund@transmode.se
Cc: Paul Mundt <lethal@linux-sh.org>,
	"Hans J. Koch" <hjk@linutronix.de>,
	gregkh@suse.de, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: UIO device name
Date: Thu, 25 Sep 2008 08:57:37 +1000	[thread overview]
Message-ID: <1222297057.4037.12.camel@moss.renham> (raw)
In-Reply-To: <1222259894.12624.247.camel@gentoo-jocke.transmode.se>


On Wed, 2008-09-24 at 14:38 +0200, Joakim Tjernlund wrote:
> On Wed, 2008-09-24 at 20:47 +0900, Paul Mundt wrote:
> > > 
> > Nonsense, there is nothing wrong with UIO's interface as it is today.
> > It is no different from sound cards, cdroms, and so on. If you want the
> 
> It is different, cdroms and audio are named differently. If they were
> using UIO they would all be named /dev/uio%d.
> 
> Consider uio_cif and uio_smx, is it impossible to image that such
> devices could use another name such as crypto_smx%d instead?
> 

My system does use uio_smx and uio_pdrv, they both appear as /dev/uioX.
This to me is just like having /dev/hda, /dev/hdb rather
than /dev/myrootpartition, /dev/somebackupspace or whatever.  In this
case you do have a /dev/cdrom symlink but it's just that, a symlink set
up by scripts.  The kernel doesn't (and shouldn't) make that naming
decision for you.

My software just walks /sys/class/uio/uioX/name, finds the one which
matches then opens the corresponding device.  No scripts needed, no
in-kernel hackery or policy making, just the interface used as the maker
intended.  What's your problem with this approach?

The only software you need is the software you have anyway, the stuff
which opens the device also discovers which device to open.

	--Ben.



  reply	other threads:[~2008-09-24 22:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24  9:21 UIO device name Joakim Tjernlund
2008-09-24  9:35 ` Paul Mundt
2008-09-24  9:57   ` Joakim Tjernlund
2008-09-24 10:14     ` Paul Mundt
2008-09-24 10:22     ` Hans J. Koch
2008-09-24 11:33       ` Joakim Tjernlund
2008-09-24 11:47         ` Paul Mundt
2008-09-24 12:38           ` Joakim Tjernlund
2008-09-24 22:57             ` Ben Nizette [this message]
2008-09-25 10:05               ` Joakim Tjernlund
2008-09-25 10:48                 ` Ben Nizette
2008-09-25 11:41                   ` Joakim Tjernlund
2008-09-25 11:53                     ` Paul Mundt
2008-09-25 12:36                       ` Joakim Tjernlund

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=1222297057.4037.12.camel@moss.renham \
    --to=bn@niasdigital.com \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=joakim.tjernlund@transmode.se \
    --cc=lethal@linux-sh.org \
    --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