View Single Post
Old 10-11-2012, 10:28 PM   #17
knc1
Embedded Cheerleader
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,431
Karma: 5840130
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by qlob View Post
try doing:

sudo ./k3flasher.bin ./mx_35to2.bin info

That should work...you will need to get the ram kernel from an ATK install though...
OK, that tells me what was meant by the mystery sentence.

<Grumble>
Now who would put a useless *.bin extension on an executable when the application uses *.bin to indicate (ARM binary) executable data (the "Ram kernel" being transfered in the above case)?
</Grumble>

No harm, no foul, just doesn't mean anything to the O.S. although often it is intended to be suggestive to the human reader, only here we see the same extension used to suggest two different things.

For those who might be interested:
http://www.linux-tutorial.info/modul...ent&pageid=224

And specific to my Grumble about the filename:
http://www.linux-tutorial.info/modul...ntent&pageid=4

Last edited by knc1; 10-11-2012 at 10:56 PM.
knc1 is offline   Reply With Quote