netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Oeser <netdev@axxeo.de>
To: "Michael Chan" <mchan@broadcom.com>
Cc: "Lucas Nussbaum" <lucas.nussbaum@imag.fr>,
	"netdev" <netdev@vger.kernel.org>
Subject: Re: [BUG] tg3 cannot do PXE (loses MAC address) after soft reboot
Date: Mon, 17 Sep 2007 13:29:35 +0200	[thread overview]
Message-ID: <200709171329.35656.netdev@axxeo.de> (raw)
In-Reply-To: <1189795942.9540.155.camel@dell>

Michael Chan schrieb:
> On Fri, 2007-09-14 at 10:14 +0200, Ingo Oeser wrote:
> > Is it enough to parse the first number in the firmware via simple_strtoul()?
> 
> No, it's not.  We need to check the number after the '.' and possibly an
> alphabet at the end as well.  Worse yet, the version may be different
> for different chips.

Ah, I see. I thought the first number is some constantly increasing
internal version number from your SCM[1] and the other is the 
"marketing release number".

Thank you for explaining this. And that different version for different
chips issue make it really hard. I can see that now.
 
> We'll see if we can come up with a simple way to detect the problem.

That would help your users (like the customers of my employer).
Admins and system vendors will love you for that :-)


Best Regards

Ingo Oeser

[1] Source Control Management e.g. cvs, subversion, git

      reply	other threads:[~2007-09-17 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13  8:39 [BUG] tg3 cannot do PXE (loses MAC address) after soft reboot Lucas Nussbaum
2007-09-13 15:15 ` Michael Chan
2007-09-13 15:41   ` Lucas Nussbaum
2007-09-13 18:05     ` Michael Chan
2007-09-13 19:28       ` Lucas Nussbaum
2007-09-13 20:47         ` Michael Chan
2007-09-14  8:14           ` Ingo Oeser
2007-09-14 18:52             ` Michael Chan
2007-09-17 11:29               ` Ingo Oeser [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=200709171329.35656.netdev@axxeo.de \
    --to=netdev@axxeo.de \
    --cc=lucas.nussbaum@imag.fr \
    --cc=mchan@broadcom.com \
    --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).