netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Valdis.Kletnieks@vt.edu
Cc: David Miller <davem@davemloft.net>,
	alessandro.suardi@gmail.com, jaswinderlinux@gmail.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.28-git8: tg3 doesn't work due to firmware not loading (-git7 is ok)
Date: Sun, 11 Jan 2009 22:46:20 +0000	[thread overview]
Message-ID: <1231713980.25018.708.camel@macbook.infradead.org> (raw)
In-Reply-To: <99827.1231712979@turing-police.cc.vt.edu>

On Sun, 2009-01-11 at 17:29 -0500, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 11 Jan 2009 13:49:37 PST, David Miller said:
> > From: Valdis.Kletnieks@vt.edu
> > Date: Sun, 11 Jan 2009 11:48:22 -0500
> > 
> > > One unanswered question:  What do we expect the system to do if they have this
> > > patch, TIGON3=y, FIRMWARE_IN_KERNEL=n, and configure a netconsole for boot
> > > messages?  I'm *hoping* the answer is "the netconsole doesn't come up at boot,
> > > but can be re-enabled via the /sys/kernel/config/netconsole interface after
> > > you've done an 'ifconfig eth0 up' or similar, or do a 'modprobe netconsole'.
> > > 
> > > Those seem like reasonable semantics to me - anybody got a different opinion?
> > 
> > Even better, how about nfsroot?  There is no "later", either you
> > can mount to root filesystem or you fail.
> 
> I don't see any sane way for an nfsroot to work unless you've built the kernel
> with TIGON3=y, and FIRMWARE=y.  Anything else is just crazy talk.  For that
> case, I'd suggest we just do this:
> 
> Signed-off-by: Valdis Kletnieks <valdis.kletnieks@vt.edu>
> 
> --- linux-2.6.28-mmotm0109/Documentation/filesystems/nfsroot.txt.dist	2008-12-24 18:26:37.000000000 -0500
> +++ linux-2.6.28-mmotm0109/Documentation/filesystems/nfsroot.txt	2009-01-11 17:27:31.000000000 -0500
> @@ -30,6 +30,9 @@ In the networking options, kernel level 
>  along with the types of autoconfiguration to support. Selecting all of
>  DHCP, BOOTP and RARP is safe.
>  
> +In addition, your network interface driver must be selected as built-in,
> +and if the card is a Tigon3 or other card that requires a firmware load
> +to become functional, you need to select FIRMWARE_IN_KERNEL.

Yeah, but it's not FIRMWARE_IN_KERNEL in the general case -- that's just
for a handful of 'speshul' legacy drivers. In the general case it's the
CONFIG_EXTRA_FIRMWARE option which needs to be set to include the
required firmware.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation

  reply	other threads:[~2009-01-11 22:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5a4c581d0901070624t6e769966t6b034b14d4732bd@mail.gmail.com>
2009-01-08  4:03 ` 2.6.28-git8: tg3 doesn't work due to firmware not loading (-git7 is ok) Alessandro Suardi
2009-01-08  6:12 ` Jaswinder Singh Rajput
2009-01-08 20:33   ` Alessandro Suardi
2009-01-08 20:53     ` David Miller
2009-01-09 17:30       ` Alessandro Suardi
2009-01-09 22:04         ` David Miller
2009-01-09 22:29           ` Alessandro Suardi
2009-01-11 11:10           ` Valdis.Kletnieks
2009-01-11 12:08             ` David Miller
2009-01-11 12:24               ` David Woodhouse
2009-01-11 12:59                 ` David Woodhouse
2009-01-11 16:42                   ` Alessandro Suardi
2009-01-11 16:53                     ` David Woodhouse
2009-01-11 19:24                       ` Alessandro Suardi
2009-01-11 19:26                         ` David Woodhouse
2009-01-11 16:48                   ` Valdis.Kletnieks
2009-01-11 16:56                     ` David Woodhouse
2009-01-11 21:49                     ` David Miller
2009-01-11 22:29                       ` Valdis.Kletnieks
2009-01-11 22:46                         ` David Woodhouse [this message]
2009-01-11 21:41                   ` David Miller
2009-01-12  0:10                   ` Valdis.Kletnieks
2009-01-12  1:39                     ` Valdis.Kletnieks
2009-01-12  8:13                     ` David Woodhouse
2009-01-13  4:46                       ` Valdis.Kletnieks
2009-01-13  5:52                       ` Valdis.Kletnieks
2009-01-11 21:39                 ` David Miller
2009-01-11 22:02                   ` David Woodhouse
2009-01-11 22:05                     ` David Miller
2009-01-11 22:41                       ` David Woodhouse
2009-01-13  6:13                         ` Willy Tarreau
2009-01-11 22:15                   ` David Woodhouse
2009-01-11 22:19                     ` David Miller
2009-01-13 18:39                   ` Matt Carlson
2009-01-13 20:27                     ` David Miller

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=1231713980.25018.708.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=alessandro.suardi@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jaswinderlinux@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).