Re: [leaf-devel] git branches
Am 31.03.2013 20:41, schrieb KP Kirchdoerfer: > Hi all; > > I just looked into the branches we have: > > git branch -r >origin/buc5-x86_64-toolchain >origin/maint >origin/maint-4.0 >origin/maint-4.2 >origin/master >origin/next >origin/pu >origin/rpi >origin/ybl/modules-OO > > Can we delete/remove > origin/buc5-x86_64-toolchain > origin/maint-4.0 > origin/maint-4.2 > origin/ybl/modules-OO What would 4.x be based upon then? maint? And if so, what when 5 goes into maint mode? I guess cleaning up is a good thing, I have no clue what all these branches were used for but then. cheers Erich -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF for raspberry pi
Hi. 31.03.2013 20:26, KP Kirchdoerfer пишет: > Hi all; > > with the help of David and based on the work of buildtool.org developers > and many others, I was able to create a toolchain that produces a kernel > and lrp's able to boot on a raspberry pi, to login, to get local net > access and to ssh into the remote box. > > While it will be a long way to create images for the raspberry pi, it > clearly shows that our toolchain is able to successfully cross-compile - > something I've expected, but it's always good to see it really works. Good work. > Before I create a remote repository, so anyone has something to work > with, I'm running rebuild from scratch. > > Some notes about what has been accomplshed and the remaining tasks: > > It's based on kernel version 3.6.11, because the patches are for 3.2 or > 3.6, but not for our currently used 3.4 kernel. > There is ongoing work to include the patches into the mainline kernel, > so life will be easier in the future. Maybe 3.2 patch (or 3.6) will lay on 3.4 kernel? Did you try? > Not all packages build, esp kernel related packages, as expected, but > also others fail, like iptraf, and I do see errors with perl > Digest/SHA1, which also means shorewall will fail to start. > I also had to remove e100* from kmodules to build moddb. e100* should not even be compiled for rpi, like many others NICs - rpi hasn't PCI/PCI-E busses, so it's waste of time and space. > The kernel config needs a review. Esp regarding modules. The kernel > config as-is compiles ext4 and vfat into the kernel. > > It seems that the raspberry is not able to load more than initrd (initrd > and initmod), so we have to concatenate initrd and initmod - with > something like the following command: > > cat initrd.gz initmod.gz > initrd-rpi.gz initmod on embedded platforms may be removed at all - all boot-time modules may be compiled into kernel. One platform, one chipset, one device set. Or, if initrd concatenation is possible - some modules like usb flash may be external, in initmod. > I had the same pb with qemu while testing arm-versatile. I think we need > to enhance the toolchain to distinguish if a host is capable to load > multiple initrd files, or if we have to create a single one. > > I have committed the firmware and raspberry pi special config files to > repo/rpi-firmware, just to put them somewhere. > > Anyway, it's a start. > > kp > -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] git branches
Hi all; I just looked into the branches we have: git branch -r origin/buc5-x86_64-toolchain origin/maint origin/maint-4.0 origin/maint-4.2 origin/master origin/next origin/pu origin/rpi origin/ybl/modules-OO Can we delete/remove origin/buc5-x86_64-toolchain origin/maint-4.0 origin/maint-4.2 origin/ybl/modules-OO as they seem outdated/no longer used? kp -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF for raspberry pi
Am 31.03.2013 20:00, schrieb Mike Noyes: > On 03/31/2013 10:26 AM, KP Kirchdoerfer wrote: >> Hi all; >> >> with the help of David and based on the work of buildtool.org developers >> and many others, I was able to create a toolchain that produces a kernel >> and lrp's able to boot on a raspberry pi, to login, to get local net >> access and to ssh into the remote box. >> >> While it will be a long way to create images for the raspberry pi, it >> clearly shows that our toolchain is able to successfully cross-compile - >> something I've expected, but it's always good to see it really works. > -snip- > > KP, > Outstanding! Blog entry posted. > https://sourceforge.net/p/leaf/blog/2013/03/leaf-for-raspberry-pi/ thx for moving it to the blog. kp -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF for raspberry pi
On 03/31/2013 10:26 AM, KP Kirchdoerfer wrote: > Hi all; > > with the help of David and based on the work of buildtool.org developers > and many others, I was able to create a toolchain that produces a kernel > and lrp's able to boot on a raspberry pi, to login, to get local net > access and to ssh into the remote box. > > While it will be a long way to create images for the raspberry pi, it > clearly shows that our toolchain is able to successfully cross-compile - > something I've expected, but it's always good to see it really works. -snip- KP, Outstanding! Blog entry posted. https://sourceforge.net/p/leaf/blog/2013/03/leaf-for-raspberry-pi/ -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] LEAF for raspberry pi
Hi all; with the help of David and based on the work of buildtool.org developers and many others, I was able to create a toolchain that produces a kernel and lrp's able to boot on a raspberry pi, to login, to get local net access and to ssh into the remote box. While it will be a long way to create images for the raspberry pi, it clearly shows that our toolchain is able to successfully cross-compile - something I've expected, but it's always good to see it really works. Before I create a remote repository, so anyone has something to work with, I'm running rebuild from scratch. Some notes about what has been accomplshed and the remaining tasks: It's based on kernel version 3.6.11, because the patches are for 3.2 or 3.6, but not for our currently used 3.4 kernel. There is ongoing work to include the patches into the mainline kernel, so life will be easier in the future. Not all packages build, esp kernel related packages, as expected, but also others fail, like iptraf, and I do see errors with perl Digest/SHA1, which also means shorewall will fail to start. I also had to remove e100* from kmodules to build moddb. The kernel config needs a review. Esp regarding modules. The kernel config as-is compiles ext4 and vfat into the kernel. It seems that the raspberry is not able to load more than initrd (initrd and initmod), so we have to concatenate initrd and initmod - with something like the following command: cat initrd.gz initmod.gz > initrd-rpi.gz I had the same pb with qemu while testing arm-versatile. I think we need to enhance the toolchain to distinguish if a host is capable to load multiple initrd files, or if we have to create a single one. I have committed the firmware and raspberry pi special config files to repo/rpi-firmware, just to put them somewhere. Anyway, it's a start. kp -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
