linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Steinert <hachi@kuiki.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: How can I specify a specific 'sub-device' of a device for udev
Date: Thu, 04 Mar 2004 07:19:04 +0000	[thread overview]
Message-ID: <4046D868.6040600@kuiki.net> (raw)
In-Reply-To: <4042D36F.9020909@kuiki.net>

Kay Sievers wrote:

>On Mon, Mar 01, 2004 at 10:23:40AM -0600, Jonathan Steinert wrote:
>  
>
>>Sure, but matching this usb device does not yield me a tty.
>>    
>>
>
>What do you get instead?
>
>I took a look on your 'tree' and it has only one interface.
>So, if you match with the SYSFS{serial}="304087" there should still
>the tty be created.
>Matching any device along the chain of your "node-device" with a rule,
>will still create only the "node-device", nothing else.
>
>Maybe I'm a bit confused and if I get the subject completly wrong
>please tell me :)
>
>Kay
>  
>

Right, I'll admit defeat there... I asumed the wrong things about udev 
and ended up burning myself on that one.

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?

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.

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.

Thanks a ton for helping me out with the usb-serial device too.

--Jonathan Steinert


-------------------------------------------------------
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

  parent reply	other threads:[~2004-03-04  7:19 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 ` Jonathan Steinert [this message]
2004-03-04 19:53 ` Greg KH

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=4046D868.6040600@kuiki.net \
    --to=hachi@kuiki.net \
    --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).