[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1237234322.16956.88.camel@localhost.localdomain>
Date: Mon, 16 Mar 2009 16:12:02 -0400
From: Dan Williams <dcbw@...hat.com>
To: Ben Greear <greearb@...delatech.com>
Cc: Ben Hutchings <bhutchings@...arflare.com>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
NetDev <netdev@...r.kernel.org>, dwmw2@...radead.org,
e1000-devel@...ts.sourceforge.net
Subject: Re: e100 firmware in 2.6.29-rc7?
On Mon, 2009-03-16 at 13:05 -0700, Ben Greear wrote:
> 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.
Most of those distros will have firmware loading capability though,
right? Every non-embedded distro (Fedora, RHEL, SUSE, Ubuntu,
Slackware, Mandriva, Xandros, etc) has it, so if you're building kernels
for those, there's not really a problem with dropping firmware into the
firmware directory for that distro, right?
Dan
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists