From: Marcel Holtmann <marcel@holtmann.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Firmware loading depends on hotplug support
Date: 01 Sep 2003 18:59:15 +0200 [thread overview]
Message-ID: <1062435561.30892.193.camel@pegasus> (raw)
In-Reply-To: <20030901163505.GA27754@ip68-0-152-218.tc.ph.cox.net>
Hi Tom,
> > [PATCH] Firmware loading depends on hotplug support
> >
> > This patch makes the firmware loading support only selectable if the
> > hotplug support is also enabled.
> >
> >
> > # This patch includes the following deltas:
> > # ChangeSet 1.1065.2.2 -> 1.1065.2.3
> > # lib/Config.in 1.4 -> 1.5
> > #
> >
> > Config.in | 3 ++-
> > 1 files changed, 2 insertions(+), 1 deletion(-)
> >
> >
> > diff -Nru a/lib/Config.in b/lib/Config.in
> > --- a/lib/Config.in Mon Sep 1 08:02:24 2003
> > +++ b/lib/Config.in Mon Sep 1 08:02:24 2003
> > @@ -41,7 +41,8 @@
> > fi
> > fi
> >
> > -if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then
> > +if [ "$CONFIG_EXPERIMENTAL" = "y" -a \
> > + "$CONFIG_HOTPLUG" = "y" ]; then
> > tristate 'Hotplug firmware loading support (EXPERIMENTAL)' CONFIG_FW_LOADER
> > fi
>
> Is this really a good idea, given that USB devices may be hot-plugged,
> without CONFIG_HOTPLUG set (drivers are compiled in, for example) ?
this option is only provided for drivers outside the kernel. If a driver
inside the kernel needs it, it is selected automaticly like the CRC32
routines.
If you disable hotplug support the request_firmware() routine will
return an error and this must be handled by the driver.
Regards
Marcel
prev parent reply other threads:[~2003-09-01 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200309011502.h81F2Mq6003467@hera.kernel.org>
2003-09-01 16:35 ` [PATCH] Firmware loading depends on hotplug support Tom Rini
2003-09-01 16:59 ` Marcel Holtmann [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=1062435561.30892.193.camel@pegasus \
--to=marcel@holtmann.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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