From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] gadget uevents not detected by udevmonitor
Date: Thu, 18 Sep 2008 00:58:49 +1000 [thread overview]
Message-ID: <20080917145848.GA28475@cloud.net.au> (raw)
In-Reply-To: <2590773a0809131833r4fc274f0x43a442201b456200@mail.gmail.com>
On Sat, Sep 13, 2008 at 09:33:32PM -0400, Christopher Taylor wrote:
> I'e configured hotplug and netlink sockets in my kernel 2.6.24 config file
> and I've insmoded g_serial. When I run udevmonitor I'm not seeing uevents
> when I plug in the usb cable to the usb device port. I am however getting
> the gadget serial messages:
> gs_disconnect: Gadget Serial disconnected
> gs_setup_complete: status error, status=0, actual-16, length=18
> gs_disconnect: Gadget Serial disconnected
> gs_set_config: gadget Serial configured, full speec CDC-ACM config
>
> I'm 100% sure this is an error on my part when building everything, but I'm
> not sure where.
>
> My whole intent here is to get uevents into my application via a netlink
> socket. I have no intent of running udev, but I do intent on listening on
> that the netlink socket just like udev does so I can tell immediately when a
> usb event occurs.
Are you sure that the kernel even generates such events? My experience
with the gadget subsystem is that it doesn't really integrate much with
the rest of the system.
I don't think buildroot can influence this.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-09-17 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 1:33 [Buildroot] gadget uevents not detected by udevmonitor Christopher Taylor
2008-09-17 14:58 ` Hamish Moffatt [this message]
2008-09-17 15:23 ` Christopher Taylor
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=20080917145848.GA28475@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.