ar6k in andy-tracking

Robert Piasek robert.piasek at member.fsf.org
Fri Feb 20 22:20:26 CET 2009


On Thursday 19 February 2009 09:03:10 cz_jc wrote:
> Hello, I'm using andy-tracking branch kernel, commit
> de8460932576502fb6bf61968a37c4d2aed2d6e2
>
> When my phone boots up, I don't see eth0 interface. This appears in dmesg:
>
> [21474538.905000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested:
> 25000kHz).
> [21474538.905000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested:
> 25000kHz).
> [21474538.910000] mmc1: queuing CIS tuple 0x80 length 1
> [21474538.910000] mmc1: queuing CIS tuple 0x81 length 1
> [21474538.910000] mmc1: queuing CIS tuple 0x82 length 1
> [21474538.910000] mmc1: new SDIO card at address 0001
> [21474538.915000] sdio_ar6000 mmc1:0001:1: deviceInsertedHandler: -1
> [21474538.915000] sdio_ar6000 mmc1:0001:1: kthread_stop (ar6000_io): -4
> [21474538.920000] sdio_ar6000: probe of mmc1:0001:1 failed with error -4
>
> After running this tweak just a single time after boot, wifi works
> flawlessly even after suspend/resume:
> echo s3c2440-sdi >/sys/bus/platform/drivers/s3c2440-sdi/unbind
> echo s3c2440-sdi >/sys/bus/platform/drivers/s3c2440-sdi/bind

I've got very similar problem on current stable branch (2.6.29). After boot I 
cant see eth0 interface at all. The driver is compiled as module.

dmesg | grep ar6000
gives me completely NO output, but
lsmod | grep ar6000
ar6000                129440  0

The only way to get eth0 interface is to manually run:
echo s3c2440-sdi >/sys/bus/platform/drivers/s3c2440-sdi/bind

That gives me:
[37716.065000] s3c2440-sdi s3c2440-sdi: host detect has no irq available                 
[37716.065000] mapped channel 0 to 0                                                     
[37716.065000] regulator: Unable to get requested regulator: SD_3V3                      
[37716.065000] s3c2440-sdi s3c2440-sdi: Regulator for SD_3V3 unavilable                  
[37716.110000] s3c2440-sdi s3c2440-sdi: powered down.                                    
[37716.110000] s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: 0kHz).               
[37716.110000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).           
[37716.120000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).           
[37716.125000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).           
[37716.135000] s3c2440-sdi s3c2440-sdi: initialisation done.                             
[37716.135000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).           
[37716.150000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz).           
[37716.180000] mmc1: queuing CIS tuple 0x01 length 3                                     
[37716.205000] mmc1: queuing CIS tuple 0x1a length 5                                     
[37716.220000] mmc1: queuing CIS tuple 0x1b length 8                                     
[37716.220000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested: 
25000kHz).       
[37716.220000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested: 
25000kHz).       
[37716.235000] mmc1: queuing CIS tuple 0x80 length 1                                     
[37716.235000] mmc1: queuing CIS tuple 0x81 length 1                                     
[37716.235000] mmc1: queuing CIS tuple 0x82 length 1                                     
[37716.235000] mmc1: new SDIO card at address 0001                                       
[37717.310000] BMI Get Target Info: Exit (ver: 0x20000059 type: 0x1)                     
[37717.310000] eth0 (sdio_ar6000): not using net_device_ops yet                          
[37717.380000] AR6000 Reg Code = 0x40000060                                    

Can it be a problem with my .config? I'm using slightly modified 
gta02_moredrivers (just changed wlan and g_ether to modules).
Everything was working fine using this config on andy-tracking up until new 
stable branch was introduced.

Any ideas?

Thanks,
Rob

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmoko.org/pipermail/openmoko-kernel/attachments/20090220/0ce8840f/attachment.pgp 


More information about the openmoko-kernel mailing list