From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: tegra: add Acer Chromebook 13 device tree
Date: Wed, 13 Aug 2014 11:12:01 -0600 [thread overview]
Message-ID: <53EB9C61.1070406@wwwdotorg.org> (raw)
In-Reply-To: <CAL1qeaGxcp4okVTYCMj0zMh-4HzsGLBvngv0+A1m8o3sZPDj2A@mail.gmail.com>
On 08/13/2014 11:04 AM, Andrew Bresticker wrote:
> On Wed, Aug 13, 2014 at 9:51 AM, Stephen Warren <swarren@wwwdotorg•org> 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?
next prev parent reply other threads:[~2014-08-13 17:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 1:56 [PATCH 1/2] ARM: tegra: add Acer Chromebook 13 device tree Dylan Reid
2014-08-13 8:53 ` Thierry Reding
2014-08-13 16:23 ` Andrew Bresticker
2014-08-13 16:51 ` Olof Johansson
2014-08-13 16:57 ` Stephen Warren
2014-08-13 16:51 ` Stephen Warren
2014-08-13 16:55 ` Olof Johansson
2014-08-13 17:04 ` Andrew Bresticker
2014-08-13 17:12 ` Stephen Warren [this message]
2014-08-13 17:17 ` Andrew Bresticker
2014-08-13 18:42 ` Dylan Reid
2014-08-13 17:10 ` Stephen Warren
2014-08-13 17:23 ` Olof Johansson
2014-08-13 17:31 ` Stephen Warren
2014-08-13 17:37 ` Olof Johansson
2014-08-13 20:17 ` Stephen Warren
2014-08-13 19:07 ` Dylan Reid
2014-08-13 19:56 ` Stephen Warren
2014-08-14 8:40 ` Dylan Reid
2015-01-13 17:49 ` Tomeu Vizoso
2015-01-14 0:32 ` Dylan Reid
2015-01-14 7:02 ` Tomeu Vizoso
2015-01-15 7:50 ` Thierry Reding
2015-01-15 12:18 ` Tomeu Vizoso
2015-01-15 17:18 ` Stephen Warren
2015-01-19 9:01 ` Tomeu Vizoso
2015-01-19 19:29 ` Andrew Bresticker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53EB9C61.1070406@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox