From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 11/12] SPEAr : Support added for SPEAr310 board
Date: Sat, 16 Jan 2010 13:20:48 -0600 [thread overview]
Message-ID: <4B521190.4050709@windriver.com> (raw)
In-Reply-To: <83d1d72b1001160926u61030ddfj2115aeda879ba2db@mail.gmail.com>
Vipin Kumar wrote:
> On Sat, Jan 16, 2010 at 8:40 PM, Tom <Tom.Rix@windriver.com> wrote:
>> Vipin Kumar wrote:
>>> Hello Tom,
>>>
>>>>>> <snip>
>>>>>>
>>>>>> +#include <asm/arch/spr_defs.h>
>>>>>> +#include <asm/arch/spr_misc.h>
>>>>>> +#include <asm/arch/spr_nand.h>
>>>>>> +
>>>>>> +int board_init(void)
>>>>>> +{
>>>>>> + return spear_board_init(MACH_TYPE_SPEAR300);
>>>>>> Does this need a new mach type ?
>>>>>> I see there isn't a SPEAR310 define in mach-types.
>>>>> Actually, spear310 and spear320 are variants of a base version spear300
>>>>> This is why we are using a single mach type
>>>>>
>>>> Ok.
>>>> Then the 310 and 320 board *.c files can be combined into 300 board files
>>>> These look like they are copies of the 300 file.
>>>> Tom
>>>>
>>> Please find the patchset v5 for SPEAr support on the mailing list
>>> It contains all your suggested changes
>>> Please consider it for mainline inclusion
>>>
>> I see in v5 that the 300,310,320 boards are still in separate files.
>> These all look like copies and could be combined.
>>
>> Do you expect there will be a need in the future to add unique code
>> to each of these board files?
>> If not, please look into combining them.
>>
>> I will provide feedback on the other files shortly.
>>
>> Tom
>>
>
> Although all three are based on one chip but sp300, sp310 and
> sp320 are different SoCs and support different IPs.
> Yes, board files are copies of each other as of now but may diverge in
> future
> I would rather create different mach ids rather than combining them
> into one.
Ok.
Fine to leave them as-is.
Tom
>
> Regards
> Vipin
next prev parent reply other threads:[~2010-01-16 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:41 [U-Boot] [PATCH v4 11/12] SPEAr : Support added for SPEAr310 board Tom
2010-01-14 11:15 ` Vipin KUMAR
2010-01-14 15:55 ` Tom
2010-01-15 17:15 ` Vipin Kumar
2010-01-16 15:10 ` Tom
2010-01-16 17:26 ` Vipin Kumar
2010-01-16 19:20 ` Tom [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-11 11:15 [U-Boot] [PATCH v4 00/12] Support for SPEAr SoCs Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 01/12] SPEAr : Adding README.spear in doc Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 02/12] SPEAr : Adding basic SPEAr architecture support Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 03/12] SPEAr : i2c driver support added for SPEAr SoCs Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 04/12] SPEAr : smi driver support " Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 05/12] SPEAr : nand " Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 06/12] SPEAr : usbd " Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 07/12] SPEAr : Support added for SPEAr600 board Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 08/12] SPEAr : Support for HW mac id read/write from i2c mem Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 09/12] SPEAr : Support added for SPEAr300 board Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 10/12] SPEAr : emi controller initialization for CFI driver support Vipin KUMAR
2010-01-11 11:15 ` [U-Boot] [PATCH v4 11/12] SPEAr : Support added for SPEAr310 board Vipin KUMAR
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=4B521190.4050709@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