From: Yan Seiner <yan@seiner.com>
To: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Marvel 8385 on a Sharp Zaurus
Date: Sun, 02 Mar 2008 19:34:34 -0800 [thread overview]
Message-ID: <47CB71CA.7050304@seiner.com> (raw)
I have a Marvell 8385 card that I am trying to use with a Sharp Zaurus,
a Xscale CPU. The card is completely dead after associating.
It associates, but fails to transmit any data. I applied this patch
<http://lists.infradead.org/pipermail/libertas-dev/2008-January/001130.html>
and now the packet counters increment when I check with ifconfig but the
card still doesn't send or receive any data.
In other words, the card associates nearly instantly, I get good signal
strength with iwconfig, ifconfig shows the RX counter incrementing if I
ping it from outside, but no packets are sent in response.
If I ping outside from inside the Zaurus, the TX counter increments, but
nothing is received on the outside.
Is there anything I can do to help debug this? I am stuck with this
card (I need Channel 13) and that's the only card that provides that.
Thanks,
--Yan
reply other threads:[~2008-03-03 4:09 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=47CB71CA.7050304@seiner.com \
--to=yan@seiner.com \
--cc=libertas-dev@lists.infradead.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).