* Jason Cooper <jason@xxxxxxxxxxxxxx> [130508 15:04]: > On Wed, May 08, 2013 at 12:51:53PM -0700, Tony Lindgren wrote: > > * Jason Cooper <jason@xxxxxxxxxxxxxx> [130508 12:29]: > > > > > > Current Problem: > > > > > > There are several gaps in my understanding of how far along TI's conversion to > > > DT is. Should I be doing a separate board file for initializing the legacy > > > items? I was hoping to do it all with DT. > > > > Sorry forgot to reply to this.. No seprate board file should be needed, > > some devices may still need to be initialized with pdata based on the > > compatible flag. > > ti,hwmod, right? Yes.. see mach-omap2/devices.c for the list that's still not initialized via DT. > > > Obviously, I don't expect anybody to run out and buy one of these, take it > > > apart, and try to boot this code. But if the omap guys could take a look at > > > this and give me a few pointers, I'd appreciate it. I'm kind of spinning my > > > wheels at the moment. > > > > > > Primarily, I'd like to get nand and usb working, so that I can read/write, > > > mount a rootfs and do better testing. > > > > The USB should be doable with device tree. At least both echi and > > musb are working properly on pandaboard. I think people have been > > using NAND with the gpmc DT patches, but I don't know the current > > status for sure. > > I'll try your suggestion in your other email for ToT and see if I can > get gpmc going. > > > Is the hard drive on the EHCI bus or how is it connected to omap? > > via ehci. They brutalized the tps driver to detect if the goflex cable > was attached or not. Once I get something stable, I'll probably write a > separate driver for that code. Or, push it out to userspace. OK. I guess you need to disconnect the drive from EHCI if the goflex is attached to avoid disk corruption? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
