[oe] RFC: omap2 support.
Koen Kooi
koen at dominion.kabel.utwente.nl
Mon Aug 13 21:43:18 UTC 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Khem Raj schreef:
> Hi
>
> This adds support of omap2430sdp board. I have added recipe for a new kernel
> and u-boot. The angstrom-2008.1 build with MACHINE=omap2430sdp till the kernel.
> Kernel is having issues due to a compile problem.
Looks pretty, some minor issues, see below.
- --- conf/machine/omap2430sdp.conf a9af9a075c6a90b2d65f3966f1fb4b8fc1eb662e
+++ conf/machine/omap2430sdp.conf a9af9a075c6a90b2d65f3966f1fb4b8fc1eb662e
@@ -0,0 +1,17 @@
+#@TYPE: Machine
+#@NAME: ARM 1136 cpu on OMAP2430 SDP board
+#@DESCRIPTION: Machine configuration for the OMAP 2430 SDP development board with a
arm1136 processor.
+
+TARGET_ARCH = "arm"
+PACKAGE_EXTRA_ARCHS = "armv5te armv6"
that should be PACKAGE_EXTRA_ARCHS = "armv4t armv5te armv6"
+PREFERRED_VERSION_u-boot = "omap2430sdp"
'omap2430sdp' is not a proper version (see below)
+PREFERRED_PROVIDERS += "virtual/${TARGET_PREFIX}depmod:module-init-tools-cross"
MACHINE_FEATURES = "kernel26" should take care of that
+BOOTSTRAP_EXTRA_RDEPENDS += "modutils-collateral"
That shouldn't be needed
============================================================
- --- packages/linux/linux-omap2_git.bb f7dd822d0aa5d74967b00c6b49bde9755d89e1f8
+++ packages/linux/linux-omap2_git.bb f7dd822d0aa5d74967b00c6b49bde9755d89e1f8
@@ -0,0 +1,13 @@
+require linux-omap.inc
+
+FILESDIR = "${@os.path.dirname(bb.data.getVar('FILE',d,1))}/linux-omap2-git"
+PV = "2.6+git${SRCDATE}"
That should be PV = "2.6.<micro release number>+git${SRCDATE}"
- --- packages/uboot/u-boot_omap2430sdp.bb fe281ead4f04210e0876f455ed429333d5f6d40d
That should be u-boot-omap2430_1.<minor version>.<microversion>.bb, so we know which uboot
version it was originally based on.
- --- conf/machine/include/tune-arm1136jf-s.conf b8cdf4c6533420f583f03a1a756edec48bc2e823
+++ conf/machine/include/tune-arm1136jf-s.conf 3a32f71999f930e828ad32e4ce1e7af1b4dc9662
@@ -1,2 +1,2 @@
- -TARGET_CC_ARCH = "-march=armv6 -mtune=arm1136jf-s -mfpu=vfp"
+TARGET_CC_ARCH = "-march=armv6j -mtune=arm1136jf-s -mfpu=vfp -mfloat-abi=softfp"
What does -mfloat-abi=softfp" imply, and shouldn't TARGET_FPU take care of that?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGwNB2MkyGM64RGpERAl/5AKCgCr7+XYfYcaGFCcuNHruNzyuFRACghfso
5A6AOBkSHh+ZHiLwjTqSTuc=
=u0ys
-----END PGP SIGNATURE-----
More information about the Openembedded-devel
mailing list