From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4055AE013A2 for ; Wed, 17 Jul 2013 08:08:59 -0700 (PDT) Received: by mail-oa0-f45.google.com with SMTP id j1so2650555oag.4 for ; Wed, 17 Jul 2013 08:08:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hnOeUzFKbRhehIaLCDRQ8LABuyzhIsjHp3dgHIOpbI0=; b=exvP+cbZtguMNJJ+vUuzhvmX6bR/JeJxUIlAUNvy1zUm8gOToxO1irLBeQLILbx35l d0fR4xDu1ssFJJP0a4nlFEoSyMu21Q9ph63OFRUdq9aTedKUTp/HDz9Kc5HjnGHolTgg WO8RIgQTSEn8qBY2tpiH/zuftrkf8eGUKrt4557HKU7gj24eOD8lN73sBY5fCljypRhk CnIdJr1rBb8GWHZtTzVLEUMJTjoaeBB4Z5kscd/mvZdb0iLqTdnNEPnx4YTpi7uaad5t i6iOpZW/yeFtVuJLQ3ovk0maMIjsXQAax4clUginphIOJ1GB7npzlhJ+htiV8vSo5ZEf m4eg== MIME-Version: 1.0 X-Received: by 10.60.37.74 with SMTP id w10mr8732536oej.30.1374073739207; Wed, 17 Jul 2013 08:08:59 -0700 (PDT) Received: by 10.60.26.225 with HTTP; Wed, 17 Jul 2013 08:08:59 -0700 (PDT) In-Reply-To: References: <20130710164618.GD16407@edge> <7D46E86EC0A8354091174257B2FED1015965BBDC@DLEE11.ent.ti.com> <7D46E86EC0A8354091174257B2FED1015965C076@DLEE11.ent.ti.com> Date: Wed, 17 Jul 2013 11:08:59 -0400 Message-ID: From: Brian Hutchinson To: "Maupin, Chase" 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 15:09:00 -0000 Content-Type: multipart/alternative; boundary=089e013cc49c1ee84b04e1b679e3 --089e013cc49c1ee84b04e1b679e3 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jul 17, 2013 at 11:05 AM, Brian Hutchinson wrote: > On Wed, Jul 17, 2013 at 11:04 AM, Brian Hutchinson wrote: > >> On Wed, Jul 17, 2013 at 10:44 AM, Maupin, Chase wrote: >> >>> ** ** >>> >>> *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 TI816x?**** >>> >>> ** ** >>> >>> 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 TI816x?**** >>> >>> **** >>> >>> 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 >>> 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 J**** >>> >>> >>> >> Will do. In the mean time ... just to kick the can further down the road >> so I can get "something" built so I can try a rootfs for my system ... I >> did a fresh clone of yocto master, meta-ti master, and meta-openembedded >> master and set machine type to beaglebone. Bitbake of core-image-minimal >> results in: >> >> hutch@neo:~/yocto_master_beaglebone/poky/build$ bitbake >> core-image-minimal >> WARNING: Host distribution "Debian-7.1" has not been validated with this >> version of the build system; you may possibly experience unexpected >> failures. It is recommended that you use a tested distribution. >> ERROR: This recipe does not have the LICENSE field set >> (ti-hw-bringup-image) >> ERROR: This recipe does not have the LICENSE field set (cloud9-gfx-image) >> ERROR: This recipe does not have the LICENSE field set (cloud9-image) >> ERROR: This recipe does not have the LICENSE field set >> (cloud9-gnome-image) >> ERROR: Unable to parse >> /home/hutch/yocto_master_beaglebone/poky/meta-ti/recipes-misc/images/ >> ti-hw-bringup-image.bb: Exited with "1" >> >> | ETA: --:--:-- >> ERROR: Command execution failed: Exited with 1 >> >> Summary: There was 1 WARNING message shown. >> Summary: There were 6 ERROR messages shown, returning a non-zero exit >> code. >> >> Guess I need to do some searching through the archives to see what this >> new LICENSE stuff is all about. >> >> Regards, >> >> Brian >> >> > Ah, forgot BBMASK ... maybe that is it. > > Yep, forgot BBMASK = "meta-ti/recipes-misc". Hate it when that happens. Sorry for the noise. --089e013cc49c1ee84b04e1b679e3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Jul 17, 2013 at 11:05 AM, Brian Hutchinson <b.hutchman@gmail.co= m> wrote:
On Wed, Jul 17, 2013 at 11:04 AM, B= rian Hutchinson <b.hutchman@gmail.com> wrote:
On Wed, Jul 17, 2013 at 10:44 AM, Maupin, Chase <chase.maupin@= ti.com> wrote:

