On Tue, Sep 29, 2009 at 11:12:10AM -0700, Mark A. Greer wrote: > On Tue, Sep 29, 2009 at 10:36:13AM -0700, Kevin Hilman wrote: > > "Thompson, Nick (GE EntSol, Intelligent Platforms)" > > <[email protected]> writes: > > > > [...] > > > > > static struct davinci_id da830_ids[] = { > > > { > > > .variant = 0x0, > > > .part_no = 0xb7df, > > > .manufacturer = 0x017, /* 0x02f >> 1 */ > > > .cpu_id = DAVINCI_CPU_ID_DA830, > > > .name = "da830/omap l137", > > > }, > > > }; > > > > > > I hacked the 0x0 to 0x08 and my target now boots. I guess the correct > > > fix is to add a second entry for the new (?) variant, but I'm not a > > > kernel expert. > > > > > > I hope that helps. Feel free to ask for more info. > > > > > > > I've merged some patches for new silicon revs of dm646x and dm355 but > > haven't seen any patches for the da830. Looks like one is needed. > > Hmm, I missed the original post of this but I'll look for it in a > minute. Yes, the correct solution for the "variant issue" would > be an additional entry in that table. I'll research the new revs > to see what else has changed and make a patch(es).
I didn't find a nice doc on TI's website describing the differences between rev A and B. Does anyone have such a doc that they can share with me? TIA, Mark -- _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
