hi all,i also found this link that say that drivers > 1.2 are not suitable for dm9000e that is in my board.
http://www.cutedigi.com/article_info.php?articles_id=29 Could it be that i have to look for a v 1.2 driver ? thanks angelo On 01/06/2010 21:16, angelo wrote:
Hi Lennart,i connected stright D0:D31 of coldfire with D0:31 of the chip. I still didn't looked too much inside the driver, but actually, probably i am one step before, the dm9000_probe is not called at all (i put some printk inside).regards, angelo On 01/06/2010 21:01, Lennart Sorensen wrote:On Tue, Jun 01, 2010 at 08:46:19PM +0200, angelo wrote:i am trying to make work properly the dm9000 driver in a custom board with coldfire mcf5307. Until now, this is what i did:- driver was already there, inside linux-2.6.X folder, i just enabled inthe config a selectable option for MCF5307. - i added some writesb,w,l/readsb,w,l functions in nomm_io.h arch/m68k/include/asm/io_no.h /** angelo, DM9000 support for MCF5307, start */ #define readsb(b,addr,count) readb(addr) #define readsw(b,addr,count) readw(addr) #define readsl(b,addr,count) readl(addr) #define writesb(b,addr,count) (io_insb((unsigned int)b,addr,count)) #define writesw(b,addr,count) (io_insw((unsigned int)b,addr,count)) #define writesl(b,addr,count) (io_insl((unsigned int)b,addr,count)) /* angelo, DM9000 support for MCF5307, end */ kernel compile fine, but i just see the following line at boot: .... dm9000 Ethernet Driver, V1.31 .... and nothing else dm9000 related, so no dm9000_probe is executed, and so the chip is not initialized.Is the endianess right? I have seen the DM9000 used with little endian arm systems. I have not seen it on coldfire (big endian) systems.
_______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
