public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/4] add TI DA8xx support: Add new directory for da8xx cpu functions
Date: Sat, 24 Oct 2009 19:34:15 -0500	[thread overview]
Message-ID: <4AE39D07.7020302@windriver.com> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D9380761E@dlee01.ent.ti.com>

Paulraj, Sandeep wrote:
> 
>> Nick Thompson wrote:
>>> Add new directory for da8xx cpu functions.
>>>
>>> Provides initial support for TI OMAP-L1x/DA8xx SoC devices.
>>> See http://www.ti.com
>>>
>>> Provides:
>>> Low level initialisation.
>>> System clock API.
>>> Timer control.
>>> System reset.
>>
>> It looks like this patch is duplicating much of what is already
>> in arm926ejs/davinci.  Unless there is a really good reason
>> for a separate cpu dir, this patch should change to merge
>> with davinci.
> Tom,
> 
> There was a similar discussion in the Linux-Davinci ML when DA8xx was being added. Finally as things stand currently, we re use most of the stuff from DaVinci for DA8xx, i.e DM355,Dm365,DM6467,DM6446 and DA8xx are all considered DaVinci SOC's
> 
> If we do the same thing in U-Boot, then the DA8xx patches submitted will need re organization.

Yes, I agree.

The more code I reviewed side-by-side with the u-boot davinci, the
more this seems moving da8xx into davinci is the way to go.
The big change is to get the memory map in hardware.h

The cleanups that Nick did for the common code should be used.

Tom

  reply	other threads:[~2009-10-25  0:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 10:34 [U-Boot] [PATCH v2 1/4] add TI DA8xx support: Add new directory for da8xx cpu functions Nick Thompson
2009-10-24 22:37 ` Tom
2009-10-24 22:48   ` Paulraj, Sandeep
2009-10-25  0:34     ` Tom [this message]
2009-10-26 21:33     ` Wolfgang Denk

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=4AE39D07.7020302@windriver.com \
    --to=tom.rix@windriver.com \
    --cc=u-boot@lists.denx.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox