From: Pavel Machek <pavel@suse.cz>
To: rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>,
Netdev list <netdev@vger.kernel.org>,
Jirka Lenost Benc <jbenc@suse.cz>,
pe1rxq@amsat.org
Subject: zd1201 failure on sharp zaurus explained
Date: Tue, 30 May 2006 15:20:54 +0200 [thread overview]
Message-ID: <20060530132054.GA9780@elf.ucw.cz> (raw)
Hi!
Now I found out what went wrong with zd1201 on sharp zaurus (spitz)...
Card is detected and seems to work okay, except that you don't get any
results from iwlist eth1 scan, and card generally does not do anything
involving radio.
And now I have an explanation, too:
If you plug card directly to zaurus, above is what happens.
If you plug it into the hub, hub flashes the lights and shuts down, as
if not enough power is available from the zaurus.
...which is probably the case, because if I connect external 6V power
supply to the hub, it all starts to work.
So... it is
1) hw problem: spitz power supply is not strong enough to drive zd1201
2) usb problem, probably. Should not usb core detect that card
requires too much juice and refuse to power it up?
...and the morale is, always put hub between device and the host so
that you can see the flashy leds :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2006-05-30 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 13:20 Pavel Machek [this message]
2006-05-30 14:11 ` zd1201 failure on sharp zaurus explained Oliver Neukum
2006-05-30 14:49 ` Pavel Machek
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=20060530132054.GA9780@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=jbenc@suse.cz \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pe1rxq@amsat.org \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
/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).