From: ryan@bluewatersys•com (Ryan Mallon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/5] SPEAR3xx: Rename register/irq defines to remove naming conflicts
Date: Mon, 14 Jun 2010 22:17:59 +1200 [thread overview]
Message-ID: <4C1601D7.1080404@bluewatersys.com> (raw)
In-Reply-To: <4C15C22A.7070408@st.com>
Viresh KUMAR wrote:
> On 6/14/2010 11:06 AM, Ryan Mallon wrote:
>> The goal of the patch series is to allow all a single kernel to have
>> support for all of the spear platforms, ie CONFIG_MACH_SPEAR300,
>> CONFIG_MACH_SPEAR310 and CONFIG_MACH_SPEAR320 can all be set.
>>
>> The current code has duplicate defines in
>> arch/arm/mach-spear3xx/include/mach/spear3[012]0.h which means that
>> these three files cannot be included at once (they are included from
>> arch/arm/mach-spear3xx/include/mach/spear.h).
>
> I understood what you did, but i am not sure how will it actually work.
> I tried to look into kernel source but couldn't find much.
>
> Suppose all three machines/boards are selected and we got one kernel.
> Then how should we tell the kernel which machines init routine to be called.
> I suppose through uboot only, but not sure how it internally works.
>
> Can you please help me understand that?
The machine id is passed in register r1 by the boot loader, which
matches the id in the MACHINE_START descriptors in the board files. Many
of the other arm sub-architectures already allow multiple
boards/implementations to be compiled into a single kernel and selected
at runtime.
~Ryan
next prev parent reply other threads:[~2010-06-14 10:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 6:05 [PATCH 0/5] SPEAr3xx: Unify build of SPEAr3xx platforms Ryan Mallon
2010-06-05 6:05 ` [PATCH 1/5] SPEAr3xx: Make local structres static Ryan Mallon
2010-06-14 5:16 ` Viresh KUMAR
2010-06-14 5:31 ` Ryan Mallon
2010-06-14 5:41 ` Viresh KUMAR
2010-06-05 6:05 ` [PATCH 2/5] SPEAR3xx: Rename register/irq defines to remove naming conflicts Ryan Mallon
2010-06-14 5:18 ` Viresh KUMAR
2010-06-14 5:36 ` Ryan Mallon
2010-06-14 5:46 ` Viresh KUMAR
2010-06-14 10:17 ` Ryan Mallon [this message]
2010-08-10 5:12 ` viresh kumar
2010-08-10 20:50 ` Ryan Mallon
2010-08-11 9:14 ` viresh kumar
2010-08-11 20:43 ` Ryan Mallon
2010-08-12 4:40 ` viresh kumar
2010-06-05 6:05 ` [PATCH 3/5] SPEAr3xx: Rework pmx_dev code to remove conflicts Ryan Mallon
2010-06-14 5:21 ` Viresh KUMAR
2010-06-05 6:05 ` [PATCH 4/5] SPEAr3xx: Rework KConfig to allow all boards to be compiled in Ryan Mallon
2010-06-05 6:05 ` [PATCH 5/5] SPEAr3xx: Replace defconfigs with single unfied defconfig Ryan Mallon
2010-06-13 22:51 ` [PATCH 0/5] SPEAr3xx: Unify build of SPEAr3xx platforms Ryan Mallon
2010-06-15 5:32 ` Viresh KUMAR
2010-06-15 6:49 ` Ryan Mallon
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=4C1601D7.1080404@bluewatersys.com \
--to=ryan@bluewatersys$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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