From: Brad House <brad@mainstreetsoftworks.com>
To: buildroot@busybox.net
Subject: [Buildroot] Allowing hotplug and udev in the same root fs???
Date: Thu, 16 Aug 2007 09:03:09 -0400 [thread overview]
Message-ID: <46C44B0D.7040507@mainstreetsoftworks.com> (raw)
In-Reply-To: <1187220251.2429.2.camel@elrond.sweden.atmel.com>
Hmm, I thought udev and hotplug worked together. Thought it
was something along the lines that hotplug would do the triggering
of driver module loading based on what new pci/usb ids showed up
on the system, since udev doesn't actually perform module loading
afaik. Hotplug is/was also responsible for firmware loading, but
I'm not sure if that is true anymore ...
Truthfully, I can't provide much to this discussion as I haven't
really bothered to look into it for a while...
-Brad
Ulf Samuelsson wrote:
> Does it make sense to allow both Hotplug and udev?
> Is it not so that you either have hotplug (real old...) or udev?
>
> The following then would make sense.
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Index: package/hotplug/Config.in
> ===================================================================
> --- package/hotplug/Config.in (revision 19502)
> +++ package/hotplug/Config.in (arbetskopia)
> @@ -1,6 +1,7 @@
> config BR2_PACKAGE_HOTPLUG
> bool "hotplug"
> default n
> + depends on !BR2_PACKAGE_UDEV
> help
> Plug in new devices and use them immediately.
>
> -------------------------------------------------------------------
>
> Comments ?
>
> BR
> Ulf Samuelsson
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
prev parent reply other threads:[~2007-08-16 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 23:24 [Buildroot] Allowing hotplug and udev in the same root fs??? Ulf Samuelsson
2007-08-16 13:03 ` Brad House [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=46C44B0D.7040507@mainstreetsoftworks.com \
--to=brad@mainstreetsoftworks.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