From: CK Hu <ck.hu@mediatek.com>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: "Matthias Brugger" <matthias.bgg@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
srv_heupstream@mediatek.com, "David Airlie" <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"\"Noralf Tr�nnes\"" <noralf@tronnes.org>,
linux-mediatek@lists.infradead.org,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: Aw: Re: [PATCH 2/2] drm/mediatek: Add Mediatek framebuffer device
Date: Tue, 19 Mar 2019 11:12:09 +0800 [thread overview]
Message-ID: <1552965129.7881.5.camel@mtksdaap41> (raw)
In-Reply-To: <trinity-1c369adc-b489-43dd-87c9-5b43d49561c5-1547991406711@3c-app-gmx-bs40>
Hi, Frank:
My platform's fbcon works correctly, so I've applied this series to [1].
If you have another patch, I'd treat it as a bug-fix.
[1]
https://github.com/ckhu-mediatek/linux.git-tags/commits/mediatek-drm-fixes-5.1
Regards,
CK
On Sun, 2019-01-20 at 14:36 +0100, Frank Wunderlich wrote:
> Tested with mmsys-Patch, but same result, no fbcon, tft is switched on but i see no kernel-log
>
> after boot is finished, i see X-server, until this point i see only black screen
>
> regards Frank
>
>
> > Gesendet: Freitag, 18. Januar 2019 um 09:39 Uhr
> > Von: "Matthias Brugger" <matthias.bgg@gmail.com>
> > may it be the not yet fixed mmsys compatible problem?
> > Frank, did you test with my last series [1]?
> > [1] https://patchwork.kernel.org/cover/10686345/
next prev parent reply other threads:[~2019-03-19 3:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 1:39 [PATCH 1/2] drm/mediatek: Implement gem prime vmap/vunmap function CK Hu
2019-01-16 1:39 ` [PATCH 2/2] drm/mediatek: Add Mediatek framebuffer device CK Hu
2019-01-17 14:14 ` Aw: " Frank Wunderlich
2019-01-18 1:46 ` CK Hu
2019-01-18 8:39 ` Matthias Brugger
2019-01-18 12:33 ` Aw: " Frank Wunderlich
2019-01-20 13:36 ` Frank Wunderlich
2019-03-19 3:12 ` CK Hu [this message]
2019-03-19 16:52 ` Aw: " Frank Wunderlich
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=1552965129.7881.5.camel@mtksdaap41 \
--to=ck.hu@mediatek.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank-w@public-files.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=noralf@tronnes.org \
--cc=p.zabel@pengutronix.de \
--cc=srv_heupstream@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).