netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: "David Miller" <davem@davemloft.net>,
	Valdis.Kletnieks@vt.edu, 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 20:24:02 +0100	[thread overview]
Message-ID: <5a4c581d0901111124p753e0436q5dc3f4645e481c8b@mail.gmail.com> (raw)
In-Reply-To: <1231692789.25018.415.camel@macbook.infradead.org>

On Sun, Jan 11, 2009 at 5:53 PM, David Woodhouse <dwmw2@infradead.org> wrote:
> On Sun, 2009-01-11 at 17:42 +0100, Alessandro Suardi wrote:
>> Patches cleanly but doesn't build in 2.6.29-rc1:
>
> Pants; sorry, I omitted this bit...
>
> diff --git a/drivers/net/tg3.h b/drivers/net/tg3.h
> index ae5da60..508def3 100644
> --- a/drivers/net/tg3.h
> +++ b/drivers/net/tg3.h
> @@ -2764,6 +2764,7 @@ struct tg3 {
>        struct ethtool_coalesce         coal;
>
>        /* firmware info */
> +       const char                      *fw_needed;
>        const struct firmware           *fw;
>        u32                             fw_len; /* includes BSS */
>  };
>

This one works, thank you.

However, with the combination of in-kernel tg3 and
 CONFIG_IN_KERNEL_FIRMWARE=n there is at least a 30" delay
 during boot while waiting for the firmware request (which will fail).

Such wait didn't use to be there, and stuff worked. Could the wait
 be removed, to behave as it used to - as well ?

Thanks again, ciao,

--alessandro

 "Sun keeps rising in the west / I keep on waking fully confused"

   (The Replacements, "Within Your Reach")

  reply	other threads:[~2009-01-11 19:24 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 [this message]
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
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=5a4c581d0901111124p753e0436q5dc3f4645e481c8b@mail.gmail.com \
    --to=alessandro.suardi@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --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).