From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bear.ext.ti.com (bear.ext.ti.com [192.94.94.41]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id F12BEE013A2 for ; Wed, 17 Jul 2013 07:44:41 -0700 (PDT) Received: from dlelxv90.itg.ti.com ([172.17.2.17]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id r6HEidFn017995; Wed, 17 Jul 2013 09:44:39 -0500 Received: from DFLE73.ent.ti.com (dfle73.ent.ti.com [128.247.5.110]) by dlelxv90.itg.ti.com (8.14.3/8.13.8) with ESMTP id r6HEid29028121; Wed, 17 Jul 2013 09:44:39 -0500 Received: from DLEE11.ent.ti.com ([fe80::40fa:b936:da7c:d113]) by DFLE73.ent.ti.com ([fe80::c9be:a3a9:7cd8:c8b3%28]) with mapi id 14.02.0342.003; Wed, 17 Jul 2013 09:44:39 -0500 From: "Maupin, Chase" To: Brian Hutchinson Thread-Topic: [meta-ti] Which machine type to use for DaVinci DM6446 and TI816x? Thread-Index: AQHOgvEiWdXn0S1Jnku/HXXYrPWuq5lo8l4A Date: Wed, 17 Jul 2013 14:44:38 +0000 Message-ID: <7D46E86EC0A8354091174257B2FED1015965C076@DLEE11.ent.ti.com> References: <20130710164618.GD16407@edge> <7D46E86EC0A8354091174257B2FED1015965BBDC@DLEE11.ent.ti.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.247.5.50] MIME-Version: 1.0 Cc: "meta-ti@yoctoproject.org" Subject: Re: Which machine type to use for DaVinci DM6446 and TI816x? X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 14:44:42 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_7D46E86EC0A8354091174257B2FED1015965C076DLEE11entticom_" --_000_7D46E86EC0A8354091174257B2FED1015965C076DLEE11entticom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable From: Brian Hutchinson [mailto:b.hutchman@gmail.com] Sent: Wednesday, July 17, 2013 8:26 AM To: Maupin, Chase Cc: Dmytriyenko, Denys; meta-ti@yoctoproject.org Subject: Re: [meta-ti] Which machine type to use for DaVinci DM6446 and TI8= 16x? On Wed, Jul 17, 2013 at 9:14 AM, Maupin, Chase > wrote: From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Brian Hutchinson Sent: Wednesday, July 17, 2013 8:08 AM To: Dmytriyenko, Denys Cc: meta-ti@yoctoproject.org Subject: Re: [meta-ti] Which machine type to use for DaVinci DM6446 and TI8= 16x? On Wed, Jul 10, 2013 at 12:46 PM, Denys Dmytriyenko > 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 mas= ter)? 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 s= upport there. Is it not there just because nobody had hardware to test it? If so, I'm ga= me to add it with some guidance :) [CEM] Generally not too hard. You can often start with the old arago machi= ne and move that in with some cleanup. Then you will need to move/create t= he bootloader and kernel recipes as well, again looking for cleanup. That = should give you a basic working system. The main issue is that someone nee= ds to be signed up to keep those recipes working and up to date. That is w= hat is missing in most cases is a maitainer. Even better, for you use I would recommend looking at commit c586bd9a66 whi= ch is the one that removed these configs and then add back the pieces you n= eed. Thanks Chase, I kind of figured it was a (people) bandwidth problem. At t= he moment I'm using a custom board based on the ti816x so I don't need kern= el 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 sim= ply 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 t= he 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 acqu= ire 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 wh= at is involved. [CEM] Sure, ping if you have questions :) Regards, Brian --_000_7D46E86EC0A8354091174257B2FED1015965C076DLEE11entticom_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

 <= /p>

From: Brian Hu= tchinson [mailto:b.hutchman@gmail.com]
Sent: Wednesday, July 17, 2013 8:26 AM
To: Maupin, Chase
Cc: Dmytriyenko, Denys; meta-ti@yoctoproject.org
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 <<= a href=3D"mailto:chase.maupin@ti.com" target=3D"_blank">chase.maupin@ti.com= > wrote:

 

From: meta-= ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of Brian Hutchinson
Sent: Wednesday, July 17, 2013 8:08 AM
To: Dmytriyenko, Denys
Cc: me= ta-ti@yoctoproject.org
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 <denys@ti.com> wrote:

 

DM6446 is quite different from OMAP-L138. Both AM180x and DA850 ar= e 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 Dyla= n (or master)?  I've always had machine support for the branches I use= d 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 k= ernel recipes as well, again looking for cleanup.  That should give yo= u 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 recomm= end 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 (peop= le) bandwidth problem.  At the moment I'm using a custom board based o= n the ti816x so I don't need kernel or u-boot (already have those working f= or 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 m= achine support for that.

 

I'll check out that commit you mentioned and start c= oming up to speed on what is involved.

 <= /p>

[CEM] Sure, ping if you h= ave questions J

 <= /p>

 

Regards,

 

Brian

 

--_000_7D46E86EC0A8354091174257B2FED1015965C076DLEE11entticom_--