Intel AnyPoint II AP310 USB Adaptor and at76c503-i3861 version 0.10 bizarreness

um, further testing has led me to conclude that if i use the 0.10 sources
as opposed to the CVS sources i can place the unit into master mode and
send and receive packets using the at76c503-i3861 module after modifying
the sources to include the vendor/product id 0x8086/0x200.

as to whether or not i can actually begin meshing now, well... i'll see.

peace, and thank you for all the hard work.

Tony

On Tue, 5 Jul 2005, T Man wrote:

>
> Hello,
>
> I'm using an Intel Anypoint II AP310 USB Adaptor with kernel 2.4.27.
>
> All is well, but i have a comment.
>
> After my initial noodling with the device i posted success with the
> at76c503-i3863 module. I noticed soon afterwards that the compatibility
> list was updated with the AP310 using the at76c503-i3861 chipset.
>
> that caused me to wonder if i had done something wrong. after doing a bit
> of reading i went and got the CVS sources and recompiled. true, the
> at76c503-i3861 is working just fine with the AP310, connecting to my local
> AP at 11Mb/s in managed mode and working seamlessly with iwconfig.
>
> i'm perplexed because i noticed when i had added the 0x8086 vendor code
> and the 0x200 product ID to at76c503-i3863.c (release 0.10), i could put
> wlan0 into master mode. at the time, i didn't have an AP at all.  in fact,
> to be fair, i only posted success with the i3863 insofar as i was able to
> use iwconfig. there were no actual packets sent and received that i can
> recall, although i was trying to do some stationary wardriving.
>
> i'm reading through the mailing list archives trying to see what kind of
> crack i'm smoking; i still have hopes that it may be possible to mess with
> the firmware and get an AP going with the at76c503 from my one fleeting
> glimpse at an iwconfig output including the words "mode: master"
>
> messing around,
>
> Tony
>