On Wed, Aug 13, 2014 at 10:12 AM, Stephen Warren <[email protected]> wrote: > On 08/13/2014 11:04 AM, Andrew Bresticker wrote: >> >> On Wed, Aug 13, 2014 at 9:51 AM, Stephen Warren <[email protected]> >> wrote: >>> >>> On 08/13/2014 02:53 AM, Thierry Reding wrote: >>>> >>>> >>>> On Tue, Aug 12, 2014 at 06:56:07PM -0700, Dylan Reid wrote: >>>>> >>>>> >>>>> The Acer Chromebook 13, codenamed "Big", contains an NVIDIA tegra124 >>>>> processor and is similar to the Venice2 reference platform. >>>>> >>>>> The keyboard, USB 2, audio, HDMI, sdcard and emmc have been tested >>>>> and work on the 1366x768 models. I haven't tried on the HD systems >>>>> yet. >>>> >>>> >>>> >>>> Presumably the HD systems will have a different compatible? Is it only >>>> the panel that's different or are there other changes? >>> >>> >>> >>> Yes, we definitely need to plan ahead for the different SKUs. I assume >>> we'll >>> have different board names for each board, which then translates int DT >>> filenames and U-Boot/cbootimage-configs/tegra-uboot-flasher board >> >> >> The firmware does not differentiate between the HD and non-HD boards, >> so it will look for the same compatible string. As I mentioned in my >> response to Thierry, we'd need to parse the EDID to figure out which >> panel is being used. > > > Well, that's if we do it at run-time. We could just have a separate DT per > SKU, couldn't we?
Oh right - yes, that would work. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
