From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 04/11 v1] ARM: OMAP3: Add assembly startup and sys_info common files
Date: Thu, 18 Sep 2008 09:15:52 +0200 [thread overview]
Message-ID: <20080918071553.03148248D3@gemini.denx.de> (raw)
In-Reply-To: <48CFF803.3080105@googlemail.com>
Dear Dirk Behme,
In message <48CFF803.3080105@googlemail.com> you wrote:
>
> 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/
... which probably means code duplication.
> *or*
>
> b)
>
> cpu/arm_cortexa8/omap3
> cpu/arm_cortexa8/xxx
>
> What's better?
Instead, we might probably have just a "cpu/arm_cortexa8/" with common
code for "omap3" and "xxx" ?
> 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
I think we shoud try and start without the xxx part.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The human race is a race of cowards; and I am not only marching in
that procession but carrying a banner. - Mark Twain
next prev parent reply other threads:[~2008-09-18 7:15 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
2008-09-18 7:15 ` Wolfgang Denk [this message]
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=20080918071553.03148248D3@gemini.denx.de \
--to=wd@denx.de \
--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