You are right in that the SVN trunk is an ambiguous term: It could mean any revision. Let me try my hand at ascii art :) Note Formatting works when javascript is enabled. Backfire is a specific branch of this trunk. If one got into openwrt during the re-write phase, it was natural to call the (SVN) trunk as Kamikaze. I believe that WhiteRussian is now defunct. The devs did a massive re-write, and to distinguish it from the stable branch, called it kamikaze. The original openwrt used to be called white-russian. Your screen capture shows FS was built under Kamikaze.Īs mazilo said, the name can be anything. Is it true that "SVN trunk" can mean any version, it depends on when OpenWrt was updated from SVN? On my AMD64 PhenomII X3 is running with an OpenSuSE v11.3 with only 2GB RAM + 2GB swap space, the compilation can easily spawns to 1500+ processes and the load average shoots to 500+ until the system runs out of swap space and crashes at the last stage trying to create firmware. If your Linux system has a lot of RAM, you may want to see how it goes using -j sans a parameter. For further information on how to take advantages of make on a multicore, you may want to read the make manual on your Linux system. If so, you may want to build the OpenWRT in the background using ionice -c 3 nice -n 20 make -j 2. If the virtual machine allows the use of multicore to compile OpenWRT, beware that the host may become very sluggish if not frozen. cc1, make, configure, etc., will be compiling your OpenWRT. You will also see as many as (at least) three processes (using -j 3), i.e. I tried "make" and "make -j 3" on Dell D820 with Debian in VirtualBox and did not see difference in CPU usage.If you launch top utility, then press 1 to list all the available CPU(s) to show their activities. It seems I need built image using "Ramdisk". Image Type: ARM Linux Kernel Image (uncompressed) # Booting kernel from Legacy Image at 00800000. ![]() Setenv bootcmd 'run bootcmd_openwrt reset' Setenv bootcmd_openwrt 'run tftp_load_openwrt run set_bootargs_tftp bootm 0x800000 0x1100000' Setenv set_bootargs_tftp 'setenv bootargs console=$console rootfstype=ext2' ![]() Setenv tftp_load_openwrt 'tftpboot 0x800000 openwrt-uImage tftpboot 0x1100000 openwrt-rootfs.tgz ' I could not figure out how to boot Openwrt from network, I tried the following: if load $devtype $disknum:1 0x810000 /boot/uEnv.I'm experimenting network loading Openwrt for Dockstar from serial console. Uenv_read=echo loading envs from $devtype $disknum. Uenv_load=usb start setenv uenv_loaded 0 for devtype in usb do for disknum in 0 do run uenv_read_disk done done Set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts ![]() Rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=/dev/mtdblock2 ro rootfstype=jffs2 $mtdparts $rescue_custom_params Rescue_bootcmd=if test $rescue_installed -eq 1 then run rescue_set_bootargs nand read.e 0x800000 0x100000 0x400000 bootm 0x800000 else run pogo_bootcmd fi Mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) And so, i would like change this default variable to realize this installation :īootcmd=run bootcmd_uenv run bootcmd_usb resetīootcmd_uenv=run uenv_load if test $uenv_loaded -eq 1 then run uenv_import fiīootcmd_usb=run usb_init run set_bootargs_usb run usb_boot i would like put OW on nand of dockstar, not on usb. On my second Dockstar, i put the new Uboot (2015.10) and i would like to put Openwrt Unfortunately, it starts searching a kernel image on usb device.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |