From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Michael Braun <michael-dev@fami-braun.de>,
Ivo van Doorn <IvDoorn@gmail.com>,
Helmut Schaa <helmut.schaa@googlemail.com>
Cc: netdev@vger.kernel.org, users@rt2x00.serialmonkey.com,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] rt2800usb:fix hang during firmware load
Date: Sun, 01 Jun 2014 23:09:24 +0400 [thread overview]
Message-ID: <538B7A64.1000306@cogentembedded.com> (raw)
In-Reply-To: <20140601175252.7980.64143.stgit@charlie.fem.tu-ilmenau.de>
On 06/01/2014 09:52 PM, Michael Braun wrote:
> The device 057c:8501 (AVM Fritz! WLAN v2 rev. B) boots into a state that does not actually require loading a firmware file.
Wrap the changelog lines on at least 80 chars please.
> The vendors driver finds out about this by checking a firmware state
> register, so this patch adopts this here.
> Finally, with this patch applied, my wifi dongle actually becomes
> usefull (scan + connect to wpa network works).
s/usefull/useful/.
> Signed-off-by: Michael Braun <michael-dev@fami-braun.de>
> ---
> drivers/net/wireless/rt2x00/rt2800usb.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
> diff --git a/drivers/net/wireless/rt2x00/rt2800usb.c b/drivers/net/wireless/rt2x00/rt2800usb.c
> index b601422..71bf101 100644
> --- a/drivers/net/wireless/rt2x00/rt2800usb.c
> +++ b/drivers/net/wireless/rt2x00/rt2800usb.c
> @@ -240,6 +240,7 @@ static int rt2800usb_write_firmware(struct rt2x00_dev *rt2x00dev,
> int status;
> u32 offset;
> u32 length;
> + __le32 fwMode;
>
> /*
> * Check which section of the firmware we need.
> @@ -257,8 +258,17 @@ static int rt2800usb_write_firmware(struct rt2x00_dev *rt2x00dev,
> /*
> * Write firmware to device.
> */
> - rt2x00usb_register_multiwrite(rt2x00dev, FIRMWARE_IMAGE_BASE,
> - data + offset, length);
> + rt2x00usb_vendor_request(rt2x00dev, USB_DEVICE_MODE,
> + USB_VENDOR_REQUEST_IN, 0, 0x11, &fwMode,
> + sizeof(fwMode), REGISTER_TIMEOUT_FIRMWARE);
> +
> + if ((fwMode & 0x00000003) == 2) {
Same comment as for the patch #1.
> + rt2x00_info(rt2x00dev,
> + "Firmware loading not required - NIC in AutoRun mode\n");
This line should start under 'rt2xx00dev', like below.
> + } else {
> + rt2x00usb_register_multiwrite(rt2x00dev, FIRMWARE_IMAGE_BASE,
> + data + offset, length);
> + }
WBR, Sergei
prev parent reply other threads:[~2014-06-01 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 17:52 [PATCH 0/2] rt2800usb: Fix support for USB 057c:8501 Michael Braun
2014-06-01 17:52 ` [PATCH 1/2] rt2800usb:fix efuse detection Michael Braun
2014-06-01 19:06 ` Sergei Shtylyov
2014-06-02 13:06 ` Stanislaw Gruszka
2014-06-01 17:52 ` [PATCH 2/2] rt2800usb:fix hang during firmware load Michael Braun
2014-06-01 19:09 ` Sergei Shtylyov [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=538B7A64.1000306@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=IvDoorn@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=michael-dev@fami-braun.de \
--cc=netdev@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.com \
/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).