Kernel Configuration used for validation &demo images of xM

Hai

Kernel configuration is little bit tough for beginners thats why am
still starting with omap2plus_defconfig. So it will be a great help if
a Beagleboard-xm specfic kernel configuration is available.

Is there any way to obtain the Kernel configuration(.config) used to
compile the validation[1] &demo[2] images of Beagleboard-xM. It will
be very useful as a base configuration

[1]:validation image-
http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/beagleboard-validation-201008201549.img.gz

[2]: demo image-
http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/beagleboard-demo-201008201549-configured.img.gz

Kernel configuration is little bit tough for beginners thats why am
still starting with omap2plus_defconfig. So it will be a great help if
a Beagleboard-xm specfic kernel configuration is available.

When I build the config "omap3_beagle_defconfig" for xM board it
didn't work for me too but when I tried "omap3_beagle_cam_defconfig"
is works fine. May be you can also give a try with
"omap3_beagle_cam_defconfig"

Amit

When I build the config "omap3_beagle_defconfig" for xM board it
didn't work for me too but when I tried "omap3_beagle_cam_defconfig"
is works fine. May be you can also give a try with
"omap3_beagle_cam_defconfig"

From where did you get that Configuration(omap3_beagle_cam_defconfig)?
Could you please post it ?

Am still looking for the Kernel configurations used to compile the
validation & demo images of Beagleboard-xM.
http://groups.google.com/group/beagleboard/msg/2cd7214c7a426be6 tells
that Jason Kridner made the images. Hope that he will post it soon..

I don't have an xM to verify this but if these are anything like the
C4/Bx validation images you can do the following to get the .config used
to build the kernel:

zcat /proc/config.gz > /tmp/beagle-config.txt

This assumes that both of the following were enabled in the kernel:
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y

I don't have an xM to verify this but if these are anything like the
C4/Bx validation images you can do the following to get the .config used
to build the kernel:

zcat /proc/config.gz > /tmp/beagle-config.txt

Thanks Michael, Its working..

The Configuration obtained by 'zcat /proc/config.gz > /tmp/beagle-
config.txt' from Beagleboard-xM Test(20100820) image is available @
http://pastebin.com/FPHKiKKH

hi Michael,
I didn’t get this part. Why wud the .config file used to build the kernel be in /proc directory?Can you make it more clear?

Thanks,
Vamsi

It's a feature, selected by a config option that angstrom has enabled...

Regards,

"cat /proc/config.gz". It can be gunzip'd and copied to the kernel directory as .config.
Regards
Sid.

I don't have an xM to verify this but if these are anything like the
C4/Bx validation images you can do the following to get the .config used
to build the kernel:

zcat /proc/config.gz > /tmp/beagle-config.txt

Thanks Michael, Its working..

The Configuration obtained by 'zcat /proc/config.gz > /tmp/beagle-
config.txt' from Beagleboard-xM Test(20100820) image is available @
http://pastebin.com/FPHKiKKH

Thanks for noting the above.

There is the starting defconfig [1] (per Angstrom) , but OE performs
some automated updates on it during the build to create the modules.
Then, there is the script [2] that modifies the defconfig during the
bitbake process.

[1] http://gitorious.org/~Jadon/angstrom/jadon-openembedded/blobs/validation-20100820b/recipes/linux/linux-omap/beagleboard/defconfig
[2] http://gitorious.org/~Jadon/angstrom/jadon-openembedded/blobs/validation-20100820b/recipes/linux/linux.inc

The kernel configuration used to compile the kernel includes and option
that tells the build system to store the configuration in a manner where
the /proc file system will make it available when the kernel is run. So
when the kernel is booted and /proc is mounted the configuration used to
compile the kernel is available from /proc/config.gz.

/proc is a special directory under Linux. It doesn't contain text files
or even binary files. Instead, the files under /proc are actually just
mechanisms for retrieving and modifying information about the running
system. You can find files under /proc that represent each running
process, available drivers, memory info and cpu info. Try

  cat /proc/cpuinfo

to see information about the processor (or processors, if there is more
than one) that your system is running.

You can even see what command line arguments were passed to the kernel
by u-boot with the following:

  cat /proc/cmdline

Hope that helps.