linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#294123: udev: Bad parsing of regular expressions in *.rules
Date: Mon, 14 Feb 2005 18:31:00 +0000	[thread overview]
Message-ID: <20050214183100.GC7815@kroah.com> (raw)
In-Reply-To: <20050208090725.GB7706@wonderland.linux.it>

On Mon, Feb 14, 2005 at 07:22:08PM +0100, Kay Sievers wrote:
> On Mon, 2005-02-14 at 09:30 -0800, Greg KH wrote:
> >> 
> >> Ahh, I see. So we may follow the link to the physical device and look
> >> for the name of the _first_ serial interface of this device? Would this
> >> solve the problem?
> >
> >Heh, not quite, as you usually want the _second_ serial interface to
> >sync off of, the first one is not useful at all (well, some tools use
> >it, but 99% of the users never will care about it.)
> >
> >And then there's the fun problem of some Sony devices creating two
> >serial "devices" where the second one is just a "fake" one, and you
> >really need to connect to the first.
> >
> >Bah, sometimes I really hate Palm...
> 
> Yeah, I can imagine that. But would it be possible to get the right one
> with the information available in sysfs? Someone could write a small
> script which matches the vendor and return a symlink for the _right_
> interface. Would that work?

Yes, if the visor driver exported the type of the port that it was in
sysfs (which it does not do right now, never got around to it as my
visor is broken...)  If anyone wants to take a look into doing this,
look at the logic in the drivers/usb/serial/visor.c::palm_os_3_probe()
function where it determines the port_function_id type.  We should
export that info to sysfs, for the os versions that support it.  For
palm os 4 and greater, I don't know how to get that information, sorry.

> Btw: The "Bad parsing ..." wasn't a udev issue. It's solved.

Yeah, I think I saw that go by in a bug report.  Huge backlog of email
today, that's what I get for being sick for 3 days...

thanks,

greg k-h


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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:[~2005-02-14 18:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  9:07 Bug#294123: udev: Bad parsing of regular expressions in *.rules Marco d'Itri
2005-02-08 17:00 ` Marco d'Itri
2005-02-09  2:24 ` Kay Sievers
2005-02-09  5:53 ` Greg KH
2005-02-12 12:28 ` Marco d'Itri
2005-02-13  3:14 ` Kay Sievers
2005-02-14 17:30 ` Greg KH
2005-02-14 18:22 ` Kay Sievers
2005-02-14 18:31 ` 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=20050214183100.GC7815@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).