Is there a special advantage to using "make xo_1_defconfig" instead of just copying over a stock Fedora 11 .config file?
I've compiled a module but it looks like I need a couple dependencies so I'm wondering if just compiling the kitchen sink would be easier than searching through "make menuconfig".
I'm running the latest XO-1 kernel from http://dev.laptop.org/~kernels/olpc-2.6.31-xo1/
I did basically this on a CentOS 5 machine:
lsb_release -d # Description: CentOS release 5.5 (Final)
yum -y install gcc make ncurses ncurses-devel glibc glibc-devel glibc-headers rpmdevtools rpm-build
adduser olpcdev su - olpcdev rpmdev-setuptree
# look for the latest 60M src rpm here: # http://dev.laptop.org/~kernels/olpc-2.6.31-xo1/?C=M;O=D wget http://dev.laptop.org/~kernels/olpc-2.6.31-xo1/kernel-2.6.31_xo1-20100505.18... rpm --nomd5 -i kernel-2.6.31_xo1-20100505.1835.1.olpc.b072a92.src.rpm cd ~/rpmbuild/SOURCES/ tar jxf olpc-2.6.tar.bz2 cd linux-2.6.31 make clean distclean make ARCH=i386 INSTALL_MOD_STRIP=1 xo_1_defconfig make ARCH=i386 INSTALL_MOD_STRIP=1 menuconfig # activate bluetooth or whatever make ARCH=i386 INSTALL_MOD_STRIP=1 modules
On Mon, May 24, 2010 at 09:56:40PM -0700, Joshua Daniel Franklin wrote:
Is there a special advantage to using "make xo_1_defconfig" instead of just copying over a stock Fedora 11 .config file?
You get the modules and code needed for the XO-1. That's the special advantage.