From: Brian Hutchinson [mailto:[email protected]] Sent: Wednesday, July 17, 2013 8:26 AM To: Maupin, Chase Cc: Dmytriyenko, Denys; [email protected] Subject: Re: [meta-ti] Which machine type to use for DaVinci DM6446 and TI816x?
On Wed, Jul 17, 2013 at 9:14 AM, Maupin, Chase <[email protected]<mailto:[email protected]>> wrote: From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Brian Hutchinson Sent: Wednesday, July 17, 2013 8:08 AM To: Dmytriyenko, Denys Cc: [email protected]<mailto:[email protected]> Subject: Re: [meta-ti] Which machine type to use for DaVinci DM6446 and TI816x? On Wed, Jul 10, 2013 at 12:46 PM, Denys Dmytriyenko <[email protected]<mailto:[email protected]>> wrote: DM6446 is quite different from OMAP-L138. Both AM180x and DA850 are just derivatives of OMAP-L138. Anyway, DM6446 is no longer supported, as it's a very old platform. > I've always used Arago or Angstrom for DM6446 support in the past and so > I'm not sure which .conf I should be using with meta-ti. My gut says use > am1808-evm.conf but I thought I should ask to be sure. -- Denys So how hard is it to get ti816x machine support moved up into Dylan (or master)? I've always had machine support for the branches I used in the past ... now I find myself needing Dylan or even master and there is no ti816x support there. Is it not there just because nobody had hardware to test it? If so, I'm game to add it with some guidance :) [CEM] Generally not too hard. You can often start with the old arago machine and move that in with some cleanup. Then you will need to move/create the bootloader and kernel recipes as well, again looking for cleanup. That should give you a basic working system. The main issue is that someone needs to be signed up to keep those recipes working and up to date. That is what is missing in most cases is a maitainer. Even better, for you use I would recommend looking at commit c586bd9a66 which is the one that removed these configs and then add back the pieces you need. Thanks Chase, I kind of figured it was a (people) bandwidth problem. At the moment I'm using a custom board based on the ti816x so I don't need kernel or u-boot (already have those working for the board and since the kernel for this platform was never mainlined, it doesn't have much churn) but simply need packages built using all the Cortex-A8 flags. I guess I could be lazy and just build for Beagleboard or something since the ABI's would be the same but I thought I would ask how to go about it the right way. Also, there have been several revs of silicon for that part and I'm about to acquire the most up-to-date EVM so I could add machine support for that. I'll check out that commit you mentioned and start coming up to speed on what is involved. [CEM] Sure, ping if you have questions :) Regards, Brian
_______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
