Which machine type to use for DaVinci DM6446 and TI816x?

Which machine type to use for DaVinci DM6446 and TI816x?

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]

Hi,

I have to support DaVinci DM6446, AM1808, OMAP-L138 and C6A816x which has
turned into TI816x in later silicon releases.

I'm trying to figure out what conf/machine to use for the above SoC's.

In Denzil, I see am389x-evm.conf and c6a816x-evm.conf and both include the
same ti816x.inc file, but I do not see support for this machine in Danny or
Dylan (unless I'm missing something).  How should I go about using Dylan
with the ti816x?

For DaVinci DM6446, I don't see an obvious machine type that supports it
but I know that the DM6446, AM1808 and OMAP-L138 are all in the same ARM926
family (da850) so should I be using the am1808-evm.conf for DaVinci DM6446?

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.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 1101 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Denys Dmytriyenko]

On Tue, Jul 09, 2013 at 11:21:13AM -0400, Brian Hutchinson wrote:
> Hi,

Hey, Brian,

Long time no see!


> I have to support DaVinci DM6446, AM1808, OMAP-L138 and C6A816x which has
> turned into TI816x in later silicon releases.
> 
> I'm trying to figure out what conf/machine to use for the above SoC's.
> 
> In Denzil, I see am389x-evm.conf and c6a816x-evm.conf and both include the
> same ti816x.inc file, but I do not see support for this machine in Danny or
> Dylan (unless I'm missing something).  How should I go about using Dylan
> with the ti816x?

http://thread.gmane.org/gmane.linux.embedded.yocto.meta-ti/1544


> For DaVinci DM6446, I don't see an obvious machine type that supports it
> but I know that the DM6446, AM1808 and OMAP-L138 are all in the same ARM926
> family (da850) so should I be using the am1808-evm.conf for DaVinci DM6446?

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

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]

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

> On Tue, Jul 09, 2013 at 11:21:13AM -0400, Brian Hutchinson wrote:
> > Hi,
>
> Hey, Brian,
>
> Long time no see!
>
>
> > I have to support DaVinci DM6446, AM1808, OMAP-L138 and C6A816x which has
> > turned into TI816x in later silicon releases.
> >
> > I'm trying to figure out what conf/machine to use for the above SoC's.
> >
> > In Denzil, I see am389x-evm.conf and c6a816x-evm.conf and both include
> the
> > same ti816x.inc file, but I do not see support for this machine in Danny
> or
> > Dylan (unless I'm missing something).  How should I go about using Dylan
> > with the ti816x?
>
> http://thread.gmane.org/gmane.linux.embedded.yocto.meta-ti/1544
>
>
> > For DaVinci DM6446, I don't see an obvious machine type that supports it
> > but I know that the DM6446, AM1808 and OMAP-L138 are all in the same
> ARM926
> > family (da850) so should I be using the am1808-evm.conf for DaVinci
> DM6446?
>
> 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
>

Hey Denys,

Wow, I wasn't expecting support to be dropped.  I'm sure there is still a
bunch of people using it.  I guess I could maybe maintain it if someone
would give pointers on how to go about it.

OK, so how about this ... I use the same u-boot and kernel that I'm
currently using (but built with the same toolchain to build the rootfs ...
meta-toolchain) but use am180x-evm to build the rootfs & packages of other
stuff I need?  I mainly need to have the packages kept relatively up to
date (security patches etc.).

Do you see anything wrong with that approach?  Same ABI right?

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 2839 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Denys Dmytriyenko]

On Wed, Jul 10, 2013 at 01:28:55PM -0400, Brian Hutchinson wrote:
> On Wed, Jul 10, 2013 at 12:46 PM, Denys Dmytriyenko <denys@ti.com> wrote:
> 
> > On Tue, Jul 09, 2013 at 11:21:13AM -0400, Brian Hutchinson wrote:
> > > Hi,
> >
> > Hey, Brian,
> >
> > Long time no see!
> >
> >
> > > I have to support DaVinci DM6446, AM1808, OMAP-L138 and C6A816x which has
> > > turned into TI816x in later silicon releases.
> > >
> > > I'm trying to figure out what conf/machine to use for the above SoC's.
> > >
> > > In Denzil, I see am389x-evm.conf and c6a816x-evm.conf and both include
> > the
> > > same ti816x.inc file, but I do not see support for this machine in Danny
> > or
> > > Dylan (unless I'm missing something).  How should I go about using Dylan
> > > with the ti816x?
> >
> > http://thread.gmane.org/gmane.linux.embedded.yocto.meta-ti/1544
> >
> >
> > > For DaVinci DM6446, I don't see an obvious machine type that supports it
> > > but I know that the DM6446, AM1808 and OMAP-L138 are all in the same
> > ARM926
> > > family (da850) so should I be using the am1808-evm.conf for DaVinci
> > DM6446?
> >
> > 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
> >
> 
> Hey Denys,
> 
> Wow, I wasn't expecting support to be dropped.  I'm sure there is still a
> bunch of people using it.  I guess I could maybe maintain it if someone
> would give pointers on how to go about it.
> 
> OK, so how about this ... I use the same u-boot and kernel that I'm
> currently using (but built with the same toolchain to build the rootfs ...
> meta-toolchain) but use am180x-evm to build the rootfs & packages of other
> stuff I need?  I mainly need to have the packages kept relatively up to
> date (security patches etc.).
> 
> Do you see anything wrong with that approach?  Same ABI right?

Brian,

Unfortunately, keeping support in meta-ti is often seen as entitlement to 
continuously forward-port features to all the new SW components - u-boot, 
kernel, IPC, etc. But that is not true for some platforms, if there are no 
development resources allocated to do so. So, some things get dropped due to 
limited bandwidth, sorry.

Your suggestion might work and you are welcome to try it out. Please let me 
know if you'd be interested in maintaining any of those outdated platforms 
going forward. Thanks.

-- 
Denys

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

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 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 :)

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 1404 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Maupin, Chase]

