On Tue, 2010-07-27 at 23:01 +0200, Gerhard Pircher wrote: [...] > 1. Documentation: > I looked at all the 'defines' files to understand their syntax and > to get an overview about all available keywords. > Nevertheless I would like to know, if there is a documentation > available that lists and explains all available keywords (if so, then > then some of the next questions are best answered with "RTFM"). I read > through the Debian kernel handbook, but that remains silent on this > topic.
Sorry, there is no documentation. The code for this is in
debian/bin/*.py and debian/lib/python.
> 2. 'image-file' keyword:
> Does this keyword also affect the kernel image makefile target?
No, it specifies the file to look at when checking that the kernel image
size is not too large.
> I specified arch/powerpc/boot/zImage for 'image-file', as I would
> like to generate a platform specific cuImage.* file afterwards
> (these U-boot images include a device-tree blob and a small boot-
> wrapper so that newer kernels can be booted on old U-boot versions)
> For this the kernel image needs to be generated with "make zImage".
I think you need to define a new image type, as we already do for Xen
and for s390 tape images. Suppose we call this 'plain-powerpc-cuimage';
then you need to add this to debian/rules.real:
$(STAMPS_DIR)/build_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain-powerpc-cuimage:
BUILD_TARGET = zImage
install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain-powerpc-cuimage:
# rules to install everything in this package
Set ${flavour}_image/type to 'plain-powerpc-cuimage' for every flavour
that should use this image type.
> 3. 'configs' keyword:
> Contrary to my expectations I had add 'configs' entries for my
> flavours, whereas the normal powerpc and powerpc64 flavours don't need
> it. Why can't the build system find my config.book3s-amigaone and
> config.44x-sam440ep files automatically?
No idea.
> The biggest stumbling block at the moment is the kernel config itself.
> The build process always stops with an error (about an invalid kernel
> config), if I just copy the config.powerpc file and modify it for the
> AmigaOne. I read something about a splitconfig script that should
> create all the config fragments, but I can't find it anywhere. So how
> do you create all the config fragments?
Some people use this:
<svn://svn.debian.org/svn/kernel/people/waldi/utils/kconfigeditor2/>.
> One last thing: the device tree source would need to be included in
> the kernel package to create the cuImage file with the bootwrapper,
> the device tree blob and the zImage (and the initrd), when the kernel
> is installed or the initrd image is (re)generated. The device tree
> sources are included in the Lenny powerpc kernel packages, but
> disappeared from the Squeeze and Sid ones (the bootwrapper object
> files are still there however).
> Does anybody know why this happened and if it is possbile to include
> the DT sources again?
[...]
If these are not part of the upstream Linux source then I think they
should be packaged separately.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
