linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moshe Yudkowsky <msha5_17@bl.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: USB camera not hotplugging because  SYSFS{ID_VENDOR} etc. not
Date: Mon, 10 Apr 2006 19:02:52 +0000	[thread overview]
Message-ID: <443AABDC.6050106@bl.com> (raw)
In-Reply-To: <443A76D5.60208@bl.com>

Andrey,

Thanks for responding.

Andrey Borzenkov wrote:

>> libgphoto2.rules:
>>> SYSFS{idVendor}="04a9", SYSFS{idProduct}="3051", MODE="0660",
>>> GROUP="camera"
> 
> If this is full rule it won't work.

That's the full rule. I'm pretty sure it used to work.

I wrote:
>>  I don't have SYSFS{ID_VENDOR} available when
>> > the device is plugged in. 

You wrote:

> This does not exist and has never existed.

But I see from udevmonitor --env that:

> ID_VENDOR=iriver
> ID_MODEL=MassStorage_Disc
> ID_REVISION\001
> ID_SERIAL=iriver_MassStorage_Disc
> ID_TYPE=disk
> ID_BUS=usb

And the rule

> SUBSYSTEM="block", ACTION="add", ENV{ID_VENDOR}="iriver", ENV{ID_SERIAL}="iriver_MassStorage_Disc", SYMLINK+="iriver", RUN+="/etc/hotplug/usb/iriver",
> ENV{REMOVE_CMD}="/etc/hotplug/usb/iriver remove"

does work as expected.

Oh, I see. One's ENV and the other is SYSFS. As always, it's impossible 
to tell from the printout if you don't know the SYSFS variables by heart.

And, for the record, I suspect that ID_VENDOR got into the environment 
via a usb_id() function call -- am I correct?

For the camera, I get

> PRODUCTJ9/3051/1 

And inside the rule for the camera I see SYSFS{idVendor}="04a9", 
SYSFS{idProduct}="3051". It looks to me as if they are very similar. 
Has there been a recent change of some sort in udev that made idVendor 
stop working? Or did this never work, and I am remembering wrong, and 
it's time to write ghoto2 and ask them to update their rules?

-- 
  Moshe Yudkowsky
  work: http://www.Disaggregate.com
  book: http://www.PebbleAndAvalanche.com


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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:[~2006-04-10 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 15:16 USB camera not hotplugging because SYSFS{ID_VENDOR} etc. not available Moshe Yudkowsky
2006-04-10 17:02 ` Andrey Borzenkov
2006-04-10 19:02 ` Moshe Yudkowsky [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=443AABDC.6050106@bl.com \
    --to=msha5_17@bl.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).