From: "Frank Wunderlich" <frank-w@public-files.de>
To: "Daniel Vetter" <daniel@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
Alexander Ryabchenko <d3adme4t@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
CK Hu <ck.hu@mediatek.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Aw: Re: [PATCH] drm/mediatek: Add MTK Framebuffer-Device (mt7623)
Date: Thu, 10 Jan 2019 20:01:37 +0100 [thread overview]
Message-ID: <trinity-0da588a3-1277-4421-ad6b-1f6aeb129dd6-1547146897687@3c-app-gmx-bs35> (raw)
In-Reply-To: <CAKMK7uEqxz4TAt_iwEC+dMWboVxCeCduyABsSwD0Ns7k=Z_UWA@mail.gmail.com>
Hi Daniel,
> > Would be good to use the new generic fbdev emulation code here, for even
> > less code. Or at least know why this isn't possible to use for mtk (and
> > maybe address that in the core code). Hand-rolling fbdev code shouldn't be
> > needed anymore.
>
> Back on the mailing list, no private replies please:
i don't wanted to spam all people with dumb questions ;)
> For examples please grep for drm_fbdev_generic_setup(). There's also a
> still in-flight series from Gerd Hoffmann to convert over bochs. That,
> plus all the kerneldoc linked from there should get you started.
> -Daniel
this is one of google best founds if i search for drm_fbdev_generic_setup:
https://lkml.org/lkml/2018/12/19/305
not very helpful...
so i tried kernel-doc
https://www.kernel.org/doc/html/latest/gpu/drm-kms-helpers.html?highlight=drm_fbdev_generic_setup#c.drm_fbdev_generic_setup
which is nice function-reference but i've found no generic workflow
as the posted driver is "only" a driver ported from kernel 4.4 by Alexander, i don't know if this new framework can be used and which parts need to be changed. I only try to bring his code Mainline....
Maybe CK Hu can help here because driver is originally from him and he knows internals. Or maybe you can help here?
i personally make my first steps as spare-time kernel-developer :)
regards Frank
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-10 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190102084917.4049-1-frank-w@public-files.de>
2019-01-07 10:36 ` [PATCH] drm/mediatek: Add MTK Framebuffer-Device (mt7623) Daniel Vetter
2019-01-08 13:40 ` Daniel Vetter
2019-01-10 19:01 ` Frank Wunderlich [this message]
2019-01-10 20:02 ` Daniel Vetter
2019-01-11 3:20 ` CK Hu
2019-01-11 9:20 ` Daniel Vetter
2019-01-11 9:49 ` CK Hu
2019-01-11 10:25 ` Daniel Vetter
2019-01-11 16:07 ` Noralf Trønnes
2019-01-14 2:02 ` CK Hu
2019-01-11 18:23 ` Aw: Re: " Frank Wunderlich
2019-01-11 1:31 ` Aw: " CK Hu
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=trinity-0da588a3-1277-4421-ad6b-1f6aeb129dd6-1547146897687@3c-app-gmx-bs35 \
--to=frank-w@public-files.de \
--cc=airlied@linux.ie \
--cc=ck.hu@mediatek.com \
--cc=d3adme4t@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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=p.zabel@pengutronix.de \
/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).