netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
	NetDev <netdev@vger.kernel.org>,
	dwmw2@infradead.org, "Brandeburg,
	Jesse" <jesse.brandeburg@intel.com>,
	e1000-devel@lists.sourceforge.net
Subject: Re: e100 firmware in 2.6.29-rc7?
Date: Mon, 16 Mar 2009 16:12:02 -0400	[thread overview]
Message-ID: <1237234322.16956.88.camel@localhost.localdomain> (raw)
In-Reply-To: <49BEB115.4050303@candelatech.com>

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



------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com

  reply	other threads:[~2009-03-16 20:12 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
2009-03-16 20:12         ` Dan Williams [this message]
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=1237234322.16956.88.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=bhutchings@solarflare.com \
    --cc=dwmw2@infradead.org \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=greearb@candelatech.com \
    --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).