Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Taylor <chtaylo3@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] efficient usb plug in notification
Date: Wed, 6 Aug 2008 11:10:01 -0400	[thread overview]
Message-ID: <2590773a0808060810o7c07b114ude1a67ed8745dd41@mail.gmail.com> (raw)

I'm trying to see what my best options are of getting USB plugin
notifications in user-space in a buildroot/uClibc env.

Since this is an embedded platform, I'm really concerned about
efficiency of the mechanisms and I'm not sure how efficient udev +
dbus + hal is. Does anyone have any thoughts on this and what some
reasonable alternatives are within the buildroot chain?

-Chris

             reply	other threads:[~2008-08-06 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 15:10 Christopher Taylor [this message]
2008-08-06 15:18 ` [Buildroot] efficient usb plug in notification sjhill at realitydiluted.com
2008-08-07  3:23   ` Christopher Taylor
2008-08-07  7:44 ` Hinko Kocevar
  -- strict thread matches above, loose matches on Subject: below --
2008-08-06 17:19 shaleh at speakeasy.net
2008-08-07  3:26 ` Christopher Taylor
2008-08-08  2:04   ` Sean Perry

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=2590773a0808060810o7c07b114ude1a67ed8745dd41@mail.gmail.com \
    --to=chtaylo3@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox