mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Willy Tarreau <w@1wt.eu>
Cc: David Miller <davem@davemloft.net>,
	albcamus@gmail.com, chris@arachsys.com, mchan@broadcom.com,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] bnx2: update bnx2-mips-09 firmware to bnx2-mips-09-6.2.1b
Date: Wed, 08 Aug 2012 09:00:23 +0200	[thread overview]
Message-ID: <1344409223.28967.217.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120808064959.GB15255@1wt.eu>

On Wed, 2012-08-08 at 08:49 +0200, Willy Tarreau wrote:
> Hi Eric,
> 
> On Wed, Aug 08, 2012 at 08:27:52AM +0200, Eric Dumazet wrote:
> > On Wed, 2012-08-08 at 08:17 +0200, Willy Tarreau wrote:
> > 
> > > 
> > > Well, if the drivers provided with the kernel don't work out of the box
> > > anymore, maybe we should also move them to a separate repository. All it
> > > is going to do otherwise is to cause invalid bug reports because users
> > > don't understand why using the latest driver does not work.
> > > 
> > > That way it would be clear that an in-kernel driver has to be self-sustaining
> > > to be maintainable, otherwise it has nothing to do there.
> > 
> > People compiling their own kernels are supposed to be able to handle
> > this problem themselves.
> > 
> > If not, they can use a distro.
> 
> But similarly, people who compile their own kernels are also supposed to
> be able to retrieve up-to-date drivers from another tree. I know many
> people who use the intel NIC drivers from sf.net and (less) other ones
> using myricom's drivers for instance.
> 
> I don't really see the value of keeping in the tree drivers that don't
> work out of the box, if it's only causing issues and bug reports.

Only the firmware is in a separate git tree, called linux-firmware, that
about all kernel developers are aware of.

The drivers themselves are in linux tree, and they are generally in
quite good shape, because of that.




      reply	other threads:[~2012-08-08  7:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 13:04 Chris Webb
2012-07-13 13:42 ` Eric Dumazet
2012-07-13 14:09   ` Chris Webb
2012-07-13 21:12     ` Michael Chan
2012-07-14  4:27     ` Ben Hutchings
2012-08-08  5:50 ` Jike Song
2012-08-08  5:58   ` David Miller
2012-08-08  6:17     ` Willy Tarreau
2012-08-08  6:27       ` Eric Dumazet
2012-08-08  6:49         ` Willy Tarreau
2012-08-08  7:00           ` Eric Dumazet [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=1344409223.28967.217.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=albcamus@gmail.com \
    --cc=chris@arachsys.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchan@broadcom.com \
    --cc=stable@vger.kernel.org \
    --cc=w@1wt.eu \
    /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

all inboxes | Powered by JetHome®