I have not had a chance to try this again.<br>But, this is a lot more clear.<br><br>I am still in doubt what is the real name of the "script.bin" that the system expects. It seems it can be any name, as long as you use a boot.scr, but if boot.scr is missing, my guess it is name is "script.bin".<br>
<br>I have seen on the list names such as:<br><br>system.bin, evb.bim, mele.bin, script.bin, sys_control.bin, etc.<br><br>Rosimildo.<br><br><br><div class="gmail_quote">On Wed, May 30, 2012 at 7:46 AM, Peter Steenbergen <span dir="ltr"><<a href="mailto:p.steenbergen@j1nx.nl" target="_blank">p.steenbergen@j1nx.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><br><div class="gmail_quote">On Wed, May 30, 2012 at 1:16 PM, Henrik Nordström <span dir="ltr"><<a href="mailto:henrik@henriknordstrom.net" target="_blank">henrik@henriknordstrom.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">ons 2012-05-30 klockan 09:46 +0100 skrev lkcl luke:<br>
<div><br>
> hmmm... could someone with debian and the "sfdisk" command please<br>
> list the parameters and attach them to the wiki somewhere appropriate?<br>
> sfdisk is the programmer's fdisk and i believe its parameters are<br>
> unambiguous. there would therefore be no further confusion (one might<br>
> hope).<br>
<br>
</div>fdisk is equally unambigious, just remember use the u command to switch<br>
to sectors instead of the legacy "cylinders" view.<br>
<br>
The only rules are<br>
<br>
a) dont partition space below sector 2048. That area is reserved for<br>
uboot.<br>
<br>
b1) Default fallback boot is that first partition is FAT formatted and<br>
have system.bin and uImage contents.<br>
<br>
b2) Preferred boot method is to look for boot.scr in /boot or / on first<br>
partition in extX or FAT format<br>
<br>
<br>
If boot.scr is used then it contains the uboot commands needed for<br>
loading kernel (+ initrd) and booting. The uboot shell is enabled so you<br>
have rudimentary sh syntax capabilities.<br>
<br>
<br>
As long as you stay within these boundaries then you are free to decide<br>
how to partition. Possible layouts are for example<br>
<br>
1) Single extX partition, sector 2048-end. boot.scr in /boot with the<br>
uboot commands needed for booting.<br>
<br>
2) extX partition + swap partition. boot.scr as above.<br>
<br>
3) FAT boot partition, extX system partition, optional swap partition.<br>
system.bin + uImage in FAT partition. No boot.scr.<br>
<br>
4) Any other partition scheme you see fit for your purpose.<br>
<br>
5) Reserving even more space and loading kernel from fixed blocks, and<br>
use some filesystem not supported by uboot for all partitioned storage.<br>
<br>
Regards<br>
<span><font color="#888888">Henrik<br>
</font></span><div><div><br><br></div></div></blockquote><div><br></div><div>You better start adding that to the wiki ;)</div><div><br></div><div>No really. Thanks for this info, very usefull.</div>
</div></div>
<br>_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br></blockquote></div><br>