From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Uboot-V2: ARM: towards a common start-arm.S
Date: Mon, 17 Mar 2008 17:32:10 -0500 [thread overview]
Message-ID: <47DEF16A.3070406@gmail.com> (raw)
Hi Sascha,
I think we dont have a seperate list for uboot-v2, so, just wanted to
know the opinion of having a single arch/arm/cpu/start-arm.S instead of
multiple start-arm files. essentially providing hooks to arch,soc,board
specific preinits can allow us to reuse major chunk of code..
I have attached a sample start-arm.S (modified from start-arm920t.S) as
reference.
Do let me know your comments and view as to how the initial handling can
be made abstract enough to plug into requirements of future SOCs, boards
etc. I am looking not to mash in #ifdef ARCH_XYZ for each of the SOC
implementation I plan on doing.
Regards,
Nishanth Menon
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: start-arm.S
Url: http://lists.denx.de/pipermail/u-boot/attachments/20080317/7002cf09/attachment.txt
next reply other threads:[~2008-03-17 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 22:32 Nishanth Menon [this message]
2008-03-18 12:19 ` [U-Boot-Users] Uboot-V2: ARM: towards a common start-arm.S Sascha Hauer
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=47DEF16A.3070406@gmail.com \
--to=menon.nishanth@gmail.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 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.