**** BEGIN LOGGING AT Tue Dec 14 02:59:57 2010 Dec 14 05:05:19 anybody around who's more familiar with the uboot source than just "I compiled it a while back" ? Dec 14 05:13:52 mdm2k: why do you ask? Dec 14 05:49:25 the stock uboot takes up the first 128k of flash and stores environment in the next 128k Dec 14 05:49:54 I'd like to compile an new one that I can put at 256k in flash that stores its environment after that, say at 512k Dec 14 05:50:09 so that I can load the second uboot from the first one, and then boot a kernel from there Dec 14 05:50:50 that way I can still boot the stock kernel in flash from the stock bootloader, but normally boot via the second uboot to load a kernel with the "correct" arch number Dec 14 05:54:09 oooh, new patch readying up Dec 14 06:02:19 mdm2k: why not just write both kernels somewhere and use an automatic chain to set archnum and boot into the other kernel? Dec 14 06:04:17 I'm not sure I follow the suggestion entirely... the default kernel is at 1M in flash, and my other kernel is on a sata disk (which the new uboot can read, and stock uboot can't) Dec 14 06:05:38 I get the impression that you can't change the arch number in uboot without recompiling, despite claims that you can do setenv arcNumber... is that incorrect? Dec 14 06:06:48 wat Dec 14 06:06:53 ofc you can change the archnum Dec 14 06:07:10 why would you think you would have to recompile to change the arcnum? Dec 14 06:07:34 http://www.openplug.org/plugwiki/index.php/Compiling_Linux_Kernel_for_the_Plug_Computer the section about "note for guruplugs" Dec 14 06:09:03 if that's the case then I should just overwrite stock uboot, and to boot the stock kernel I'd just setenv arcNumber 2601 Dec 14 06:11:55 why would you need to boot to the stock kernel though? Dec 14 06:16:42 anyway mdm2k, to answer your original question, it's easy enough to modify where the settings are stored, see include/configs/guruplug.h in the uboot tree Dec 14 06:16:46 around lines 74-76 Dec 14 06:17:00 unsure where to edit to change where uboot itself is stored Dec 14 06:18:01 I'm just paranoid and don't want to kill the system that works correctly with the bluetooth and wifi hardware before I get everything going on the sata disk install Dec 14 06:19:37 but if I can load the original kernel from my new uboot then problem solved Dec 14 06:20:13 let me give that a try Dec 14 06:30:14 mdm2k: btw in my uboot i cloned from the git repo a few months ago has the guruplug's arcnum assigned properly Dec 14 06:30:30 so any recent checkout should be able to boot mainline kernels Dec 14 06:37:01 yeah, new uboots have the right number and boot vanilla kernels, the issue is that I want to also be able to boot the default guruplug kernel with the wacky arch num Dec 14 06:37:33 you should be able to set arcNumber in that case then, afaik Dec 14 06:40:26 mdm2k: why would you want to boot the default kernel, though? Dec 14 06:40:47 even if during a kernel upgrade it fails to boot, you can just boot the one you had before Dec 14 06:40:55 (via tftp or usb or..) Dec 14 06:43:15 I want to mostly leave the flash alone, leaving the entire default system on it Dec 14 06:43:52 I'm using a sata disk that will have my actual stuff on it Dec 14 06:44:10 so I want to be able to boot that, with its kernel, or to boot the default flash system with its kernel Dec 14 06:45:47 you can still boot to the default fs with a newer kernel, you'll just get unimportant errors (assuming you're only booting to it for recovery) about missing modules Dec 14 06:46:23 personally, i just use a usb drive with the default ubuntu on it, and just change the root= in bootargs Dec 14 06:46:42 (i store / on the flash, with /usr /var and /home on an esata drive) Dec 14 06:48:30 you've got bluetooth and wifi working with your own kernel, right? the drivers are fine and don't need patches so long as you provide the firmware blobs? Dec 14 06:49:10 i don't know about bluetooth, as i don't have any bluetooth devices, and i'd probably just leave it turned off anyway Dec 14 06:49:13 but wireless works Dec 14 06:49:17 with only the firmware blob Dec 14 06:50:13 do you use the uapctl binary, or is there a replacement for that available? Dec 14 06:50:31 somebody had the source for that Dec 14 06:50:43 but i don't use it Dec 14 06:51:26 are you using the wireless in ap or sta mode? Dec 14 06:51:47 sta for now Dec 14 06:51:51 ap is on my todo list Dec 14 06:52:50 mdm2k: http://plugcomputer.org/plugforum/index.php?topic=2196.msg13114#msg13114 Dec 14 06:52:53 the sources Dec 14 06:53:20 oh nice Dec 14 06:53:45 I read somewhere that it was probably just a bunch of ioctls so it wouldn't be hard to reimplement but that's even easier Dec 14 06:54:11 well you can find out exactly what it is now ;D Dec 14 06:54:26 the sources are rather small too Dec 14 06:55:02 2 .c/.h pairs and a a few .conf files Dec 14 07:24:09 so, setenv arcNumber 2601 in my recently compiled uboot doesn't seem to boot the original guruplug kernel Dec 14 07:24:16 any ideas? Dec 14 07:27:10 mdm2k: you could kexec Dec 14 07:27:17 or make an initrd that does Dec 14 07:27:26 (although that would make 3 kernels!) Dec 14 07:28:06 as to why it doesn't boot, not how I can make it more complicated :) Dec 14 07:58:59 hmm, arch/arm/lib/bootm.c seems to indicate it's setenv machid, not arcNumber Dec 14 08:02:57 and it takes hex Dec 14 08:03:06 setenv machid A29 works, yay **** ENDING LOGGING AT Wed Dec 15 02:59:57 2010