From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 04/11 v1] ARM: OMAP3: Add assembly startup and sys_info common files
Date: Tue, 16 Sep 2008 20:16:35 +0200 [thread overview]
Message-ID: <48CFF803.3080105@googlemail.com> (raw)
In-Reply-To: <59b21cf20809142352u63de215ema809812800aa21ec@mail.gmail.com>
Magnus Lilja wrote:
> Hi
>
> 2008/9/14 <dirk.behme@googlemail.com>:
>
>>From: Dirk Behme <dirk.behme@gmail.com>
>>
>>Add assembly startup and sys_info common files
>>
>>Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>>
>>---
>> cpu/omap3/Makefile | 44 +++
>> cpu/omap3/config.mk | 36 +++
>> cpu/omap3/lowlevel_init.S | 360 +++++++++++++++++++++++++++++++
>> cpu/omap3/start.S | 522 ++++++++++++++++++++++++++++++++++++++++++++++
>> cpu/omap3/sys_info.c | 314 +++++++++++++++++++++++++++
>
>
> Is omap3 is a cpu? Isn't OMAP3 a SoC-family containing ARM Cortex-A8
> CPUs and the directory therefore should be something like
> cpu/arm_cortexa8/omap3 or cpu/cortexa8/omap3?
Yes, from strict technical point of view you are correct. Cortex A8 is
the 'CPU' and OMAP3 is the SoC.
But what do we win adding an additional directory layer
cpu/arm_cortexa8/omap3? Let's assume we will see an additional
Cortex-A8 core xxx in the future. Then we would have
a)
cpu/omap3/
cpu/xxx/
*or*
b)
cpu/arm_cortexa8/omap3
cpu/arm_cortexa8/xxx
What's better?
Anyway, I will do what is wanted here :)
If U-Boot maintainers want cpu/arm_cortexa8/xxx, I wonder if we could
do this using git to move the files once the patches are applied? It
seems easier to move the files to an other directory using git instead
of flooding this list with new patches just to change directories. Any
proposals?
Thanks
Dirk
next prev parent reply other threads:[~2008-09-16 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 9:50 [U-Boot] [PATCH 04/11 v1] ARM: OMAP3: Add assembly startup and sys_info common files dirk.behme at googlemail.com
2008-09-15 6:52 ` Magnus Lilja
2008-09-16 18:16 ` Dirk Behme [this message]
2008-09-18 7:15 ` Wolfgang Denk
2008-09-20 16:25 ` Dirk Behme
2008-10-13 23:21 ` 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=48CFF803.3080105@googlemail.com \
--to=dirk.behme@googlemail.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