=A0<= /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?

=A0

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:

=A0<= /p>

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?

=A0

On Wed, Jul 10, 2013 at 12:46 PM, Denys Dmytriyenko = <denys@ti.com> = wrote:

=A0

DM6446 is quite different from OMAP-L138. Both AM180= x and DA850 are just
derivatives of OMAP-L138.

Anyway, DM6446 is no longer supported, as it's a very old platform.<= /u>



> 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. =A0My gut= says use
> am1808-evm.conf but I thought I should ask to be sure.

--
Denys

=A0

So how hard is it to get ti816x machine support move= d up into Dylan (or master)? =A0I'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.

=A0

Is it not there just because nobody had hardware to = test it? =A0If so, I'm game to add it with some guidance :)

=A0<= /p>

[CEM] Generally not too h= ard.=A0 You can often start with the old arago machine and move that in wit= h some cleanup.=A0 Then you will need to move/create the bootloader and kern= el recipes as well, again looking for cleanup.=A0 That should give you a ba= sic working system.=A0 The main issue is that someone needs to be signed up= to keep those recipes working and up to date.=A0 That is what is missing in most cases is a maitainer.

=A0<= /p>

Even better, for you use = I would recommend looking at commit c586bd9a66 which is the one that remove= d these configs and then add back the pieces you need.<= /p>

=A0<= /p>

=A0

Thanks Chase, =A0I kind of figured it was a (people)= bandwidth problem. =A0At 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 packa= ges built using all the Cortex-A8 flags. =A0I guess I could be lazy and jus= t 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. =A0Also, there have been several revs of silicon for tha= t part and I'm about to acquire the most up-to-date EVM so I could add = machine support for that.

=A0

I'll check out that commit you mentioned and sta= rt coming up to speed on what is involved.

=A0<= /p>

[CEM] Sure, ping if= you have questions J


<= div>
Will do. =A0In the mean time ... just to kic= k the can further down the road so I can get "something" built so= I can try a rootfs for my system ... I did a fresh clone of yocto master, = meta-ti master, and meta-openembedded master and set machine type to beagle= bone. =A0Bitbake of core-image-minimal results in:

hutch@neo:~/yocto_master_beaglebone/poky/build$ bitbake= core-image-minimal
WARNING: Host distribution "Debian-7.1&q= uot; has not been validated with this version of the build system; you may = possibly experience unexpected failures. It is recommended that you use a t= ested distribution.
ERROR: This recipe does not have the LICENSE field set (ti-hw-bringup-= image)
ERROR: This recipe does not have the LICENSE field set (cl= oud9-gfx-image)
ERROR: This recipe does not have the LICENSE fiel= d set (cloud9-image)
ERROR: This recipe does not have the LICENSE field set (cloud9-gnome-i= mage)
ERROR: Unable to parse /home/hutch/yocto_master_beaglebone/= poky/meta-ti/recipes-misc/images/ti-hw-bringup-image.bb: Exited with "1" =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| ETA: =A0-= -:--:--
ERROR: Command execution failed: Exited with 1

Summary: There was 1 WARNING message shown.
Summary: There were= 6 ERROR messages shown, returning a non-zero exit code.

Guess I need to do some searching through the archives to see wh= at this new LICENSE stuff is all about.

Regards,

Brian
=A0
Ah, forgot BBMASK ... maybe that is it.=A0

Yep, forgot BBMASK =3D "meta-ti/recipes-misc". =A0Hate it when t= hat happens. =A0Sorry for the noise.
=A0

--089e013cc49c1ee84b04e1b679e3--