I am not an expert, but I will try to answer most of your questions: - add a package, say qemu you can add a package to a defined configuration by issuing the following command 'scripts/Build-Target -cfg system -job ?-packagename' giving that your configeration name is system, replace ? with the appropriate build level 0-9, usually 5 for normal packages. A prefered way is to add packages to your target/target_name configuration folder. It is different on each target depends on your build.sh script. For example, I can add additional packages to the file under target/target_name/pkgsel.
- bump the kernel (in trunk) from 2.6.28 to 2.6.29-rc, enable squashfs 4.0 (which is in the 2.6.29 kernel and is not compatible with 3.x). For some reasons, I found it hard to upgrade my kernel 2.6.21 because I had so much patches and filesystems ported to that kernel, ie squashfs, aufs, unionfs. My attempt to upgrade to kernel 2.6.28 a month ago failed, so I gave up on it. <can't help you here> - add a custom patch to the kernel You can add patches to the kernel in many ways, the preferred method is dropping patch files to the target directory, under target/target_name/package/linux26. although, you can also drop your patches in package/base/linux26. All patches need to have extension .patch. - create a squash 4.0 image with initrd (well for squash 4.0 I need the 4.0 mksquashfs tool as well) I am not sure what you mean by create squash image with initrd, do you mean and initrd? As for my target, i created a custom build script which creates the squashfs 3.0 image and initrd. If you want to use squashfs 4, I think you need to upgrade mksquashfs 4.0 on the host. On Thu, Mar 19, 2009 at 5:39 AM, Ingmar Schraub <[email protected]> wrote: > > Hello, > > I am still very new to T2 (started yesterday), testing, building, > reading the manual (yes, I do... a comprehensive and great manual!!) and > I see that the T2 folks have spent a lot of time and efforts in getting > the project to this stage. It's impressive. > > As I come from buildroot, I know how to add packages, how to re-compile > individual package, how to re-build everything but leave the toolchain > in place (to save time in building), create different types of target > images (iso, rootfs, squashfs, etc.). > > Now with T2 I see similarities, but some parts are different. > > Could someone give me a pointer how to get started with the following tasks: > - add a package, say qemu > - bump the kernel (in trunk) from 2.6.28 to 2.6.29-rc, enable squashfs > 4.0 (which is in the 2.6.29 kernel and is not compatible with 3.x). > - add a custom patch to the kernel > - create a squash 4.0 image with initrd (well for squash 4.0 I need the > 4.0 mksquashfs tool as well) > > I have done this exercise with buildroot (execept adding qemu, which > would be rather tough to build against uClibc...). > > Any suggestions are welcome. > > Thanks a lot in advance!! > > cheers, Ingmar > > > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [email protected] with a subject of: unsubscribe t2 > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
