From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kirkwood: added common config file mv-config.h
Date: Fri, 01 Oct 2010 08:35:32 +0200 [thread overview]
Message-ID: <4CA58134.8070605@free.fr> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D19A696EA26@SC-VEXCH4.marvell.com>
Le 01/10/2010 08:10, Prafulla Wadaskar a ?crit :
>
>
>> -----Original Message-----
>> From: Albert ARIBAUD [mailto:albert.aribaud at free.fr]
>> Sent: Thursday, September 30, 2010 9:05 PM
>> To: Prafulla Wadaskar
>> Cc: Rogan Dawes; u-boot at lists.denx.de; Ashish Karkare;
>> Prabhanjan Sarnaik
>> Subject: Re: [U-Boot] [PATCH] kirkwood: added common config
>> file mv-config.h
>>
>> Le 30/09/2010 16:33, Prafulla Wadaskar a ?crit :
>>
>>>>> +/*
>>>>> + * IDe Support on SATA port0
>>>>> + */
>>>>
>>>> IDe?
>>>
>>> I think Ide can be removed, right?
>
> I mean here s/Ide//g
>
>>
>> Do none of the boards have disks? At least openrd-base should
>> have IDE
>
> Guruplug, openrd_base and rd6281a have disk support
>
>> (and openrd-client as well if the patch to introduced it is
>> finally merged).
>>
>> So IDE should stay IMO, but the IDE stuff should be split into
>> board-specifics (basically the defines for the IDE0 and, if
>> it exists,
>> IDE1 base addresses) and SoC-specifics (basically everything
>> else, i.e.
>> all that is required for cmd_ide.c to compile).
>
> At this moment I only see the case with edminiv2 board where ATA bus0 is configured for sata port1.
> To extend this support for this board, we can undef and redef the respective macros.
>
> Whereas on all other boards it is one-to-one mapping.
>
> To me setting default configuration make more sense, that avoids code duplication in several files.
>
> Regards..
> Prafulla . .
Even if almost all boards have straight rather than cross mappings of
IDE0/IDE1 to SATA0/SATA1, not all of them have two busses (guruplug has
only one, and likewise another kirkwood based board I'm working on) so
half the boards would have to modify the settings anyway.
Besides, having each board explicitely telling what busses is has rather
than making it half implicit in the SoC common config file has two
advantages:
- someone looking at the board config file will immediately know without
if it supports IDE *and* how many busses it actually provides *and* how
they are mapped;
- boards will always declare "what is there" rather than declaring
either "what is there" or possibly "what isn't there even though the
common config said there would be".
After all, this is only one or two lines in the board config, and they
are always positively informative.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-10-01 6:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 17:53 [U-Boot] [PATCH] Kirkwood: dram_init is moved to dram.c Prafulla Wadaskar
2010-09-30 15:39 ` Heiko Schocher
2010-10-01 5:59 ` Prafulla Wadaskar
2010-10-01 6:17 ` Heiko Schocher
2010-10-01 8:00 ` Wolfgang Denk
2010-10-01 6:20 ` Albert ARIBAUD
2010-10-01 6:25 ` Prafulla Wadaskar
2010-10-01 7:53 ` Wolfgang Denk
2010-09-30 17:29 ` Wolfgang Denk
2010-10-01 7:23 ` Prafulla Wadaskar
2010-09-30 17:53 ` [U-Boot] [PATCH] kirkwood: added common config file mv-config.h Prafulla Wadaskar
2010-09-30 13:54 ` Rogan Dawes
2010-09-30 14:33 ` Prafulla Wadaskar
2010-09-30 15:26 ` Rogan Dawes
2010-09-30 15:35 ` Albert ARIBAUD
2010-10-01 6:10 ` Prafulla Wadaskar
2010-10-01 6:35 ` Albert ARIBAUD [this message]
2010-10-01 6:45 ` Prafulla Wadaskar
2010-09-30 17:54 ` [U-Boot] [PATCH] Kirkwood: Changes specific to ARM relocation support Prafulla Wadaskar
2010-09-30 15:40 ` Heiko Schocher
2010-09-30 16:21 ` Albert ARIBAUD
2010-09-30 17:50 ` Wolfgang Denk
2010-09-30 17:49 ` Wolfgang Denk
2010-09-30 22:06 ` Marek Vasut
2010-10-01 7:21 ` Prafulla Wadaskar
2010-09-30 17:34 ` 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=4CA58134.8070605@free.fr \
--to=albert.aribaud@free.fr \
--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