All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: Which machine type to use for DaVinci DM6446 and TI816x?
Date: Thu, 11 Jul 2013 14:36:07 -0400	[thread overview]
Message-ID: <20130711183607.GR18647@edge> (raw)
In-Reply-To: <CAFZh4h_+1hgc9SJ1WrNgDL07Lj7JjwfHZLecf+RrWcVEyeprPQ@mail.gmail.com>

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


  reply	other threads:[~2013-07-11 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 15:21 Which machine type to use for DaVinci DM6446 and TI816x? Brian Hutchinson
2013-07-10 16:46 ` Denys Dmytriyenko
2013-07-10 17:28   ` Brian Hutchinson
2013-07-11 18:36     ` Denys Dmytriyenko [this message]
2013-07-17 13:07   ` Brian Hutchinson
2013-07-17 13:14     ` Maupin, Chase
2013-07-17 13:25       ` Brian Hutchinson
2013-07-17 14:44         ` Maupin, Chase
2013-07-17 15:04           ` Brian Hutchinson
2013-07-17 15:05             ` Brian Hutchinson
2013-07-17 15:08               ` Brian Hutchinson
2013-07-23 17:28         ` Denys Dmytriyenko
2013-07-23 17:44           ` Brian Hutchinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130711183607.GR18647@edge \
    --to=denys@ti.com \
    --cc=b.hutchman@gmail.com \
    --cc=meta-ti@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.