netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
	e1000-devel@lists.soutceforge.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [2.6.29-rc2 regression] e100: netconsole not functional because of missing firmware
Date: Mon, 19 Jan 2009 20:20:34 +0100	[thread overview]
Message-ID: <200901192020.35116.rjw@sisk.pl> (raw)
In-Reply-To: <4807377b0901191030g27efac79rbd39501eb2eea4cb@mail.gmail.com>

On Monday 19 January 2009, Jesse Brandeburg wrote:
> On Sat, Jan 17, 2009 at 8:08 AM, Andrey Borzenkov <arvidjaar@mail.ru> wrote:
> > [    2.008509] e100: eth0: e100_request_firmware: Failed to load
> > firmware "e100/d101m_ucode.bin": -22
> > [    2.010461] netconsole: failed to open eth0
> > [    2.010996] netconsole: cleaning up
> >
> > This has been working all the time without requiring any external
> > firmware to be present. Why it suddenly refuses to work now?
> 
> to use netconsole you probably need to set config option
> CONFIG_FIRMWARE_IN_KERNEL=y
> 
> Hm, I wonder if we couldn't have netconsole=y select
> CONFIG_FIRMWARE_IN_KERNEL in Kconfig
> 
> the arguments as to why the firmware was split out of the drivers have
> already been made on this list.  Not that I agree with them, but the
> decision has been made and we're (network devs) going along with it.

Still, if that leads to functional regressions, like this one, we need to do
something about it IMO.  David?

Thanks,
Rafael

      parent reply	other threads:[~2009-01-19 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17 16:08 [2.6.29-rc2 regression] e100: netconsole not functional because of missing firmware Andrey Borzenkov
2009-01-19 18:30 ` Jesse Brandeburg
2009-01-19 18:43   ` Andrey Borzenkov
2009-01-19 19:20   ` Rafael J. Wysocki [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=200901192020.35116.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=arvidjaar@mail.ru \
    --cc=dwmw2@infradead.org \
    --cc=e1000-devel@lists.soutceforge.net \
    --cc=jesse.brandeburg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).