Re: [Angstrom-devel] [Review] linux-rp-2.6.24 r4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hans Henry von Tresckow schreef: | mtn diff for linux-rp 2.6.24 attached Would this only be for poodle, or also for c7x0, spitz, akita, tosa and collie? What's the opinion of zaurus mentors on this? regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHt/a3MkyGM64RGpERAs/PAJ41KPuRmCTTS1y2tUXyAm8JmG2LYQCgkbhD Vykk0MM7Q/5FvxMdGBpxF7A= =ZQ7L -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] h5000 test images available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, PaulS merged the defconfig updates and the autobuilder chucked out 2007.12-r4 images at http://www.angstrom-distribution.org/unstable/autobuild/h5000/ There are 2 ways to test all this new goodness: 1. download and reflash 2. 'ipkg update ipkg upgrade reboot'[2] Changes since r2: * kernel updated to 2.6.21-hh20-r13 (was r6) * glibc now check for changes to /etc/resolv.conf * updated bluez utils and libs * at76_usb driver included (no firmware yet[1]) Please send your finding to this list so we can work out on how to update bugzilla and the linuxtogo wiki. regards, Koen [1] Try http://hovland.org/familiar/atmel_at76c503-rfmd-1.103.5.41.bin (no WPA) [2] in an hour or so when all the feeds are done syncing - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD4DBQFHt/wWMkyGM64RGpERAkofAJjez/cg96Cbm1IDc+sF3cHCJRL8AKCCHb1b 5pBQE40C9z4wUCkah3Of/Q== =AwIe -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [RFC] update release images with 2007.12-rX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We've fixed a number of bugs in the stable branch and it would be nice if users can benefit from that straight away, without having to use the package manager. Up until this point there have been no big kernel upgrades (e.g 2.6.x - 2.6.x+1), only defconfig tweaks. So: Update release images with 2007.12-rX, where X = 4 What do you think about this? If you think this is a good idea, do we want to shoot for -r4 (after testing), or do mentors want to get some more bugfixes in and aim for -r5? regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHt/3AMkyGM64RGpERAsDBAJ4728mOXxV7udwK+D7nWIlHVXoCvQCfSlL2 CoQt9kuPO7VW7Ck9MxNWwtg= =c6mC -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [review] bitbake.conf elaborations from .dev
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Sokolovsky schreef: | Hello, | | Changes to maintain consistency with .dev and open way for | local.conf-free OE opeation. | * Machines which have affinity towards jffs2, can add 'IMAGE_FSTYPES ?= | jffs2' to their configs. (Many known machines have been updated | already). The machines in the branch haven't been updated yet AFAIK. - -1 from me till it includes the machine updates as well regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHt/iNMkyGM64RGpERAgE2AJ9TJ7cJw3+TtN0QKErsUUBLVWyUOwCfb3rq a2N9F0kHO8uI0sw8Ed2thDI= =d7QZ -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [review] bitbake.conf elaborations from .dev
Hello, On Sun, 17 Feb 2008 10:04:13 +0100 Koen Kooi [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Sokolovsky schreef: | Hello, | | Changes to maintain consistency with .dev and open way for | local.conf-free OE opeation. | * Machines which have affinity towards jffs2, can add 'IMAGE_FSTYPES ?= | jffs2' to their configs. (Many known machines have been updated | already). The machines in the branch haven't been updated yet AFAIK. - -1 from me till it includes the machine updates as well Well, of course that patch would be merged too with these changes - it's just not easy to pull all revs for review ann. I assume with that change it's +1. regards, Koen -- Best regards, Paul mailto:[EMAIL PROTECTED] ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [RFC] update release images with 2007.12-rX
Hello, On Sun, 17 Feb 2008 10:26:24 +0100 Koen Kooi [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, We've fixed a number of bugs in the stable branch and it would be nice if users can benefit from that straight away, without having to use the package manager. Up until this point there have been no big kernel upgrades (e.g 2.6.x - 2.6.x+1), only defconfig tweaks. So: Update release images with 2007.12-rX, where X = 4 What do you think about this? That's something I was thinking about as means to get out of the situation where both old bootloader and rootfs images for linux-hh devices are cross-incompatible with the new ones (to appear yet). But only when new ones ready. I think that we should prioritize package manager upgrades by all means, and use image upgrades only when package manager upgrades don't work smoothly. On the other hand, r0 went with pretty annoying 100% CPU usage bug, which would be nice to exterminate completely. So, overall 0 points from me. If you think this is a good idea, do we want to shoot for -r4 (after testing), or do mentors want to get some more bugfixes in and aim for -r5? I'd like to bump to r5 right now, marking that linux-hh kernels now support kexec command line. So, it would be Angstrom 2007.12-r5 and kernel 2.6.21-hh20-r13. Ones the new bootloaders are out, all before that would need to be nuked. (And all that because of thinko in the arm-linux kernel and/or kexec command line support patch, which bothers to put atags not where old kernels expect them). regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHt/3AMkyGM64RGpERAsDBAJ4728mOXxV7udwK+D7nWIlHVXoCvQCfSlL2 CoQt9kuPO7VW7Ck9MxNWwtg= =c6mC -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel -- Best regards, Paul mailto:[EMAIL PROTECTED] ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] ChangeLog for new distro revs, was Re: h5000 test images available
Hello, On Sun, 17 Feb 2008 10:19:18 +0100 Koen Kooi [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, PaulS merged the defconfig updates and the autobuilder chucked out 2007.12-r4 images at http://www.angstrom-distribution.org/unstable/autobuild/h5000/ There are 2 ways to test all this new goodness: 1. download and reflash 2. 'ipkg update ipkg upgrade reboot'[2] Changes since r2: * kernel updated to 2.6.21-hh20-r13 (was r6) * glibc now check for changes to /etc/resolv.conf * updated bluez utils and libs * at76_usb driver included (no firmware yet[1]) I lu-u-uv to see such changes list! But of course in our situation it's just random boon not here to stay, right? Because devels are not going to keep such boring stuff as changes list in their heads, and we don't have dedicated docs person to collect that otherwise. In this regard doing proper rev tags would help much, so we can run a kind of mtn2cl.sh on tag range. [] -- Best regards, Paul mailto:[EMAIL PROTECTED] ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [RFC] update release images with 2007.12-rX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Sokolovsky schreef: | Hello, | | On Sun, 17 Feb 2008 10:26:24 +0100 | Koen Kooi k.kooi-oe7qfRrRQfcdWmXj+hCI//[EMAIL PROTECTED] wrote: | | Hi, | | We've fixed a number of bugs in the stable branch and it would be nice | if users can benefit from that straight away, without having to use | the package manager. Up until this point there have been no big kernel | upgrades (e.g 2.6.x - 2.6.x+1), only defconfig tweaks. | | So: | | Update release images with 2007.12-rX, where X = 4 | | What do you think about this? | | That's something I was thinking about as means to get out of the | situation where both old bootloader and rootfs images for linux-hh | devices are cross-incompatible with the new ones (to appear yet). But | only when new ones ready. I think that we should prioritize package | manager upgrades by all means, and use image upgrades only when package | manager upgrades don't work smoothly. It's not meant as an image upgrade, it's meant to improve the important 'first impression' new users get from angstrom. | On the other hand, r0 went with pretty annoying 100% CPU usage bug, | which would be nice to exterminate completely. So, overall 0 points | from me. | | If you think this is a good idea, do we | want to shoot for -r4 (after testing), or do mentors want to get some | more bugfixes in and aim for -r5? | | I'd like to bump to r5 right now, marking that linux-hh kernels now | support kexec command line. Sure, please go ahead with that. | So, it would be Angstrom 2007.12-r5 and | kernel 2.6.21-hh20-r13. Ones the new bootloaders are out, all before | that would need to be nuked. (And all that because of thinko in the | arm-linux kernel and/or kexec command line support patch, which | bothers to put atags not where old kernels expect them). What do you meant exactly with 'bootloader', is that a bootldr replace, LAB, kernel+initramfs as first stage, kernel+initramfs as second stage, something else? regards, Koen PS: altboot is broken because it doesn't handle timed-out reads, so zaurus people can stop claiming there's a magical kernel version that solved it; there isn't - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHuAm3MkyGM64RGpERAjGdAJ9QPX7busiMFb9JTeNEUbfvY5c4hQCcDSuM SzMqI/rLU4gIemdr3G7p3S8= =UDgW -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] ChangeLog for new distro revs, was Re: h5000 test images available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Sokolovsky schreef: | Hello, | | On Sun, 17 Feb 2008 10:19:18 +0100 | Koen Kooi k.kooi-oe7qfRrRQfcdWmXj+hCI//[EMAIL PROTECTED] wrote: | | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Hi, | | PaulS merged the defconfig updates and the autobuilder chucked out | 2007.12-r4 images at | | http://www.angstrom-distribution.org/unstable/autobuild/h5000/ | | There are 2 ways to test all this new goodness: | | 1. download and reflash | 2. 'ipkg update ipkg upgrade reboot'[2] | | Changes since r2: | | * kernel updated to 2.6.21-hh20-r13 (was r6) | * glibc now check for changes to /etc/resolv.conf | * updated bluez utils and libs | * at76_usb driver included (no firmware yet[1]) | | I lu-u-uv to see such changes list! But of course in our situation it's | just random boon not here to stay, right? Because devels are not going | to keep such boring stuff as changes list in their heads, and we don't | have dedicated docs person to collect that otherwise. [EMAIL PROTECTED]:~/website/unstable/autobuild/h5000$ diff -Nurd Angstrom-console-image-glibc-ipk-2007.12-r2-h5000-testlab/installed-package-sizes.txt Angstrom-console-image-glibc-ipk-2007.12-r4-h5000-testlab/installed-package-sizes.txt That will give you the packages that changed, once you have that it's trivial to find the changes by peeking in BACKPORTS.txt or using a restricted mtn log (e.g. 'mtn log packages/foo --last 3') | In this regard doing proper rev tags would help much, so we can run a | kind of mtn2cl.sh on tag range. That (any volunteers?) or keep a NEWS.angstrom file in the branch that includes a user-readable changelist instead of concatenated commit messages. regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHuAsWMkyGM64RGpERArEZAKCCUbUW6cEx5ZkglZeeUaQQBistlACgtOyZ oKgC26v4It9YU4PycN1wRdU= =xf3V -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [RFC] update release images with 2007.12-rX
Hello, On Sun, 17 Feb 2008 11:17:28 +0100 Koen Kooi [EMAIL PROTECTED] wrote: [] But | only when new ones ready. I think that we should prioritize package | manager upgrades by all means, and use image upgrades only when package | manager upgrades don't work smoothly. It's not meant as an image upgrade, it's meant to improve the important 'first impression' new users get from angstrom. Ok by me then. (Except that I have so much stuff unmerged to help with that and daily use even better ;-) ). [] | I'd like to bump to r5 right now, marking that linux-hh kernels now | support kexec command line. Sure, please go ahead with that. Done. | So, it would be Angstrom 2007.12-r5 and | kernel 2.6.21-hh20-r13. Ones the new bootloaders are out, all before | that would need to be nuked. (And all that because of thinko in the | arm-linux kernel and/or kexec command line support patch, which | bothers to put atags not where old kernels expect them). What do you meant exactly with 'bootloader', is that a bootldr replace, LAB, kernel+initramfs as first stage, kernel+initramfs as second stage, something else? Well, I sent RFC on that: http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2008-February/001776.html So yes, this is 2nd stage kernel+initramfs solution, replacing a kernel loaded by 1nd stage bootloader (be it haret, HH.org bootloader, anything else) [some time ago I proposed to consider NAND bootstrap loader as 0th stage, so I assume that numbering]. At the same time, bootloading (actually, interactive selection) functionality is made to be transparent and used only if no root= was specified on kernel commandline. So actually, it's a drop-in replacement for production kernel too, which fact RFC above emphasizes and exploits. (But I intend to add recognition and ignoring of botched commandlines bootldr passes, so this thing is going to solve lots of issues for us ;-) ). regards, Koen PS: altboot is broken because it doesn't handle timed-out reads, so zaurus people can stop claiming there's a magical kernel version that solved it; there isn't Well, at this time, initramfs-bootmenu-image doesn't support timeout at all. That's mostly because timeout implies ability to save last choice, and that in turn is machine-specific stuff which I wanted to keep away from initramfs-bootmenu-image until it will mature and procedure for its building will be settled. And even for specific machines, that requires good thought where to store settings. If mtd map has 'kernel' partition, store settings in last few bytes of it? How does that sound? ;-) [] -- Best regards, Paul mailto:[EMAIL PROTECTED] ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [review] merge kexec command line support
Hello, - Revision: f5ac91666271607b6fb0d8186495c57e9a4c5b01 Ancestor: af267d79107d9258fec25067e3ac6765f2ba9cc6 Author: [EMAIL PROTECTED] Date: 2008-02-05T23:28:12 Branch: org.openembedded.dev Renamed entries: packages/kexec/kexec-tools-1.101 to packages/kexec/files Added files: packages/kexec/files/kexec-static.patch packages/kexec/kexec-tools-static_1.101.bb ChangeLog: kexec-tools: add static version. partly closes 3739. * rename packages/kexec/kexec-tools-1.101 to packages/kexec/files so that patches can be shared * add packages/kexec/files/kexec-static.patch and packages/kexec/kexec-tools-static_1.101.bb - Revision: af267d79107d9258fec25067e3ac6765f2ba9cc6 Ancestor: 1be7d4d46464a58e8c1173f4199c4e064d787854 Author: [EMAIL PROTECTED] Date: 2008-02-05T23:23:32 Branch: org.openembedded.dev Renamed entries: packages/kexec/kexec-tools_1.101.bb to packages/kexec/kexec-tools.inc Added files: packages/kexec/kexec-tools_1.101.bb Modified files: packages/kexec/kexec-tools.inc ChangeLog: kexec-tools: unify - Revision: 28e2872ee9420efa1c6785b37d88314496a12175 Ancestor: e2d31688a9fdad7d686402b98de5719584b3e09e Author: [EMAIL PROTECTED] Date: 2007-12-27T16:25:20 Branch: org.openembedded.dev Added files: packages/kexec/kexec-tools-1.101/kexec-arm-atags.patch Modified files: packages/kexec/kexec-tools_1.101.bb ChangeLog: kexec-tools: Add support for ARM atags allowing the commandline to be set (based on #3430 with changes) -- Best regards, Paul mailto:[EMAIL PROTECTED] ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [review] merge kexec command line support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Sokolovsky schreef: | Hello, +1 on the kexec stuff | | - | Revision: f5ac91666271607b6fb0d8186495c57e9a4c5b01 | Ancestor: af267d79107d9258fec25067e3ac6765f2ba9cc6 | Author: [EMAIL PROTECTED] | Date: 2008-02-05T23:28:12 | Branch: org.openembedded.dev | | Renamed entries: | packages/kexec/kexec-tools-1.101 to packages/kexec/files | Added files: | packages/kexec/files/kexec-static.patch | packages/kexec/kexec-tools-static_1.101.bb | | ChangeLog: | | kexec-tools: add static version. partly closes 3739. | * rename packages/kexec/kexec-tools-1.101 to packages/kexec/files so | that patches can be shared | * add packages/kexec/files/kexec-static.patch and | packages/kexec/kexec-tools-static_1.101.bb | | - | Revision: af267d79107d9258fec25067e3ac6765f2ba9cc6 | Ancestor: 1be7d4d46464a58e8c1173f4199c4e064d787854 | Author: [EMAIL PROTECTED] | Date: 2008-02-05T23:23:32 | Branch: org.openembedded.dev | | Renamed entries: | packages/kexec/kexec-tools_1.101.bb to | packages/kexec/kexec-tools.inc Added files: | packages/kexec/kexec-tools_1.101.bb | Modified files: | packages/kexec/kexec-tools.inc | | ChangeLog: | | kexec-tools: unify | | - | Revision: 28e2872ee9420efa1c6785b37d88314496a12175 | Ancestor: e2d31688a9fdad7d686402b98de5719584b3e09e | Author: [EMAIL PROTECTED] | Date: 2007-12-27T16:25:20 | Branch: org.openembedded.dev | | Added files: | packages/kexec/kexec-tools-1.101/kexec-arm-atags.patch | Modified files: | packages/kexec/kexec-tools_1.101.bb | | ChangeLog: | | kexec-tools: Add support for ARM atags allowing the commandline to be | set (based on #3430 with changes) | | | - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHuCC4MkyGM64RGpERApQPAJ98ph55r+zgkwbK+Ta+U3WROCKD9ACfV8Gb TYnbr8Z/CbaZ+jHr3NtxEGc= =uocF -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [RFC] update release images with 2007.12-rX
Koen Kooi wrote: * on angelboot (read: zaurus) machines the kernel partition holds stripped down kernel + initramfs that kexecs a second kernel (with more dirvers) with a bigger initramfs which kexecs a third kernel to boot into final userspace I think we should have a stripped down kernel + initramfs thats kexecs the kernel to boot into userspace. When the klibc stuff is ready, we only need to disable networking the get the kernel small enough to get the initramfs into the partition too (I hope). So we would only gain the boot-from-nfs option if we use the solution you describe. Regards, Thomas ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Bootloading: the revolution, was: Re: [RFC] update release images with 2007.12-rX
Hello, On Sun, 17 Feb 2008 12:23:48 +0100 Koen Kooi [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Sokolovsky schreef: | Well, I sent RFC on that: | http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2008-February/001776.html | So yes, this is 2nd stage kernel+initramfs solution, replacing a kernel | loaded by 1nd stage bootloader (be it haret, HH.org bootloader, | anything else) [some time ago I proposed to consider NAND bootstrap | loader as 0th stage, so I assume that numbering]. At the same time, | bootloading (actually, interactive selection) functionality is made to | be transparent and used only if no root= was specified on kernel | commandline. So actually, it's a drop-in replacement for production | kernel too, which fact RFC above emphasizes and exploits. Let me see if I understand it correctly: [] Well, let me reword it differently, as all it is done with cross-unification in mind: 1. 1st-level bootloader is tasked with one and only simple task: to load and run Linux kernel. In particular, flash-based bootloaders will need to load it either from dedicated flash partition or from a rootfs if they are smart enough from that. 2. That kernel which they load is actually a kernel bundled with initramfs-bootmenu-image. 3. It first checks if kernel command is a bad from a known bad bootloader, in which case it ignores it. Otherwise, if root= is specified, rootfs is booted from that location. All builtin kernel boot options are supported, plus consistent extension syntax for other options (like loopback boot). 4. Otherwise (no root= or cmdline from bad 1st stage bootloader), it shows interactive menu listing of all available block devices with supported file systems. These include: ext2, jffs2, and for vfat - loopback images in the root directory. Also, NFS option is given. 5. Once user selects location, it checks if /boot/zImage (sic) exists, and if so, kexecs to it with appropriately constructed root=. If no /boot/zImage exists, it just uses that rootfs directly (switch_root's to it). 6. To support booting from various filesystems, this new kernel should have initramfs itself to pull up needed modules. Also, to support extended boot syntaxes (loop e.g.), it should be initramfs-uniboot itself. Then, interactive selection is just a small module of it, and the whole thing can be just bundled with initramfs-bootmenu-image, or in other words, bootloader and production kernel is the same zImage! Notes: On step 5, special param is passed on the command line, to avoid recursive kexec invocation and force switch_root behavior for production kernel. * on (non-hx4700) bootldr machines /boot/zImage will hold kernel + initramfs that kexecs a different kernel So we have devices without dedicated root partition? Live and learn. ;-D So yes, this is another reason why bootloader and production kernel should be the same file. So, initially /boot/zImage will be loaded in bootloader mode, and will allow to select actual boot location. But without any accidental gaps in that - no I can boot from flash and CF, but not SD. And if user selects flash boot, it will kexec very itself, but this time in production kernel mode. * on hx4700 the kernel partition holds kernel + initramfs that kexecs a different kernel (/boot/zImage?) Yes. * on angelboot (read: zaurus) machines the kernel partition holds stripped down kernel + initramfs that kexecs a second kernel (with more dirvers) with a bigger initramfs which kexecs a third kernel to boot into final userspace If Zaurus people will be so kind to adopt solution above, then yes. (I once again want to stress fact that I personally dropped my efforts of reviving LAB with the idea for us all to make a common ultimately flexible solution). Then yes, to overcome kernel partition size restriction, an adhoc initramfs can be used with the only task to boot big kernel from flash, and that kernel can be one with initramfs-bootmenu-image bundled, offering all the choices above. * we leave u-boot machines alone for now, since most u-boots are quite sensible nowadays. Yep, but that of course will work for it too. My ultimate goal would be to engineer a Ultimate Rule Them All bootloader which would do only point 1 from the above, and thus will be small and easily portable. Marcin: is that the same idea you had for angelboot machines, or will we repartition flash and put in our own rescue filesystem? I already approached discussing this with Z people, and regret to say that we didn't find too much understanding, from my point of view this seemed like they want to re-make their own wheel of special, small, but sacred size gifted/burdened upon them by Gods of The Old Vendor ;-). Well, I'd like to draw attention that it all works now (kexec support added 2 days ago, jffs2 loading debugged yesterday), and has zero machine affinity in it, so we can start working together on optimizing/elaborating it.
Re: [Angstrom-devel] Bootloading: the revolution, was: Re: [RFC] update release images with 2007.12-rX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Sokolovsky schreef: | 4. Otherwise (no root= or cmdline from bad 1st stage bootloader), it | shows interactive menu listing of all available block devices with | supported file systems. These include: ext2, jffs2, and for vfat - | loopback images in the root directory. Also, NFS option is given. | | 5. Once user selects location, it checks if /boot/zImage (sic) exists, | and if so, kexecs to it with appropriately constructed root=. If | no /boot/zImage exists, it just uses that rootfs directly | (switch_root's to it). It would be really sweet if those scripts parsed /proc/config.gz to control which options are presented to the user. No use in showing CF boot or trying to load pcmcia modules if the defconfig has those disabled. For the bitcounters among us: disabling OABI compat on ARM will gives us back the bits 'wasted' by CONFIG_IKCONFIG. All non-arm systems I know off have enough space for the kernel to stop us worrying. regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHuCupMkyGM64RGpERAtygAJ9nynSQDu3ClvEfMvdzZNazT9wPxwCggQUm K8uH5DqoIydoweyC+GIk/oc= =GVQ0 -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [Review] linux-rp-2.6.24 r4
Hello Hans, I didn't received that diff either. Could you maybe send it to me directly ? Another notes: a) In which time zone/country are you located ? I'm asking, because I very seldom see you on IRC (neither am I, but then I know when I could reach you). b) What are your plans for Angstrom ? I think it would be great if 2.6.24 could become default-kernel for Angstom on Poodle, and if we could enable WPA wireless as well by default. Best regards, Helge Original-Nachricht Datum: Fri, 15 Feb 2008 23:02:17 -0800 Von: Hans Henry von Tresckow [EMAIL PROTECTED] An: angstrom-distro-devel@linuxtogo.org Betreff: [Angstrom-devel] [Review] linux-rp-2.6.24 r4 mtn diff for linux-rp 2.6.24 attached -- Henry von Tresckow (hvontres) ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [Review] linux-rp-2.6.24 r4
please ignore, I planned to send it in private to Hans Henry von Tresckow Helge Original-Nachricht Datum: Sun, 17 Feb 2008 14:21:18 +0100 Von: Helge Deller [EMAIL PROTECTED] An: angstrom-distro-devel@linuxtogo.org Betreff: Re: [Angstrom-devel] [Review] linux-rp-2.6.24 r4 Hello Hans, I didn't received that diff either. Could you maybe send it to me directly ? Another notes: a) In which time zone/country are you located ? I'm asking, because I very seldom see you on IRC (neither am I, but then I know when I could reach you). b) What are your plans for Angstrom ? I think it would be great if 2.6.24 could become default-kernel for Angstom on Poodle, and if we could enable WPA wireless as well by default. Best regards, Helge Original-Nachricht Datum: Fri, 15 Feb 2008 23:02:17 -0800 Von: Hans Henry von Tresckow [EMAIL PROTECTED] An: angstrom-distro-devel@linuxtogo.org Betreff: [Angstrom-devel] [Review] linux-rp-2.6.24 r4 mtn diff for linux-rp 2.6.24 attached -- Henry von Tresckow (hvontres) ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel -- Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! http://games.entertainment.web.de/de/entertainment/games/free ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [RFC] update release images with 2007.12-rX
Dnia Sunday, 17 of February 2008, Koen Kooi napisał: * on angelboot (read: zaurus) machines the kernel partition holds stripped down kernel + initramfs that kexecs a second kernel (with more dirvers) with a bigger initramfs which kexecs a third kernel to boot into final userspace Marcin: is that the same idea you had for angelboot machines, or will we repartition flash and put in our own rescue filesystem? Basically there were two ideas according to Zaurus boot: 1. use kernel+initramfs in kernel partition and let it kexec /boot/zImage 2. use rescue flash partition to keep our boot+reflash system which will be executed by kernel from 1st point Personally I would go into 1st way if we are able to get working system in ~400-500KB of initramfs (minimal Zaurus kernel for c7x0 was ~700KB). -- JID: hrw-jabber.org OpenEmbedded developer/consultant We were talking about everything. It's called friendship. It's like therapy for poor people [WaT 2x18] ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [RFC] update release images with 2007.12-rX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marcin Juszkiewicz schreef: | Dnia Sunday, 17 of February 2008, Koen Kooi napisał: | * on angelboot (read: zaurus) machines the kernel partition holds | stripped down kernel + initramfs that kexecs a second kernel (with more | dirvers) with a bigger initramfs which kexecs a third kernel to boot | into final userspace | | Marcin: is that the same idea you had for angelboot machines, or will | we repartition flash and put in our own rescue filesystem? | | Basically there were two ideas according to Zaurus boot: | | 1. use kernel+initramfs in kernel partition and let it kexec /boot/zImage which leaves CMDLINE intact from /boot/zImage and thus behaves as a non-broken angelboot, right? | 2. use rescue flash partition to keep our boot+reflash system which will |be executed by kernel from 1st point would be rescue filesystem be kernel+init(c)ramfs or a 'real' filesystem? Would it include e.g. wireless-tools and parted? I'm certain ~ we can do all that in less than 7MB, especially with uclibc+thumb (non-collie). | Personally I would go into 1st way if we are able to get working system in | ~400-500KB of initramfs (minimal Zaurus kernel for c7x0 was ~700KB). We would need only busybox and kexec-tools[1] in there, right? regards, Koen [1] does busybox have a kexec applet already? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHuEDlMkyGM64RGpERAujKAJ9rYr5U1OMJPDkNSeORF1EH7ZBW2QCbBE1Z P9vAybq54zJE1dhk2M4Wb8c= =4zz+ -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Bootloading: the revolution, was: Re: [RFC] update release images with 2007.12-rX
Hello, On Sun, 17 Feb 2008 13:42:17 +0100 Koen Kooi [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Sokolovsky schreef: | 4. Otherwise (no root= or cmdline from bad 1st stage bootloader), it | shows interactive menu listing of all available block devices with | supported file systems. These include: ext2, jffs2, and for vfat - | loopback images in the root directory. Also, NFS option is given. | | 5. Once user selects location, it checks if /boot/zImage (sic) exists, | and if so, kexecs to it with appropriately constructed root=. If | no /boot/zImage exists, it just uses that rootfs directly | (switch_root's to it). It would be really sweet if those scripts parsed /proc/config.gz to control which options are presented to the user. No use in showing CF boot or trying to load pcmcia modules if the defconfig has those disabled. For the bitcounters among us: disabling OABI compat on ARM will gives us back the bits 'wasted' by CONFIG_IKCONFIG. All non-arm systems I know off have enough space for the kernel to stop us worrying. /proc/config.gz is important lifecycle maintenance feature, it is of course enabled in linux-hh. But why parse it? Again, initramfs-bootmenu uses actual partitions available (per /proc/partitions) as the source of user choices. As for loading modules, that's done with modprobe -q foo 2/dev/null, so no smoke if they're not there ;-). regards, Koen [] -- Best regards, Paul mailto:[EMAIL PROTECTED] ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [RFC] update release images with 2007.12-rX
Dnia Sunday, 17 of February 2008, Koen Kooi napisał: Marcin Juszkiewicz schreef: | Basically there were two ideas according to Zaurus boot: | | 1. use kernel+initramfs in kernel partition and let it kexec | /boot/zImage which leaves CMDLINE intact from /boot/zImage and thus behaves as a non-broken angelboot, right? CMDLINE can be read from /boot/kernel_params (example name) file by initramfs and used for kexec-ed kernel. | 2. use rescue flash partition to keep our boot+reflash system which | will be executed by kernel from 1st point would be rescue filesystem be kernel+init(c)ramfs or a 'real' filesystem? Whatever is possible. This needs someone who will try to re-use rescue partition (rootfs/kernel) for our use - remember that angelboot boots into rescue if 'OK' is hold on power on. Would it include e.g. wireless-tools and parted? I'm certain ~ we can do all that in less than 7MB, especially with uclibc+thumb We can add anything needed there. GNU Tar, Parted would be most important ones (think Spitz) but WiFi/BT support and bunch of drivers for networking would be nice to have. (non-collie). Collie use simpler way of booting: 1. bootloader - kernel 2. bootloader - flasher 3. bootloader - diagnostics There is no rescue kernel/rootfs like it is in PXA models. | Personally I would go into 1st way if we are able to get working | system in ~400-500KB of initramfs (minimal Zaurus kernel for c7x0 was | ~700KB). We would need only busybox and kexec-tools[1] in there, right? [1] does busybox have a kexec applet already? Paul methods can be used - I did not checked what he use as my c760 is rather developer tool for use from time to time then each day use PDA. -- JID: hrw-jabber.org OpenEmbedded developer/consultant BSD is for people who love Unix. Linux is for people who hate Microsoft. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [RFC] update release images with 2007.12-rX
Hello, On Sun, 17 Feb 2008 19:54:16 +0100 Marcin Juszkiewicz [EMAIL PROTECTED] wrote: [] | Personally I would go into 1st way if we are able to get working | system in ~400-500KB of initramfs (minimal Zaurus kernel for c7x0 was | ~700KB). We would need only busybox and kexec-tools[1] in there, right? [1] does busybox have a kexec applet already? Paul methods can be used - I did not checked what he use as my c760 is rather developer tool for use from time to time then each day use PDA. IMHO, most promising way should be using klibc-linked utils (including its ash). Thomas Kunze works on that. I of course may imagine that will require patching for real-world usability (timeout for 'read' for example). But again, that should be more promising way than plucking busybox. Current numbers for initramfs-bootmenu-image: 820138 Angstrom-initramfs-bootmenu-image-uclibc-ipk-2007.12-r4-hx4700.rootfs.cpio.gz When bundled with the biggest linux-hh zImage (hx4700's due to pcmcia builtin): just dozen Kbs less than 2Mb which is pure luck as that's size of hx4700 kernel partition ;-). Inside: ~850Kb busybox, ~300k - NFS kernel modules. [] -- Best regards, Paul mailto:[EMAIL PROTECTED] ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH] Poodle WPA support
Could the developers here please check this patch for correctness and if OK, commit it to the -dev branch? Basically it enables WPA wireless support with CF-WIFI-cards on Poodle by default. This is done by adding some missing config lines (MACHINE_FEATURES_append_poodle and MACHINE_EXTRA_RRECOMMENDS_poodle), which are similiar to the ones of other Zaurus devices. In task-base.bb I've added the kernel-module-crypto_algapi and kernel-module-cryptomgr to the WIFI section, since they are necessary for WPA support. I assume this should make other Devices WPA-ready as well (is anybody else testing WPA?). Last but not least, the patch against packages/linux/linux-rp-2.6.24/pxafb.patch cleans up the patch itself. Somehow one section went in there twice. Thanks, Helge --- conf/machine/include/zaurus-2.6.inc 39d33e732bf59736015329814890e175fef292aa +++ conf/machine/include/zaurus-2.6.inc b18a61d786ca9ff15682abff9637b3e6fda7c071 @@ -26,12 +26,13 @@ MACHINE_FEATURES_append_spitz = usbhos MACHINE_FEATURES_append_tosa = usbhost wifi MACHINE_FEATURES_append_akita = usbhost MACHINE_FEATURES_append_spitz = usbhost ext2 +MACHINE_FEATURES_append_poodle= wifi MACHINE_EXTRA_RDEPENDS = zaurusd MACHINE_EXTRA_RRECOMMENDS_c7x0 = kernel-module-snd-soc-corgi kernel-module-pxa2xx-cs kernel-module-pcmcia MACHINE_EXTRA_RRECOMMENDS_akita = kernel-module-snd-soc-spitz kernel-module-pxa2xx-cs kernel-module-pcmcia MACHINE_EXTRA_RRECOMMENDS_spitz = kernel-module-snd-soc-spitz -MACHINE_EXTRA_RRECOMMENDS_poodle = kernel-module-snd-soc-poodle +MACHINE_EXTRA_RRECOMMENDS_poodle = kernel-module-snd-soc-poodle kernel-module-pxa2xx-cs kernel-module-pcmcia MACHINE_EXTRA_RRECOMMENDS_collie = kernel-module-locomo-spi kernel-module-sa1100-cs kernel-module-mmc-block \ kernel-module-collie-ts kernel-module-leds-locomo kernel-module-locomokbd --- packages/tasks/task-base.bb 461108bf3685f7346e95114839d03eebb184593b +++ packages/tasks/task-base.bb 37aa3d6c27df362f019142443c1e917b48d198e6 @@ -345,6 +346,8 @@ RRECOMMENDS_task-base-wifi = \ kernel-module-ieee80211-crypt-wep \ kernel-module-ecb \ kernel-module-arc4 \ +kernel-module-crypto_algapi \ +kernel-module-cryptomgr \ kernel-module-michael-mic \ kernel-module-aes --- packages/linux/linux-rp-2.6.24/pxafb.patch d67eb27feca26ea83424f3eebfe5fd89f5e3b75f +++ packages/linux/linux-rp-2.6.24/pxafb.patch f885ab91c336e3345ebcc06ff37f90b630dca0d1 @@ -11,16 +11,3 @@ Index: linux-2.6.23/drivers/video/pxafb. lccr3 = fbi-reg_lccr3; set_hsync_time(fbi, pcd); fbi-reg_lccr3 = (fbi-reg_lccr3 ~0xff) | LCCR3_PixClkDiv(pcd); -Index: linux-2.6.23/drivers/video/pxafb.c -=== linux-2.6.23.orig/drivers/video/pxafb.c2008-01-25 16:25:21.0 -0800 -+++ linux-2.6.23/drivers/video/pxafb.c 2008-01-25 16:32:14.0 -0800 -@@ -1194,7 +1194,7 @@ - if ((clkinfo-old == 13000)) - break; - -- pcd = get_pcd(fbi-fb.var.pixclock); -+ pcd = get_pcd(fbi,fbi-fb.var.pixclock); - lccr3 = fbi-reg_lccr3; - set_hsync_time(fbi, pcd); - fbi-reg_lccr3 = (fbi-reg_lccr3 ~0xff) | LCCR3_PixClkDiv(pcd); ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
