From: drEagle <dreagle@doukki.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Request for tutorial
Date: Fri, 10 Apr 2015 02:08:56 +0200 [thread overview]
Message-ID: <55271498.6060405@doukki.net> (raw)
In-Reply-To: <20150409174416.GW9524@bill-the-cat>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Le 09/04/2015 19:44, Tom Rini a ?crit :
> On Thu, Apr 09, 2015 at 06:20:37PM +0200, drEagle wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Hi all,
>>
>> Is there any tutorial to help integrating a new platform into mainline u-boot ?
>> I may propose a new board upsream but the only information I have are an older refork uboot.
>>
>> Any advice will be welcome.
>
> No, but it depends on both how old the old fork is and what does /
> doesn't exist upstream already. If for example the SoC core already
> exists in mainline, mainly use the old code base to move the "board"
> specific part up. If the SoC isn't there in mainline, you can probably
> drop-in the old code base easily enough and get it building / linking,
> and then clean it up. But it really depends on just how old the fork
> is.
The Hardware is a ZYXEL NSA310S.
The NS310S is a DB-88F6702A-BPE board, also known as DB6702A-GMtech.
Like in DLINK DNS-320 (B2) or LaCie CloudBox.
The SOC is a Marvell 88F6282 (ARMADA 300).
The Armada 300 is in the KIRKWOOD family.
The 88F6282 is not upstream.
The GPL code from Zyxel is based on Marvell 3.6.0.
The Marvell u-boot are based on the U-Boot 1.1.4.
My study references are shared on a wiki[1]
[1] https://doukki.net/doku.php?id=hard:arm:armada:armada-zyxel-nsa310
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVJxSYAAoJEIoWzNw2mnfMlywH/1lKXS1emJCsRGdtpKVqII3m
8xukoM147UjWQzuUC87dY/XEhxxfQkx5Kb2QmAQRbm6celfGroNAOQq9XzNfUCeE
sB+4LeKPqJaMGiv5RLu904OiV3LRGpmh8uSFsgHdICFPuvhRgsv2VRQPtHiIlCgl
w+T+YwPBmoX+F/HPrrsmidsisDO3TZUSQ5MXJkmAY15Z3WwFjTVC+Il2A4VCak3h
d29iZQ4+dkmkeUF1GxgZozLSxqbHdm8gVwRpTvzpYhsvOkYF6+aeHRDw4WxPlOwJ
uVXnHZP1N3yijuYgRrq2iXRY/tTgkweWXjVRKumKUwuN/J5ucoZYBlNvr2vGU6c=
=yyvb
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-04-10 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 16:20 [U-Boot] Request for tutorial drEagle
2015-04-09 17:44 ` Tom Rini
2015-04-10 0:08 ` drEagle [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=55271498.6060405@doukki.net \
--to=dreagle@doukki.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.