public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rogan Dawes <rogan@dawes.za.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V7 0/4] Add disk support to orion5x and edminiv2
Date: Thu, 05 Aug 2010 17:35:35 +0200	[thread overview]
Message-ID: <4C5ADA47.1020100@dawes.za.net> (raw)
In-Reply-To: <4C5AD4F7.2030604@free.fr>

On 2010/08/05 5:12 PM, Albert ARIBAUD wrote:
> Le 05/08/2010 16:28, Rogan Dawes a ?crit :
>> On 2010/08/05 4:11 PM, Albert ARIBAUD wrote:
>>> Rogan, what other code do you think you'd be duplicating?
>>>
>>> Amicalement,
>>
>> In truth, I was really thinking only of the config files, not really the
>> code per se.
>>
>> I suppose that there is not really that much else that really is common.
>>
>> Rogan
>
> As for the configs, some u-boot boards do commonalize, see for instance
> include/configs/spear*.h. That makes sense because there is a board
> family, with a common HW design and common external components.
>
> For instance, the recently submitted patch for the kirkwood-based openrd
> family could probably commonalize since most of the OpenRD Base and
> OpenRD Client HW design is shared, and I assume Ultimate reuses it a lot
> too.
>
> In our case, the boards are from different manufacturers, so
> commonalization seems less obvious to me, except for MV88E1116 if both
> boards have it, but the config for it is a single define
> (CONFIG_RESET_PHY_R) which makes putting it in a common config header
> overkill (but commonalization of reset code would make sense though).
>
> Amicalement,

The DNS323 uses the Marvell 88E1111, but it is working with the same 
config as yours, so I suppose they are compatible.

I was really thinking in terms of all the peripheral configs, the SATA, 
USB, network, etc, which *should* be the same, since they are all based 
on the same SoC.

While your edmini only uses a single SATA port, that could easily be 
overcome by defining addresses for both in the board config, and just 
#undef'ing it for those that do not use the second port. (It seems more 
descriptive to have both ports defined in the same place, and then say 
that the edmini doesn't use the second one).

I might just be being lazy, of course :-)

Rogan
P.S. Is there any attention being paid to the ARM defconfig cleanup 
going on in the kernel, and thoughts of copying their approach?

  reply	other threads:[~2010-08-05 15:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 12:35 [U-Boot] [PATCH V7 0/4] Add disk support to orion5x and edminiv2 Albert Aribaud
2010-08-05 12:35 ` [U-Boot] [PATCH V7 1/4] ide: add configuration CONFIG_IDE_SWAP_IO Albert Aribaud
2010-08-05 12:35   ` [U-Boot] [PATCH V7 2/4] ide: add mvsata_ide driver Albert Aribaud
2010-08-05 12:35     ` [U-Boot] [PATCH V7 3/4] cmd_ide: add support for orion5x Albert Aribaud
2010-08-05 12:35       ` [U-Boot] [PATCH V7 4/4] edminiv2: add mvsata_ide and cmd_ide support Albert Aribaud
2010-08-05 18:48         ` Prafulla Wadaskar
2010-08-05 18:43       ` [U-Boot] [PATCH V7 3/4] cmd_ide: add support for orion5x Prafulla Wadaskar
2010-08-05 21:28         ` Albert ARIBAUD
2010-08-05 19:09     ` [U-Boot] [PATCH V7 2/4] ide: add mvsata_ide driver Prafulla Wadaskar
2010-08-05 21:29       ` Albert ARIBAUD
2010-08-06  9:38         ` Albert ARIBAUD
2010-08-07  6:39     ` Prafulla Wadaskar
2010-08-07  8:31       ` Albert ARIBAUD
2010-08-05 18:58   ` [U-Boot] [PATCH V7 1/4] ide: add configuration CONFIG_IDE_SWAP_IO Prafulla Wadaskar
2010-08-05 12:42 ` [U-Boot] [PATCH V7 0/4] Add disk support to orion5x and edminiv2 Rogan Dawes
2010-08-05 13:02   ` Wolfgang Denk
2010-08-05 14:11     ` Albert ARIBAUD
2010-08-05 14:28       ` Rogan Dawes
2010-08-05 15:12         ` Albert ARIBAUD
2010-08-05 15:35           ` Rogan Dawes [this message]
2010-08-05 18:25           ` Wolfgang Denk
2010-08-05 18:37             ` Prafulla Wadaskar
2010-08-06  7:08               ` Albert ARIBAUD
2010-08-06  8:18                 ` Prafulla Wadaskar
2010-08-06  9:09                   ` Albert ARIBAUD

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=4C5ADA47.1020100@dawes.za.net \
    --to=rogan@dawes.za.net \
    --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