From: Ben Greear <greearb@candelatech.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
NetDev <netdev@vger.kernel.org>,
dwmw2@infradead.org, e1000-devel@lists.sourceforge.net
Subject: Re: e100 firmware in 2.6.29-rc7?
Date: Mon, 16 Mar 2009 13:05:41 -0700 [thread overview]
Message-ID: <49BEB115.4050303@candelatech.com> (raw)
In-Reply-To: <1237231540.3106.9.camel@achroite>
Ben Hutchings wrote:
>> The config & dmesg is attached. Some of the options are for patches we've
>> added, and we even have a small patch in the e100 (but have had it there
>> for years, so probably un-related to this). Still, I will not complain
>> if you decide to ignore the report.
> [...]
>
> Your config has CONFIG_E100=m, but CONFIG_FIRMWARE_IN_KERNEL only
> applies to firmware used by non-modular drivers. The assumption is that
> once userland is capable of loading modules it is also capable of
> loading firmware.
Well, that's an annoyance. Would it be that hard to allow modular drivers
to compile-in their FW as well? It would be a nice option for
those of us trying to build portable pre-compiled kernels for various
distributions and distribution versions.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2009-03-16 20:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 20:16 e100 firmware in 2.6.29-rc7? Ben Greear
2009-03-16 18:47 ` Brandeburg, Jesse
2009-03-16 19:13 ` Ben Greear
2009-03-16 19:25 ` Ben Hutchings
2009-03-16 20:05 ` Ben Greear [this message]
2009-03-16 20:12 ` Dan Williams
2009-03-16 20:20 ` Ben Greear
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=49BEB115.4050303@candelatech.com \
--to=greearb@candelatech.com \
--cc=bhutchings@solarflare.com \
--cc=dwmw2@infradead.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@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).