From: "Karl O. Pinc" <kop@meme.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Udev rule for HSDPA modem
Date: Wed, 03 Dec 2008 17:06:12 +0000 [thread overview]
Message-ID: <1228323972l.20654l.2l@mofo> (raw)
In-Reply-To: <bed87e0b812045212a08a0c9ef4a06b2.squirrel@kone.netland.fin>
On 12/03/2008 09:11:29 AM, Kay Sievers wrote:
> On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
> > On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org>
> wrote:
> > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
> > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
> > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
> > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> > >>> >> Greg KH wrote:
> > Ok, I found one. You mean "port_number", right? But unfortunately it
> > looks pretty useless in this case. :)
> >
> > $ grep . /sys/bus/usb-serial/devices/*/port_number
> > /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
> > /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
> >
> > They would only be not "0" if the serial lines would be on the same
> > usb interface?
> >
> > We would need a per-device enumeration, but that's nothing the
> > usb-serial stuff knows/cares about if we have different usb
> > interfaces, right?
>
> Greg, do you have a usb multi-port serial card? Can you possibly give
> this a try, and show us "tree /dev/serial"?
I've been following this thread, and don't fully understand it
but have what may be a related problem. I'll describe it here
just so that you can keep it in mind in case it's relevant
or if you want some information on my device.
I put my problem on hold some months ago and will eventually
get back to it.
I've a Digi Edgeport 4/16. It's got 16 serial ports.
It's been a while and I don't really know what I'm doing
with udev but as I recall the device
has an internal USB hub and the kernel seems to discover the
different "plugs" on the "hub" in a different order at various times.
(There's either 2 or 4 serial ports on each internal "endpoint",
I forget.)
Hence, there's no persistent correspondence between physical
serial port and /dev device. I tried writing some udev rules
akin to the persistent rule generation for network devices,
posted the results here, and got what seemed to be better
ideas back I've not followed up on.
Anyhow, I tried "tree /dev/serial/" to post the results
here and there is no /dev/serial. Let me know if you'd
like some other information on the device.
Debian etch
Linux 2.6.18-6-686
udev 0.105-4
Regards,
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
next prev parent reply other threads:[~2008-12-03 17:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 17:56 Udev rule for HSDPA modem Jar
2008-11-28 18:51 ` Greg KH
2008-11-29 8:00 ` Jar
2008-11-29 17:37 ` Greg KH
2008-11-30 5:21 ` Kay Sievers
2008-12-03 6:45 ` Greg KH
2008-12-03 9:27 ` Kay Sievers
2008-12-03 12:12 ` Kay Sievers
2008-12-03 15:11 ` Kay Sievers
2008-12-03 17:06 ` Karl O. Pinc [this message]
2008-12-03 17:37 ` Kay Sievers
2008-12-03 18:49 ` Karl O. Pinc
2008-12-03 23:10 ` Greg KH
2008-12-03 23:54 ` Kay Sievers
2008-12-04 0:04 ` Greg KH
2008-12-04 0:12 ` Kay Sievers
2008-12-04 0:40 ` Greg KH
2008-12-04 1:14 ` Kay Sievers
2008-12-04 6:28 ` Jar
2008-12-04 7:23 ` Kay Sievers
2008-12-04 14:22 ` Jar
2008-12-04 15:27 ` Karl O. Pinc
2008-12-04 18:56 ` Greg KH
2008-12-04 19:11 ` Greg KH
2008-12-05 2:53 ` Kay Sievers
2008-12-05 4:54 ` Karl O. Pinc
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=1228323972l.20654l.2l@mofo \
--to=kop@meme.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).