From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: e1000-devel@lists.sourceforge.net, jaswinder@infradead.org,
linux-next@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3)
Date: Mon, 03 Nov 2008 16:09:27 +0000 [thread overview]
Message-ID: <1225728567.745.13.camel@macbook.infradead.org> (raw)
In-Reply-To: <20081103160057.GA12456@orion>
On Mon, 2008-11-03 at 19:00 +0300, Alexander Beregalov wrote:
> # CONFIG_FIRMWARE_IN_KERNEL is not set
> CONFIG_EXTRA_FIRMWARE=""
OK, so you didn't include the E100 firmware in the kernel, so it only
actually manages to bring up the E100 after it's mounted the root file
system, not in time for the console?
If you set CONFIG_FIRMWARE_IN_KERNEL, does it work?
I think that's fairly much expected behaviour. I wonder if there's a way
we could make it slightly more intuitive though.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-11-03 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 12:25 e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3) Alexander Beregalov
2008-11-03 15:49 ` Alexander Beregalov
2008-11-03 15:56 ` David Woodhouse
2008-11-03 16:00 ` Alexander Beregalov
2008-11-03 16:09 ` David Woodhouse [this message]
2008-11-03 16:42 ` Alexander Beregalov
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=1225728567.745.13.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=a.beregalov@gmail.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jaswinder@infradead.org \
--cc=linux-next@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