From: Lubomir Rintel <lkundrak@v3.sk>
To: Pavel Machek <pavel@ucw.cz>
Cc: Olof Johansson <olof@lixom.net>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] ARM: dts: mmp2: add OLPC XO 1.75 machine
Date: Mon, 5 Aug 2019 11:56:00 +0200 (CEST) [thread overview]
Message-ID: <1387772868.4330.1564998960018.JavaMail.zimbra@v3.sk> (raw)
In-Reply-To: <20190803085824.GB8224@amd>
----- On Aug 3, 2019, at 10:58 AM, Pavel Machek pavel@ucw.cz wrote:
> On Fri 2019-08-02 12:33:26, Lubomir Rintel wrote:
>> This is a fairly complete description of an OLPC XO 1.75 laptop.
>> What's missing for now is the GPU, LCD controller, DCON, the panel and
>> audio.
>
> Ok, but I need GPU/LCD/panel... that's my only output. Is video
> expected to work in 5.2? Does the firmware pass right device tree,
> including the GPU/LCD/DCON?
The firmware (and the dts) uses a simple-framebuffer. You won't get
any nifty features, but you'll get a framebuffer.
Hopefully we'll get a proper DRM video soon. The status is roughly
as follows:
LCDC: potentially supported by the Armada DRM driver. Patches sent to
Russell King some months ago, not there yet. I'd prefer not to nag him.
DCON: Russell dislikes the idea of a DRM bridge, DRM maintainers prefer
if the driver was not a DRM encoder driver. This seems to require
quite some work to fix [1].
[1] https://www.spinics.net/lists/dri-devel/msg201927.html
GPU: supported by the etnaviv driver, good enough for 2D acceleration
to work with xorg-x11-video-armada driver. 3D (weston and mutter alike)
is broken. To add this to the device tree, the clock and power needs
to be figured out.
> Is there config somewhere I could use?
>
> Thanks a lot,
> Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures)
> http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2019-08-05 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 10:33 [PATCH v2 0/6] ARM: dts: mmp2: devicetree updates Lubomir Rintel
2019-08-02 10:33 ` [PATCH v2 1/6] ARM: dts: mmp2: trivial whitespace fix Lubomir Rintel
2019-08-02 10:33 ` [PATCH v2 2/6] ARM: dts: mmp2: fix the SPI nodes Lubomir Rintel
2019-08-02 10:33 ` [PATCH v2 3/6] ARM: dts: mmp2: rename the USB PHY node Lubomir Rintel
2019-08-02 10:33 ` [PATCH v2 4/6] ARM: dts: mmp2: add camera interfaces Lubomir Rintel
2019-08-02 10:33 ` [PATCH v2 5/6] ARM: dts: mmp2: specify reg-shift for the UARTs Lubomir Rintel
2019-08-02 10:33 ` [PATCH v2 6/6] ARM: dts: mmp2: add OLPC XO 1.75 machine Lubomir Rintel
2019-08-03 8:58 ` Pavel Machek
2019-08-05 9:56 ` Lubomir Rintel [this message]
2019-08-03 8:59 ` [PATCH v2 0/6] ARM: dts: mmp2: devicetree updates Pavel Machek
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=1387772868.4330.1564998960018.JavaMail.zimbra@v3.sk \
--to=lkundrak@v3.sk \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
Powered by JetHome