On Thursday 09 April 2009, Tom Wheeler wrote: > I have had problems getting the dm9000 mac/phy working properly with the > DM355 EVM. I have seen a number of posts indicating problems with the > dm9000 and the DM355.
In my case, enabling LOCKDEP is sufficient to make all of those problems vanish ... a dm9000 IRQ handler bugfix made *some* of the problems go away. (e3162d381fc359ebe5c98a3e216888a7cb200051 is in 2.6.29 and thus DaVinci GIT.) > The 2.6.18 kernel requests the individual > interrupt for GPIO1 (IRQ 45) where the 2.6.28 kernel uses the gpio > controller interrupt (IRQ 65) which is chained to the bank interrupt. > By changing the 2.6.28 kernel to reflect what I saw in the 2.6.18 kernel > this seemed to solve the problems I was seeing. How did you get the "direct" GPIO IRQ to work? Did you have to disable its bank IRQ or anything? Last time I tried to use those "direct" IRQs, they didn't work at all. > Are there known issues with the DM355 gpio controller interrupt handling > where it chains the individual interrupts to the bank interrupt? So far as I know, the DM355 EVM is the first DaVinci board to make heavy use of GPIO IRQs. So it's plausible that there be some kind of load-dependent bug there. There's no confirmation of such a bug in IRQ handling, though. I'm moderately convinced there *is* a timing bug affecting that EVM, but whether it's EMIF bus timings or some IRQ handling race is an open question. - Dave _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
