<div dir="ltr">You should add this to the wiki on the frontpage! (Insh'allah)<br><br><div class="gmail_quote">On Tue, May 1, 2012 at 4:08 PM, lkcl luke <span dir="ltr"><<a href="mailto:luke.leighton@gmail.com" target="_blank">luke.leighton@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, May 1, 2012 at 2:36 PM, Henrik Nordström<br>
<<a href="mailto:henrik@henriknordstrom.net">henrik@henriknordstrom.net</a>> wrote:<br>
> tis 2012-05-01 klockan 13:59 +0100 skrev lkcl luke:<br>
><br>
>> in other words, do consider using the 2.6.{whatever} kernel - or<br>
>> whatever actually works, get everything working, and _then_ replace<br>
>> one and *ONLY* one component at a time.<br>
><br>
> Not sure what you mean by this. Replace what components with what?<br>
<br>
</div> for example, i am advising paul to consider - nothing more than<br>
*consider* - using the 2.6.36 kernel initially, and the version of<br>
u-boot that is known to work, and downloading pre-existing armhf<br>
debian packages known to be working, proving that it all works.... AND<br>
THEN AND ONLY THEN trying the 3.0 or 3.3 kernel, and THEN AND ONLY<br>
THEN trying a new version of u-boot, and THEN AND ONLY THEN trying<br>
some alternative package compilations, tricks, combinations and so on.<br>
<br>
in other words, start from a known easy-to-achieve but above-all<br>
absolute paramount and ultra-high-priority *working* system,<br>
regardless of whether it is the required actual ultimate goal, and<br>
then change one and ONLY one component or item at a time.<br>
<br>
and - most importantly - RELEASE IT! make it publicly available!<br>
preferably as you're actually going along, rather than "oh i'll<br>
release it when it's ready" (*1)<br>
<br>
then, if the "component" selected - the change required - turns out<br>
to not work, or is too much to do, then the action that can be taken<br>
is:<br>
<br>
a) give up. this is not an unreasonable option. it's *not* a failure<br>
(*2). at least, however, someone else can take over because you<br>
released everything publicly.<br>
<br>
b) ask for help. this again is not an unreasonable option: someone<br>
else might have more expertise than you. it is NOT a failure or a<br>
threat to your ego if you ask for help.<br>
<br>
c) try a smaller incremental step. this again is perfectly<br>
reasonable: yes you couldn't get xyz working but so what - if you try<br>
just x or just y or just z or even w you might get a little bit<br>
further.<br>
<br>
is that clearer?<br>
<br>
l.<br>
<br>
(*1) this attitude absolutely drives me nuts: it means *you* want "all<br>
the glory", or your ego is in the way - fear of criticism - which is<br>
just as bad. don't do it! work publicly, and openly invite others to<br>
collaborate with you!<br>
<br>
(*2) however if you didn't release everything publicly, you just<br>
pissed everyone off by forcing them to duplicate all the effort that<br>
you _did_ go to.<br>
<div class="HOEnZb"><div class="h5"><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></div></div></blockquote></div><br></div>