From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: How can I specify a specific 'sub-device' of a device for udev naming?
Date: Thu, 04 Mar 2004 19:53:42 +0000 [thread overview]
Message-ID: <20040304195342.GA2357@kroah.com> (raw)
In-Reply-To: <4042D36F.9020909@kuiki.net>
On Thu, Mar 04, 2004 at 01:19:04AM -0600, Jonathan Steinert wrote:
>
> However, I'd like to ask... since you (I think) asume that each physical
> device maps to only one node; What will happen when someone wants to
> name multiple devices based on an attribute higher in the than the
> unique branch?
Well, it's a bit hard if you want to do that, isn't it :)
usb to serial devices have the same "issue", as well as many other types
of devices. The trick is in coming up with a unique name rule for those
kinds of devices.
> The first example I came up with is my Griffin iMic (a usb sound card
> dongle) which creates multiple device nodes. The trouble is that I think
> ALSA is supposed to handle this situation and not udev.
>
> The next best example I can think of would be naming USB devices based
> on which hub they are plugged in to. The hub must be identified by some
> sort of serial number or other attribute, but then there may be more
> than one device plugged into that hub.
Well, you can always go on the position of the usb device (plugged into
which port of which hub.) But again, you are back to the "multiple
virtual devices per physical device" issue.
We are a whole lot better off than before, when we could never even
determine this information. It's up to the individual driver writers to
help expose unique information for their devices that can help out in
creating "good enough" rules.
> I'm just throwing this question out to see how it could be solved, so I
> can't give you specific attributes till I build the system I want this for.
There is no "general" solution for this. It's going to be a individual
one as every system ends up being different.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-03-04 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 6:08 How can I specify a specific 'sub-device' of a device for udev naming? Jonathan Steinert
2004-03-01 12:36 ` How can I specify a specific 'sub-device' of a device for udev Kay Sievers
2004-03-01 16:23 ` Jonathan Steinert
2004-03-01 17:00 ` Kay Sievers
2004-03-01 23:56 ` Jonathan Steinert
2004-03-02 0:37 ` How can I specify a specific 'sub-device' of a device for udev naming? Kay Sievers
2004-03-04 7:19 ` How can I specify a specific 'sub-device' of a device for udev Jonathan Steinert
2004-03-04 19:53 ` Greg KH [this message]
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=20040304195342.GA2357@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).