Lejin Joy(disabled)
|
Re: RE: LAN91C96 LAN controller driver --> devn-smc9000.so issue
|
Lejin Joy(disabled)
01/08/2009 10:43 AM
post19652
|
Re: RE: LAN91C96 LAN controller driver --> devn-smc9000.so issue
Hi Aboyd,
I tried giving the timer interrupt value but the sloginfo remained the same.
So was checking regarding detection of the PHY chip as per your suggestion. MDI_PHY_Find() function was failing over the
entire PHY id range but MDI_InitPhy() was successful.
The command I give is :
io-net -dsmc9000 ioport=0x04800000,irq=200,mac=0050c2271e63,verbose=4 -p tcpip
Kindly help me in clarifying following doubts :
1) How exactly we determine the required ioport for the driver ?
I am using the reference omap 5912 driver's ioport address, entered from command line (0x04800000) which gets
assigned as cfg.io_window_base[0] and mmap_device_io mapped to get the iobase as 0x1800000. And all further accessing
of registers are based on this.
On my board this gives me the following output with PHY chip not detected and chp id wrong.
devn-smc9000: detected 49152 bytes of on-chip RAM
Unable to find MII transceiver
devn-smc9000: No MII transceiver found!
SMC9000
Vendor .............. 0x0
Device .............. 0xf
Revision ............ 0x0
I/O port base ....... 0x4800000
Interrupt ........... 0xc8
MAC address ......... 0050c2 271e63
tcpip starting
Using pseudo random generator. See "random" option
The same on OMAP 5912 with the same controller chip gives the following and works fine.
devn-smc9000: detected 6144 bytes of on-chip RAM
SMC9000
Vendor .............. 0x0
Device .............. 0x4
Revision ............ 0x9
I/O port base ....... 0x4800000
Interrupt ........... 0xc8
MAC address ......... 000e99 020dd0
tcpip starting
Using pseudo random generator. See "random" option
And on assigning the IP address or mounting npm-qnet.so, it gives the following output continuously.
"devn-smc9000: chip has lost its memory, resetting MMU" from the smc9000_lockup_recover().
2) Is interrupt required for any of the initilization or chip reading ? Since the InterruptAttachEvent() is towards the
end of
smc9000_register_device(), is it used by any other functions other than for packet transmitting and recieving?
Could you please give your inputs.
Thanks,
Lejin
|
|
|