From: Gert Boddaert <Gert.Boddaert@Boditec.be>
To: linux-wireless@vger.kernel.org
Subject: rt2x00 : big-endianess broken for rt73usb (master mode) for e.g. xscale and powerpc
Date: Wed, 22 Jul 2009 07:34:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20090722T072047-806@post.gmane.org> (raw)
I was able to do some testing on the rt73usb driver.
As mentioned in an earlier post, the latest driver breaks the master mode.
Although a linux client (x86 laptop) can connect to the rt73usb AP,
a windows XP client (x86 laptop) cannot.
I fails to obtain a DHCP address.
In order to reproduce the bug, you need a big-endian system with a rt73usb
stick, and hostapd.
I did not test client mode for big-endian systems.
Breaking down the different patches that were applied since 8 april 2009, I was
able to identify the culprit.
No solution yet, but I thought I should flag this
as a bug.
It is the following patch that breaks big-endian compatibility:
***
Some hardware require L2 padding between header and payload
because both must be aligned to a 4-byte boundary. This hardware
also is easier during the RX path since we no longer need to
move the entire payload but rather only the header to remove
the padding (mac80211 only wants the payload to be 4-byte aligned).
Signed-off-by: Ivo van Doorn <IvDoorn@...>
---
drivers/net/wireless/rt2x00/rt2x00.h | 10 ++++
drivers/net/wireless/rt2x00/rt2x00crypto.c | 68 +++++++++++++++++-----------
drivers/net/wireless/rt2x00/rt2x00dev.c | 33 +++++++------
drivers/net/wireless/rt2x00/rt2x00lib.h | 27 +++++++++--
drivers/net/wireless/rt2x00/rt2x00queue.c | 39 ++++++++++++++++
drivers/net/wireless/rt2x00/rt2x00queue.h | 14 +++++-
6 files changed, 143 insertions(+), 48 deletions(-)
(...)
reply other threads:[~2009-07-22 7:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=loom.20090722T072047-806@post.gmane.org \
--to=gert.boddaert@boditec.be \
--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