From: Johannes Erdfelt <johannes@erdfelt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Libusb-devel] udev craze: need /dev/bus/usb rationale
Date: Tue, 07 Feb 2006 00:00:19 +0000 [thread overview]
Message-ID: <20060207000019.GP24785@sventech.com> (raw)
In-Reply-To: <20060126094517.GA4063@bode.aurel32.net>
On Mon, Feb 06, 2006, Greg KH <greg@kroah.com> wrote:
> On Mon, Feb 06, 2006 at 03:29:41PM -0800, Johannes Erdfelt wrote:
> > I'm working on implementing inotify support into libusb 1.0 right now.
>
> Does usbfs support inotify events? For some reason I didn't think it
> did, but I'm probably wrong...
Well, it looks like it's trying to, but it's broken:
belushi:..otify-utils-0.25% ./inotify_test /proc/bus/usb/002
inotify device fd = 3
/proc/bus/usb/002 WD=1
read = 32
sizeof inotify_event = 16
pevent->len = 16
EVENT ON WD=1
DELETE (file) 0x00000200
FILENAME\x024
read = 32
sizeof inotify_event = 16
pevent->len = 16
EVENT ON WD=1
DELETE (file) 0x00000200
FILENAME\x025
That was an unplug followed by a replug. This was with my test Keyspan
serial device so there was a reset after the firmware was loaded. It
looks like we're only receiving DELETE events, and no CREATE ones.
It works correctly in /dev/bus/usb (which doesn't seem to create a
device node when it loads firmware):
belushi:..otify-utils-0.25% ./inotify_test /dev/bus/usb/2
inotify device fd = 3
/dev/bus/usb/2 WD=1
read = 32
sizeof inotify_event = 16
pevent->len = 16
EVENT ON WD=1
DELETE (file) 0x00000200
FILENAME&
read = 32
sizeof inotify_event = 16
pevent->len = 16
EVENT ON WD=1
CREATE (file) 0x00000100
FILENAME(
I had planned on using the old method of polling on
/proc/bus/usb/devices for systems we use /proc/bus/usb anyway.
JE
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&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
next prev parent reply other threads:[~2006-02-07 0:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 9:45 [Libusb-devel] udev craze: need /dev/bus/usb rationale Aurelien Jarno
2006-01-26 10:16 ` Linus Walleij
2006-01-27 2:08 ` Johannes Erdfelt
2006-01-27 2:17 ` Kay Sievers
2006-01-27 2:25 ` Greg KH
2006-01-27 2:26 ` Johannes Erdfelt
2006-01-27 3:01 ` Kay Sievers
2006-01-27 3:17 ` Greg KH
2006-01-27 3:38 ` Charles Lepple
2006-01-27 3:51 ` Kay Sievers
2006-01-27 3:53 ` Kay Sievers
2006-01-27 4:01 ` Andrey Borzenkov
2006-01-27 4:05 ` Andrey Borzenkov
2006-01-27 4:11 ` Kay Sievers
2006-01-27 4:20 ` Greg KH
2006-01-27 4:21 ` Greg KH
2006-01-27 4:23 ` Greg KH
2006-01-27 7:50 ` Linus Walleij
2006-01-27 11:56 ` Olivier Blin
2006-01-27 17:04 ` David Zeuthen
2006-01-27 17:15 ` Olivier Blin
2006-01-27 17:28 ` Darren Salt
2006-01-27 17:33 ` Bill Nottingham
2006-01-27 19:29 ` Johannes Erdfelt
2006-01-27 19:39 ` Linus Walleij
2006-01-27 19:44 ` Johannes Erdfelt
2006-01-27 20:45 ` Greg KH
2006-01-28 0:12 ` Greg KH
2006-02-06 23:29 ` Johannes Erdfelt
2006-02-06 23:53 ` Greg KH
2006-02-07 0:00 ` Johannes Erdfelt [this message]
2006-02-07 0:23 ` Greg KH
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=20060207000019.GP24785@sventech.com \
--to=johannes@erdfelt.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).