The omap3_evm_defconfig needs to be updated. Else, build fails with: LD init/built-in.o LD .tmp_vmlinux1 arm-none-linux-gnueabi-ld: no machine record defined arm-none-linux-gnueabi-ld: no machine record defined make: *** [.tmp_vmlinux1] Error 1 "make oldconfig" did not help either. I 'hacked' a defconfig with using omap_3430sdp_defconfig as reference for the build to be successful. Will need to review it later in the night before I send a patch... Best regards, Sanjeev -----Original Message----- From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Tony Lindgren Sent: Monday, August 11, 2008 8:56 PM To: linux-omap@xxxxxxxxxxxxxxx; Sakari Ailus; Hiroshi DOYU; Eduardo Valentin Subject: Git tree updated to v2.6.27-rc2, help needed Hi all, I've updated our git tree to v2.6.27-rc2, and looks like we still have a bunch of issues to solve: - DSP compile is broken as now device_create() is same as device_create_drvdata(). So device_create() expects some some drvdata to be set also in drivers/dsp/dspgateway/task.c and drivers/dsp/dspgateway/dsp_ctl_core.c. Hiroshi, care to take a look at the DSP issue? - V4L drivers init needs to be fixed as the configuration is now passed in some other struct. This affects at least omap24xxcam.c and radio-tea5761.c. Sakari & Eduardo, can you look at these issues? - Booting fails early on 3430sdp for some reason - Alignment error on omap2/3. This seems to happen also with 718fc6cd4db902aa2242a736cc3feb8744a4c71a reverted? - Pending patches to isp1301_omap.c need to be tested on H2 and H4 USB - Cpufreq is oopses on at least omap1 I'll continue looking at the 3430sdp boot issues on Tuesday and then update to current mainline with the header changes. Cheers, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
