From: Jouni Malinen <jkmaline@cc.hut.fi>
To: Pavel Roskin <proski@gnu.org>
Cc: NetDev <netdev@vger.kernel.org>, hostap <hostap@shmoo.com>
Subject: Re: [PATCH] hostap: allow flashing firmware
Date: Wed, 4 Jan 2006 21:18:57 -0800 [thread overview]
Message-ID: <20060105051857.GO8939@jm.kir.nu> (raw)
In-Reply-To: <1135984946.17805.21.camel@dv>
On Fri, Dec 30, 2005 at 06:22:26PM -0500, Pavel Roskin wrote:
> Host AP driver has code to support writing firmware to non-volatile
> memory, a.k.a. flash. This code has been extensively tested when Host
> AP was a standalone driver.
>
> Add a configuration option to the kernel to allow enabling this
> functionality. Improve the description of the RAM download option.
> Mention cards that require it. Remove obsolete scary comment.
I'm not completely against this change, but that scary comment is there
on purpose and it is not fully obsolete. It is still possible to get
HFA3841 cards into state which require hardware modifications to recover
from (i.e., they are as good as dead for most users). Taken into this
account, I would prefer that the help text for HOSTAP_FIRMWARE_NVRAM
would include a warning about the potential issues of using incorrect
firmware images. In most cases, RAM (volatile) download can be used to
upgrade the firmware without having to modify the flash contents. This
is also what the current Windows drivers are doing.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-01-05 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 23:22 [PATCH] hostap: allow flashing firmware Pavel Roskin
2006-01-05 5:18 ` Jouni Malinen [this message]
2006-01-05 11:34 ` Henrik Brix Andersen
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=20060105051857.GO8939@jm.kir.nu \
--to=jkmaline@cc.hut.fi \
--cc=hostap@shmoo.com \
--cc=netdev@vger.kernel.org \
--cc=proski@gnu.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).