From: Georg Schardt <schardt@team-ctech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] add board support for virtex4fx12 minimodul
Date: Tue, 09 Sep 2008 15:23:39 +0200 [thread overview]
Message-ID: <48C678DB.2080500@team-ctech.de> (raw)
In-Reply-To: <aa76a2be0809090555x24d3a1a7gd139b34f44ec7aeb@mail.gmail.com>
Hi Ricardo,
if such an architecture is wanted i can try to create it ?
but i'm stil a beginner in u-boot and not very firm in git, so i think i
ask many things here on the list :)
Georg
Ricardo wrote:
> Hello Georg
>
> Its a pleasure to help.
>
>
>>> 2) Try to unificate the fx12mm board under a more global board, like
>>> the ml507 with is now in mainstream
>>>
>>>
>> you mean, that i create only a new config file and use the ml507 board code
>> ?
>> is this better than create new board specific files under board/avnet/fx12mm
>> ?
>>
>
> I mean something more... If you take a look to your board, it is
> basically a modern version of the ml300 (what is great).
> Unfortunately, the ml300 board cannot use all your improvements.
>
> We faced the same problems building the v5fx30teval board and we
> decide to generate a generic board called ppc440-generic which will be
> the skeleton of all the fpgas boards with the ppc440 processor.
>
> What I am asking you is to create the same architechture for the
> ppc400 processor.
>
>
> Best Regards
>
prev parent reply other threads:[~2008-09-09 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 18:07 [U-Boot] [PATCH] add board support for virtex4fx12 minimodul schardt
2008-09-08 20:04 ` Ricardo
2008-09-09 7:21 ` Georg Schardt
2008-09-09 8:19 ` Wolfgang Denk
2008-09-09 8:23 ` Georg Schardt
[not found] ` <aa76a2be0809090553j482c2f9x1172a634eaf1a405@mail.gmail.com>
2008-09-09 12:55 ` Ricardo
2008-09-09 13:23 ` Georg Schardt [this message]
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=48C678DB.2080500@team-ctech.de \
--to=schardt@team-ctech.de \
--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