[U-Boot] KIRKWOOD - PARTITIONS and BOOTSTRAP

[drEagle <dreagle@doukki.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

Le 07/04/2015 02:39, Tom Rini a ?crit :
> On Sat, Apr 04, 2015 at 06:13:18PM +0200, drEagle wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Le 03/04/2015 23:46, Vagrant Cascadian a ?crit :
>>> On 2015-03-25, drEagle wrote:
>>>> Le 21/03/2015 15:53, Vagrant Cascadian a ?crit :
>>>>> It seems that OpenRD Ultimate with u-boot 2015.04-rc3 and newer no
>>>>> longer builds from source, both in Debian and with mainline git. It
>>>>> appears to have overgrown the size limits set for it:
>>>>
>>>> Looks like the NAND partition map had to be changed to give more space for u-boot.
>>>
...
>>> I'll likely remove openrd_ultimate from future uploads to Debian if I
>>> can't get confirmation about how to fix this properly.
>>
>> The same may be a problem for SHEEVAPLUG and GURUPLUG, may be also all KIRKWOOD derivatives.
>> We need to get a more robust and compatible way to define the NAND PARTS, the BOOTLOAD and the NAND UPGRADE.
>> Each distribution has differents needs.
>>
>> It's a discution needed upstream because it ill impact all distribution and users.
> 
> It's possible that by removing some CONFIG options things can fit under
> the size limit and not require env to be moved.

I do not agree with a stay in the past situation.
I have proposed these refresh to help kirkwood plugs become useable.
This is a platform that was looking promising and had also been not so user frendly in the beginning.
The features like the sheevaplug MMC/SD driver was a pain.
UBOOT have greatly gain in a peace of software more robust that in was few years ago.
For Kirkwood Sheevaplugs we have also a device, SD cards, which was simply unuseable.

So I decided to get this driver upstream.

So what now ?
USB layer get fixed.
IDE layer get fixed.
UBIFS is a new standard.
EXT4 support helpfull.
DEVICETREE is needed for linux kernel support.

What I proposed is to get a refresh for :
- - The NAND partitions (with a possible study to be friendly with most distributions around)
- - To discuss about the better BOOTSTRAP method (I may used a script, propose defaults ENV. We may need to boot from IDE, USB, NAND, NET, ...)

It's an open discussion to get a friendly users, understand with the lesser patch in each distribution, with the most possibility afford.

I do not think that, all around customisation is the solution.

Enjoy
G?rald
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVJLuSAAoJEIoWzNw2mnfM+E4H/je+trD4WIb4Fgm01IZxZyev
0i7Z7F9Yf7pENUmh+IWdjycVMbOTXfHfA4/NXkUTF/TPK8xoE7Qv/tDqoqbeQ1Tl
ZU2OtKu9HU8mKivj+2ljNSCoiahx9Kv22zU6VjNTlp0Xc423yiU9OjaFHpIQg6g3
BhFzbCIvM/SWRvUfpLtmGVuYR66hOIaKvFtg0k3MoD9ZdHXbQE9G3ywGGg6M3CVU
D6+OdWg8E5UyL6Ion3aBYYlieZRzCS3hvo2/QwT95XfFG9LHmt4wG6cTC5SQtmdZ
t/bUVFgB0OOderKN0kV4AVBn88rcdro5e+CkA4qKqYWn6hm2cb2YBIbs/XQDfKI=
=J7kX
-----END PGP SIGNATURE-----