On Fri, May 9, 2014 at 11:20 PM, Andreas Färber <afaerber@xxxxxxx> wrote: > Am 08.05.2014 01:40, schrieb Alex Courbot: >> On 05/08/2014 12:57 AM, Stephen Warren wrote: >>> On 05/06/2014 09:18 PM, Alexandre Courbot wrote: >>>> Console rotation is needed for devices like Tegra Note 7 and NVIDIA >>>> SHIELD to get the boot console in the expected orientation. >>> >>> I've squashed this into Tegra's for-3.16/defconfig branch. >>> >>> Can you please also update multi_v7_defconfig, and send that change to >>> arm-soc (arm@xxxxxxxxxx) to be applied. Thanks. >> >> I omitted doing this for now because the devices that require this >> option (TN7/SHIELD) need a custom build with appended DTB and/or >> command-line anyway. Therefore they cannot use a multi-mach kernel > > What does appending a .dtb have to do with whether or not to use a > multi-mach kernel? We package zImage/uImage and .dtbs separately, so > surely the multi_v7_defconfig should be kept working with Tegra devices. > Appending a .dtb only comes into play for preparing installation images. When appending a dtb the kernel image must also be built with CONFIG_ARM_APPENDED_DTB, which I guess is not an option we want to add by default to Tegra and probably even less to multi_v7. So since the kernel config needs to be changed anyway, I thought we would always want to use tegra_defconfig as a basis for these devices. Not that adding CONFIG_FRAMEBUFFER_CONSOLE_ROTATION to multi_v7 would inflate the resulting kernel much, though. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
