Re: OMAP totally fucked?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Arnd & Olof,

* Tony Lindgren <tony@xxxxxxxxxxx> [120303 12:49]:
> 
> Anyways, we should revert commit 72b026a4 because of the
> breakage it causes.

Correction, we should revert commit c295fb63. The above commit
is wrong and only exists on my machine.

Arnd & Olof, can you please revert commit c295fb63 (ARM: OMAP2+:
Fix multiple randconfig errors with SOC_OMAP and SOC_OMAP_NOOP)
in omap/fixes-non-critical?

This commit by me generates bloated .config files with make
oldconfig on existing .config files.

Further mach-omap2/Kconfig changes can then wait until they're
properly tested..
 
> Below is a second attempt for the Kconfig changes. Now the
> CONFIG_MACH_ needs to be set in your seed .config.

..as this patch needs at least one more change to add a submenu
for MACH_OMAP_GENERIC to select the SoC type. Other boards
should not need that, so it might be best to make it available
only for MACH_OMAP_GENERIC.

Regards,

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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux