From: Joerg Albert <jal2@gmx.de>
To: Mladen Horvat <acid-burn@opendreambox.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: zd1211rw with MIPS architecture: mysterious behavior with zd1211b and AL2230/AL2230S RF Chip
Date: Fri, 31 Jul 2009 21:03:13 +0200 [thread overview]
Message-ID: <4A733FF1.7050301@gmx.de> (raw)
In-Reply-To: <loom.20090731T125828-710@post.gmane.org>
On 07/31/2009 03:11 PM, Mladen Horvat wrote:
> the same stick runs flawless on a x86 pc with kernel 2.6.30.
> as i said, also on the same machine with kernel 2.6.12 and the vendor driver
> this stick works without problems.
>
> perhaps someone has an idea ?
Just a wild guess, if your target runs MIPS in big endian: a missing endian conversion in the zd1211rw driver?
Wasn't USB little-endian based?
If the stick runs on the same MIPS target with 2.6.12 and vendor driver, it shouldn't be a USB 1.1 vs. 2.0
problem - I guess the stick is a high speed device, as the zd1211b supports 802.11g.
Regards,
Joerg.
next prev parent reply other threads:[~2009-07-31 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 13:11 zd1211rw with MIPS architecture: mysterious behavior with zd1211b and AL2230/AL2230S RF Chip Mladen Horvat
2009-07-31 19:03 ` Joerg Albert [this message]
2009-08-01 9:41 ` Mladen Horvat
2009-08-01 8:00 ` Hin-Tak Leung
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=4A733FF1.7050301@gmx.de \
--to=jal2@gmx.de \
--cc=acid-burn@opendreambox.org \
--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).