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 18:49:58 +0000 [thread overview]
Message-ID: <1228330198l.20654l.7l@mofo> (raw)
In-Reply-To: <bed87e0b812045212a08a0c9ef4a06b2.squirrel@kone.netland.fin>
On 12/03/2008 11:37:10 AM, Kay Sievers wrote:
> On Wed, Dec 3, 2008 at 18:06, Karl O. Pinc <kop@meme.com> wrote:
> > 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:
> >> 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 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.
>
> Did you copy the in the earlier mail attached file to
> /etc/udev/rules.d/, and diconnect/reconnect the device? Only this
> would create the /dev/serial/ stuff.
No. Now I have and it does not seem to work,
but then I don't see the ttyUSB devices either.
I'm thinking that my kernel does not yet have
support and I need something newer. (I know
I got ttyUSB devices created the last time
I tested the device....)
I'm sorry, I have to stop now. I will try
to report back in a few days. I hope I've
not distracted you too much.
I tried udevtest and didn't get any parse errors.
> >
> > Debian etch
> > Linux 2.6.18-6-686
> > udev 0.105-4
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 18:49 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
2008-12-03 17:37 ` Kay Sievers
2008-12-03 18:49 ` Karl O. Pinc [this message]
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=1228330198l.20654l.7l@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).