Forest Bond wrote:
> I see. So, the only apparent solution is to notify Atheros of the problem,
> and
> hope that they chastise the module manufacturer appropriately?
Your mac OUI is Abocom. We had a previous report of abocom doing this
exact crime with the same ID a while ago. It's unfortunate
> I don't think so, I'm thinking more specific entries in the
> EEPROM. We would need a debug version that dumps the EEPROM before
> we load the firmware. We will have to find data at some offset,
> which reliably would tell us, whether we deal with a ZD1211B
> instead of a ZD1211. Just classical r
On Wed, Aug 15, 2007 at 11:00:47PM +0200, Ulrich Kunitz wrote:
> Forest Bond wrote:
> > >> I hope this is enough info to get this working in mainline.
> >
> > > Not really, we need to find another way to identify the chip.
> >
> > It wouldn't be something you could find in /proc/bus/usb/devices,
Forest Bond wrote:
> Hi,
>
> On Wed, Aug 15, 2007 at 07:59:51AM +0200, Ulrich Kunitz wrote:
> >> Vendor: Shuttle
> >> Model: PN18G (although it doesn't seem to be marked as such)
> >> USB Device ID: 07b8:6001
> >> Chip: ZD1211B
> >> RF: AL2230S
>
> [...]
>
Hi,
On Wed, Aug 15, 2007 at 07:59:51AM +0200, Ulrich Kunitz wrote:
>> Vendor: Shuttle
>> Model: PN18G (although it doesn't seem to be marked as such)
>> USB Device ID: 07b8:6001
>> Chip: ZD1211B
>> RF: AL2230S
[...]
>> Anyway, it looks like this is a re-us
> Vendor: Shuttle
> Model: PN18G (although it doesn't seem to be marked as such)
> USB Device ID: 07b8:6001
> Chip: ZD1211B
> RF: AL2230S
>
> The chip description from dmesg:
>
> [ 1378.268000] zd1211rw 5-6:1.0: zd1211b chip 07b8:6001 v4810 high 00-12-0e
>
Hi,
Quick device info:
Vendor: Shuttle
Model: PN18G (although it doesn't seem to be marked as such)
USB Device ID: 07b8:6001
Chip: ZD1211B
RF: AL2230S
You can see this product here:
http://www.newegg.com/Product/Product.aspx?Item=N82E16856997001
The chip
