On 23/09/15 18:22, Jeremy Linton wrote:
Marc, |FWIW, mainline booting with this patch on Juno r1 with ACPI enabled dies a |horrible death: Sorry about the delay, I didn't see this message. <trimmed> |How did you get this to work? Firmware release? Yes, it's a firmware problem with the ACPI tables. It is likely you need _DSD changes for the SMSC. If your trying to run juno with ACPI there are a few other ACPI table changes you will need beyond what was in the last linaro release. I wanted to just provide a direct link to the correct firmware in this response, but it seems the required version is sort of up in the air at the moment. Be assured I will really push on this next week, and will provide a follow up here. Originally, the lack of DSD wasn't a problem, but as this patch evolved the fact that it consolidates a number of configuration code paths balancing that got tricky, and ACPI machines with "bad" tables were the victims (rather than breaking something I can't control).
Even now absence of _DSD *should* continue to be just fine. We can bailout without initializing the device. Pulling the entire kernel down just because of an incomplete device entry make no sense IMO.
In the meantime, if this is blocking anyone I can provide instructions on how to update the required ACPI tables.
I found that the driver has issues even with DT missing some of the optional properties. We need to fix it but I don't have much knowledge of the driver and also not sure how these properties are defined in ACPI/DSD world i.e. required vs optional. Regards, Sudeep -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
