Re: Broken device trees for exynos in linux-next

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

 



Kukjin,

On Thu, Aug 22, 2013 at 2:55 AM, Kukjin Kim <kgene@xxxxxxxxxx> wrote:
> Yeah, it can be used for test. But there are many differences between
> exynos_defconfig and exynos5440_defconfig...PCIe, GbE, HugeTLB and KVM...so
> I'm still wondering how to handle it without other defconfig.
>
> Olof, do you still having objection for exynos5440_defconfig? If so, OK I
> will revert exynos5440_defconfig for now so that I could pull out the
> 'defconfig' branch to arm-soc for upcoming merge window. Then, let's discuss
> again :)

As far as I see it, you have two options:

1. Add the needed drivers to multi_v7_defconfig and use that for your platform.
2. Add them to both multi_v7_defconfig and exynos_defconfig.

Enabling the new drivers on exynos_defconfig does no harm.

I don't want to see a new defconfig for this.


-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux SoC Development]     [Linux Rockchip Development]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Linux SCSI]     [Yosemite News]

  Powered by Linux