netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Dan Williams <dcbw@redhat.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 13:20:43 -0700	[thread overview]
Message-ID: <49BEB49B.8090602@candelatech.com> (raw)
In-Reply-To: <1237234322.16956.88.camel@localhost.localdomain>

Dan Williams wrote:

>> 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?

No, but figuring out the problem from a customer's bug report ("nothing works")
and then finding the firmware and having the customer install it will be much
worse than just having everything work like it used to.

I just see zero benefits to having external firmware
for the vast majority of end-users, and lots of downside
for at least myself.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


------------------------------------------------------------------------------
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:20 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
2009-03-16 20:20           ` Ben Greear [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=49BEB49B.8090602@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=bhutchings@solarflare.com \
    --cc=dcbw@redhat.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).