On 3/17/2016 7:27 AM, Catalin Marinas wrote:
On Wed, Mar 16, 2016 at 10:26:08AM -0500, Timur Tabi wrote:
Catalin Marinas wrote:
Why do you need your own defconfig? If it's just on the short term until
all your code is upstream, that's fine, but this goes against the single
Image aim. I would like defconfig to cover all supported SoCs (and yes,
ACPI on by default once we deem it !EXPERT anymore), though at some
point we may need a server/mobile split (if the generated image is too
large, maybe more stuff being built as modules).
Yes, that's exactly it. Ours is an ACPI system, and so we have to have our
own defconfig for now. We're holding off on pushing our own defconfig
changes (enabling drivers, etc) until ACPI is enabled in
arch/arm64/configs/defconfig.
Is there anything that prevents you from providing a dtb/dts for this
SoC?
Note ThunderX's SOC have customers where some are embedded users
(uboot) and server users (UEFI). The cores always have 128 byte
cacheline size. So please don't make this dependent on ACPI. Note the
defconfig works correctly on T88.
Thanks,
Andrew
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html