Dave, If you check out the omap-only branch of git://git.linaro.org/ubuntu/linux-linaro-natty.git.
Then fakeroot ./debian/rules clean fakeroot ./debian/rules editconfigs Turn on Thumb2 If you look in the output you will see the file in /tmp that was used to assemble the config. If you want to build the packaged kernel then go follow along... ## Make a couple of changes in order to cross compile: ## turn off tools (actually do_tools is already off for omap) sed -i -e 's/do_tools.*=.*/do_tools = false/' debian.linaro/rules.d/armel.mk ## turn off dh_strip sed -i -e 's/dh_strip.*pkghdr.*/echo skipping dh_strip for cross build/' debian/rules.d/2-binary-arch.mk Then debuild: debuild -eCROSS_COMPILE=arm-linux-gnueabi- -nc -ns -aarmel -b If you have any questions please ask. John On Fri, Feb 25, 2011 at 4:07 AM, Dave Martin <dave.mar...@linaro.org> wrote: > On Thu, Feb 24, 2011 at 3:19 PM, John Rigby <john.ri...@linaro.org> wrote: >> Dave, >> >> Not sure if you noticed in the IRC logs so here is what happened for >> the packaged release. >> >> Pulled latest linux-linaro-2.6.38 that has your patches. >> >> Fixed arch/arm/mach-omap2/Makefile to allow smc instructions in >> arch/arm/mach-omap2/sleep34xx.S >> >> Disabled CONFIG_BINFMT_AOUT. >> >> The resulting kernel builds and boots but some modules have problems: >> >> $ modprobe fat >> fat: unknown relocation: 102 >> FATAL: Error inserting vfat >> >> So if we had deployed this kernel we would have images that are not >> upgradeable since we need access to the fat partition to install new >> uImage and uInitrd. >> >> On the positive side we did get some testing and know there is at >> least one module relocation problem. >> >> John > > Thanks for trying it. I confess I hadn't tested modules much, since > module support with Thumb-2 has been in the kernel for ages and is not > arch-specific. > > Can you give me a pointer to the exact config which was used, so I can > try and reproduce it? Is there a build log? > > IIUC, that relocation should not be ending up in modules: it's a short > branch with range +/-2K, so fixup would rarely succeed. > > Maybe there is a tools issue, or some missing processing step when > .kos get generated... > > Cheers > ---Dave > _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev