All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maupin, Chase" <chase.maupin@ti.com>
To: Brian Hutchinson <b.hutchman@gmail.com>,
	"Dmytriyenko, Denys" <denys@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: Which machine type to use for DaVinci DM6446 and	TI816x?
Date: Wed, 17 Jul 2013 13:14:01 +0000	[thread overview]
Message-ID: <7D46E86EC0A8354091174257B2FED1015965BBDC@DLEE11.ent.ti.com> (raw)
In-Reply-To: <CAFZh4h-W=557rBxsehQhzpgJuxk+Z5BmKeboNk2eAGnBt8vBUQ@mail.gmail.com>

[-- 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 --]

  reply	other threads:[~2013-07-17 13:14 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
2013-07-17 13:07   ` Brian Hutchinson
2013-07-17 13:14     ` Maupin, Chase [this message]
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=7D46E86EC0A8354091174257B2FED1015965BBDC@DLEE11.ent.ti.com \
    --to=chase.maupin@ti.com \
    --cc=b.hutchman@gmail.com \
    --cc=denys@ti.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.