From: Pavel Roskin <proski@gnu.org>
To: Dave <kilroyd@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 00/05] orinoco: Agere/Lucent firmware download
Date: Fri, 14 Sep 2007 01:05:12 -0400 [thread overview]
Message-ID: <1189746312.26312.39.camel@dv> (raw)
In-Reply-To: <46E8557F.2080401@gmail.com>
Hello, Dave!
On Wed, 2007-09-12 at 22:09 +0100, Dave wrote:
> Implements firmware download to RAM for Lucent-Agere firmware.
> Firmware download is a requirement to implement WPA on these cards.
I really appreciate your efforts.
Please avoid copying to David Gibson in the future, as he stepped down
as the maintainer.
Also, it may work better if you post your patches to orinoco-devel
first, and then to linux-wireless. Many people hesitate to reply to
messages cross-posted to several lists. orinoco-users doesn't need to
be involved at all.
I understand that it's a major change, and in needs to be tested
thoroughly. I don't have time to review the patches right now, but it
is on my TODO list.
> The following firmwares download and run on my Dell TrueMobile 1150:
> 7.65, 8.10, 8.42, 8.58
What some users may want to run is 6.06 or 6.16, as the 7.xx and 8.xx
firmwares have stability issues with the monitor mode.
> The following firmwares download, but are not compatible with the
> current orinoco_cs driver:
> 9.40, 9.42, 9.48
That's great news anyway. We may see Hermes II supported eventually.
> All my testing done on a pentium3 Dell C600. FW 9.48 download also
> confirmed on a powerbook using a modified airport driver compiled
> with a static copy of the firmware
Please use sparse to check endianess and other issues. You can use this
command once sparse is in PATH:
make C=2 CF="-Wall -D__CHECK_ENDIAN__"
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-09-14 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 21:09 [PATCH 00/05] orinoco: Agere/Lucent firmware download Dave
2007-09-14 5:05 ` Pavel Roskin [this message]
2007-09-14 17:53 ` Dave
2007-09-14 18:48 ` Dave
2007-09-14 19:06 ` Johannes Berg
2007-09-14 21:01 ` Dave
2007-09-14 21:13 ` 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=1189746312.26312.39.camel@dv \
--to=proski@gnu.org \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@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).