Quantcast

AR9227

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

AR9227

Hrishikesh
Hello,

I tried  using the ko's file generated by "madwifi-0.9.4" and "madwifi-hal-0.10.5.6-r4126-20100324" on an mips24 core based board and i am not able to get the wireless up (no ath0 entry) . There was no error in inserting the .Ko files.

The chip is AR9227 and the lspci command shows it as follows

# ./lspci -v
00:09.0 Ethernet controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
        Subsystem: Atheros Communications Inc. Device ee1c
        Flags: 66MHz, medium devsel, IRQ 138
        Memory at b6900000 (32-bit, non-prefetchable) [disabled] [size=64K]
        Capabilities: [40] #80 [0000]
        Capabilities: [80] #00 [0000]

#./lspci  -n
00:09.0 0200: 168c:ff1d (rev 01)


Grep on madwifi-hal-0.10.5.6-r4126-20100324 for "0xff1d" (PCI device id) shows  :

hal/ah_devid.h:94:#define AR5416_DEVID_EMU_PCI  0xff1d          /* PCI Owl Emulation*/

and this is the only entry for AR5416_DEVID_EMU_PCI . (there is no support in "madwifi-0.9.4" source)

I manually added the entry for 0xff1d PCI device in the PCI driver but after inserting the module
the pci driver complaints about eeprom magic.

I have used kernel 2.6.21.7 and required to use it.

Requesting your help to resolve this issue .

Thanks & Regards,
Hrishikesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AR9227

Pavel Roskin
On 06/29/2011 02:46 AM, Hrishikesh wrote:

> Hello,
>
> I tried  using the ko's file generated by "madwifi-0.9.4" and
> "madwifi-hal-0.10.5.6-r4126-20100324" on an mips24 core based board and i am
> not able to get the wireless up (no ath0 entry) . There was no error in
> inserting the .Ko files.
>
> The chip is AR9227 and the lspci command shows it as follows
>
> # ./lspci -v
> 00:09.0 Ethernet controller: Atheros Communications Inc. AR5008 Wireless

MadWifi 0.9.4 and the snapshots from the 0.9.4 branch don't support
AR5008.  You need a MadWifi snapshot from the trunk:

http://snapshots.madwifi-project.org/madwifi-trunk/

Alternatively, consider upgrading your kernel to at least 2.6.24 and
using compat-wireless with ath9k.

--
Regards,
Pavel Roskin

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Madwifi-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/madwifi-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AR9227

Hrishikesh
Thanks for your reply Pavel .
I did a grep for the device id 0xff1d on the trunk source and was not able to find this device .

Warm Regards,
Hrishikesh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AR9227

Pavel Roskin
On 06/29/2011 09:06 AM, Hrishikesh wrote:
> Thanks for your reply Pavel .
> I did a grep for the device id 0xff1d on the trunk source and was not able
> to find this device .

It needs to be added.  I checked Google, and it looks like that the
devices with IDs 0xff1c and 0xff1d are not supported as is.  There are
some hints that those devices have no EEPROM.  In any case, an open HAL
would be easier to modify to make such devices work.

--
Regards,
Pavel Roskin

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Madwifi-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/madwifi-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AR9227

Hrishikesh
Thanks for your reply.
You are right about the device id 0xff1d  seems like a generic id .The id should have been 0x2d  for AR9227 device.How can one use open HAL for system without EEPROM ?

Warm Regards,
Hrishikesh Gokhale
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: AR9227

Pavel Roskin
On 07/08/2011 05:43 AM, Hrishikesh wrote:
> Thanks for your reply.
> You are right about the device id 0xff1d  seems like a generic id .The id
> should have been 0x2d  for AR9227 device.How can one use open HAL for system
> without EEPROM ?

I'm afraid only by modifying the driver.

I think you have better chances someone helping you if you work with
ath9k, not with MadWifi.  MadWifi is not actively developed anymore.

--
Regards,
Pavel Roskin

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Madwifi-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/madwifi-users
Loading...