[-- Attachment #1: Type: text/plain, Size: 1750 bytes --]


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 <denys@ti.com<mailto:denys@ti.com>> 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.


Regards,

Brian



[-- Attachment #2: Type: text/html, Size: 6056 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 2824 bytes --]

On Wed, Jul 17, 2013 at 9:14 AM, Maupin, Chase <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:* 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 <denys@ti.com> 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.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 5631 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Maupin, Chase]

[-- Attachment #1: Type: text/plain, Size: 3029 bytes --]


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 <chase.maupin@ti.com<mailto:chase.maupin@ti.com>> wrote:

From: meta-ti-bounces@yoctoproject.org<mailto:meta-ti-bounces@yoctoproject.org> [mailto: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<mailto: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 <denys@ti.com<mailto:denys@ti.com>> 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


[-- Attachment #2: Type: text/html, Size: 10227 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 4746 bytes --]

On Wed, Jul 17, 2013 at 10:44 AM, Maupin, Chase <chase.maupin@ti.com> 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 <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:* 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 <denys@ti.com> 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

[-- Attachment #2: Type: text/html, Size: 9455 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 5041 bytes --]

On Wed, Jul 17, 2013 at 11:04 AM, Brian Hutchinson <b.hutchman@gmail.com>wrote:

> On Wed, Jul 17, 2013 at 10:44 AM, Maupin, Chase <chase.maupin@ti.com>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 <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:* 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 <denys@ti.com> 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.

[-- Attachment #2: Type: text/html, Size: 9896 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 5310 bytes --]

On Wed, Jul 17, 2013 at 11:05 AM, Brian Hutchinson <b.hutchman@gmail.com>wrote:

> On Wed, Jul 17, 2013 at 11:04 AM, Brian Hutchinson <b.hutchman@gmail.com>wrote:
>
>> On Wed, Jul 17, 2013 at 10:44 AM, Maupin, Chase <chase.maupin@ti.com>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 <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:* 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 <denys@ti.com>
>>> 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.

[-- Attachment #2: Type: text/html, Size: 10404 bytes --]

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Denys Dmytriyenko]

On Wed, Jul 17, 2013 at 09:25:37AM -0400, Brian Hutchinson wrote:
> On Wed, Jul 17, 2013 at 9:14 AM, Maupin, Chase <chase.maupin@ti.com> wrote:
> 
> > [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.****
> 
> 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.

Brian,

So, are you willing to become a maintainer for that platform? I've heard from 
several other people in the community before, who expressed interest, but 
never came back with the final decision yet... Let me know what you decide. 
Thanks.

-- 
Denys

Re: Which machine type to use for DaVinci DM6446 and TI816x?

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]

On Tue, Jul 23, 2013 at 1:28 PM, Denys Dmytriyenko <denys@ti.com> wrote:

>
> Brian,
>
> So, are you willing to become a maintainer for that platform? I've heard
> from
> several other people in the community before, who expressed interest, but
> never came back with the final decision yet... Let me know what you decide.
> Thanks.
>
>
>
I'm still going to look into it to see what all is involved before I
commit.  I don't want to say I'll do it and then suck at it if you know
what I mean.  I think the best long term solution for us (with my employee
hat on) is to mainline as much ti816x stuff as possible as it will only
make our life easier since we have products based on that platform.  What
really needs to happen is for the kernel to get mainlined.  I've seen some
folks working on that on the ARM list but haven't looked at their progress
in a while.

For now in order to meet some deadlines, I've simply been building
filesystems/packages with beaglebone as the machine type.  Hopefully that
will allow me to put out enough fires to have time to look into it more.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 1556 bytes --]