From: Larry Finger <larry.finger@lwfinger.net>
To: Andy Green <andy@warmcat.com>
Cc: Michael Buesch <mb@bu3sch.de>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH 2/2] bcm43xx-mac80211: Fix reported rx frequency and channel
Date: Fri, 20 Jul 2007 09:36:01 -0500 [thread overview]
Message-ID: <46A0C851.2040302@lwfinger.net> (raw)
In-Reply-To: <46A050B4.3060500@warmcat.com>
Andy Green wrote:
>
> I never heard of a special blessed firmware before, I don't think that
> the driver made any dmesg when given the non-blessed one, if that is
> what it is? I was given this firmware by the traditional "person on
> IRC" and don't know where it came from, but I still have it here if any
> versioning can be extracted from it.
Just as API's and ABI's change, the writers of firmware can change their layout, which is what
happened here. Nothing "blessed", just one behavior before, and a second after, the change. The
version info can be gotten from fwcutter.
Larry
next prev parent reply other threads:[~2007-07-20 14:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 10:38 [PATCH 0/2] Small driver fixes andy
2007-06-11 10:38 ` [PATCH 1/2] zd1211rw-mac80211: return hardware specific tx rate code for rx status andy
2007-07-19 19:10 ` John W. Linville
2007-07-19 21:19 ` Ulrich Kunitz
2007-06-11 10:38 ` [PATCH 2/2] bcm43xx-mac80211: Fix reported rx frequency and channel andy
2007-06-11 11:26 ` Johannes Berg
2007-06-11 11:45 ` Johannes Berg
2007-07-19 19:10 ` John W. Linville
2007-07-19 19:39 ` Michael Buesch
2007-07-20 6:05 ` Andy Green
2007-07-20 7:37 ` Johannes Berg
2007-07-20 13:31 ` John W. Linville
2007-07-20 14:36 ` Larry Finger [this message]
2007-07-20 14:47 ` Andy Green
2007-07-20 16:58 ` Larry Finger
2007-07-20 17:36 ` Michael Buesch
2007-07-20 17:48 ` Andy Green
2007-07-20 17:50 ` Michael Buesch
2007-07-20 20:40 ` Johannes Berg
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=46A0C851.2040302@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=andy@warmcat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).