linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: Ram kumar <ramkumar.research@gmail.com>,
	Javier Cardona <javier@cozybit.com>,
	andrey@cozybit.com, linux-wireless@vger.kernel.org
Subject: Re: any controller working in AP mode ?
Date: Thu, 23 Jul 2009 12:32:04 -0400	[thread overview]
Message-ID: <1248366724.2661.9.camel@mj> (raw)
In-Reply-To: <200907230846.17683.hs4233@mail.mn-solutions.de>

On Thu, 2009-07-23 at 08:46 +0200, Holger Schurig wrote: 
> > Web search for 1286:1fab doesn't find anything useful other
> > than recommendations to use ndiswrapper.
> 
> It might be some 802.11n (marketing speak "Top Dog") thingy ???

That's very unlikely.  ZEW2502 is advertised as 802.11b/g and it's dirt
cheap ($20).  Besides, its ID 1286:1fab suggests that it's probably a
predecessor of 1286:2001 that is supported by the kernel drivers.

In case it matters, its FCC ID is T58331GU2006M1.  Some sites say its
chipset is "Marvell 88W8338 + 88W8010", see e.g.
http://www.xpcgear.com/zew2502.html

I modified both libertas drivers to support that ID.  usb8xxx asks for
usb8388.bin.  After I installed that firmware, usb8xxx started panicking
with so many messages that the interesting part scrolls from the screen.
I could try to capture that with a serial console.  It's clearly not the
right way to react to bad hardware.

As for libertas_tf_usb, it does something strange.  It registers a phy
that only supports monitor mode.  No network device is registered.  I
can add it using iw.  If I try to bring the interface up, the driver
requests lbtf_usb.bin.  Whether that file is present of not, ifconfig
hangs, and all subsequent network commands on other terminals hang too.

Apparently, error handling in libertas drivers needs some improvement,
regardless of whether ZEW2502 is a potentially supported device.

The device is supported by ndiswrapper with the x86_64 WinXP driver.
Scanning works, but wpa_supplicant fails.  That's just to verify that
the device is functional.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-07-23 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  5:21 any controller working in AP mode ? Ram kumar
2009-07-15 18:12 ` Andrey Yurovsky
2009-07-15 20:44 ` Javier Cardona
2009-07-16  6:38   ` Ram kumar
2009-07-17 15:19     ` Pavel Roskin
2009-07-17 17:57       ` Bob Copeland
2009-07-20 12:03       ` Ram kumar
2009-07-20 12:22         ` Pavel Roskin
2009-07-22 15:48       ` Pavel Roskin
2009-07-23  6:46         ` Holger Schurig
2009-07-23 16:32           ` Pavel Roskin [this message]
2009-07-23 22:39             ` Pavel Roskin

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=1248366724.2661.9.camel@mj \
    --to=proski@gnu.org \
    --cc=andrey@cozybit.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=javier@cozybit.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ramkumar.research@gmail.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).