From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Martin Langer <martin-langer-Mmb7MZpHnFY@public.gmane.org>,
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>,
Stefano Brivio <st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
Subject: Re: [PATCH] bcm43xx-softmac: improve wrong firmware message
Date: Thu, 14 Sep 2006 10:00:40 -0400 [thread overview]
Message-ID: <20060914140034.GB27558@tuxdriver.com> (raw)
In-Reply-To: <45072F4D.80109-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
On Tue, Sep 12, 2006 at 05:06:05PM -0500, Larry Finger wrote:
> Martin Langer wrote:
> >
> >Why not writing both (ucode rev and driver version)? Something like
> >
> > "from version 4.x binary drivers (rev>0x128).\n"
> >
> >BTW, if anybody needs the relationship between ucode revsion and driver
> >version then he should look at the table here:
> >
> >http://www.langerland.de/linux/bcm43xx/firmware.html
>
> I could do that; however, I think this error message may have a short life
> as I'm just now looking at Michael's v4 firmware revisions for d80211 with
> an eye toward porting them to softmac.
>
> John - what do you think?
Let's just take the new/current patch as-is. Someone who understands
"rev > 0x128" should be able to find the message in the code for
himself... :-)
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
prev parent reply other threads:[~2006-09-14 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 20:29 [PATCH] bcm43xx-softmac: improve wrong firmware message Larry Finger
2006-09-12 21:49 ` Martin Langer
2006-09-12 22:06 ` Larry Finger
[not found] ` <45072F4D.80109-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-13 12:31 ` Michael Buesch
2006-09-14 14:00 ` John W. Linville [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=20060914140034.GB27558@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
--cc=martin-langer-Mmb7MZpHnFY@public.gmane.org \
--cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.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).