From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb scanner configuration: udev
Date: Mon, 10 Jan 2005 16:50:51 +0000 [thread overview]
Message-ID: <20050110165051.GA10347@kroah.com> (raw)
In-Reply-To: <1105374433.5028.313.camel@localhost.localdomain>
On Mon, Jan 10, 2005 at 08:27:14AM -0800, Thomas Frayne wrote:
> My problem looks similar to the one described in the the No Hotplug Events thread.
>
> I am running on an up to date Fedora Core 3 system, and have installed
> sane-backends 1.0.15-1.4 and xsane 0.92-13 via synaptic. Over the last
> 18 months, I have periodically tried to get my HP 7450C scanner working
> under SANE, but was never completely successful. This time I succeeded.
>
> Now I find that /dev/scanner-usb-:proc:bus:usb:002:010 is a link to
> /proc/bus/usb/002/010, but the device name changes when I reboot.
usb scanners do not have a /dev entry, as they use libusb to access the
device directly through usbfs in userspace. That is why no udev hotplug
event happens. I do not know what program created that /dev link, but
it wasn't udev.
I suggest bringing this up on the SANE mailing lists, as there's nothing
we can do here.
Good luck,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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
prev parent reply other threads:[~2005-01-10 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 16:27 usb scanner configuration: udev Thomas Frayne
2005-01-10 16:50 ` 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=20050110165051.GA10347@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).