From: Daniel Vetter <daniel@ffwll.ch>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Tomi Valkeinen" <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Sudip Mukherjee" <sudipm.mukherjee@gmail.com>,
"Teddy Wang" <teddy.wang@siliconmotion.com>,
"Arnaud Patard" <arnaud.patard@rtp-net.org>,
airlied@linux.ie, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] staging: remove fbdev drivers
Date: Fri, 9 Dec 2016 09:13:35 +0100 [thread overview]
Message-ID: <20161209081335.q2bnqmtoo2xtcgri@phenom.ffwll.local> (raw)
In-Reply-To: <1481233393.26959.53.camel@kernel.crashing.org>
On Fri, Dec 09, 2016 at 08:43:13AM +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2016-12-09 at 08:23 +1100, Benjamin Herrenschmidt wrote:
> > > From memory, David claimed you cannot directly work on the fb with a "proper"
> >
> > DRM driver. Maybe I misunderstood but then the DRM shines by its complete
> > absence of useful documentation
>
> That sentence should have been in the past, it does look like
> documentation has been landing in the tree this year ! yay ! I'll go
> off read it.
We've been building up that documentation for years now, not sure where
exactly you've looked in the past ;-)
And to make sure you're looking at the right stuff: Please run
$ make DOCBOOKS="" htmldocs
and then look at Documentation/output/gpu. Otherwise all the kerneldoc
stuff isn't pulled in, and a lot of the overview sections (not just
abi/struct docs) are in there.
And if something looks fishy or doesn't make sense, please raise it here
or on #dri-devel on freenode so that we can improve the docs.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2016-12-09 8:14 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 8:03 [RFC PATCH 0/3] staging: remove fbdev drivers Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 1/3] staging: remove xgifb Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 2/3] staging: remove sm750fb Tomi Valkeinen
2016-11-23 8:03 ` [RFC PATCH 3/3] staging: remove fbtft Tomi Valkeinen
2016-11-23 17:26 ` Noralf Trønnes
2016-11-24 8:36 ` Tomi Valkeinen
2016-11-23 20:12 ` Drew Fustini
2016-11-23 8:19 ` [RFC PATCH 0/3] staging: remove fbdev drivers Daniel Vetter
2016-11-23 8:21 ` Tomi Valkeinen
2016-11-23 8:25 ` Geert Uytterhoeven
2016-11-23 8:45 ` Daniel Vetter
2016-11-23 8:52 ` Greg Kroah-Hartman
2016-11-23 9:12 ` Tomi Valkeinen
2016-11-23 9:49 ` Greg Kroah-Hartman
2016-11-23 10:05 ` Thomas Petazzoni
2016-12-22 20:36 ` Andy Shevchenko
2016-12-08 22:00 ` Sudip Mukherjee
2016-12-08 1:01 ` Benjamin Herrenschmidt
2016-12-08 8:01 ` Tomi Valkeinen
2016-12-08 21:23 ` Benjamin Herrenschmidt
2016-12-08 21:43 ` Benjamin Herrenschmidt
2016-12-09 8:13 ` Daniel Vetter [this message]
2016-12-13 7:36 ` Gerd Hoffmann
2016-12-08 10:10 ` Daniel Vetter
2016-12-08 12:15 ` Geert Uytterhoeven
2016-12-08 14:02 ` Daniel Vetter
2016-12-08 14:22 ` Geert Uytterhoeven
2016-12-08 14:37 ` Thomas Petazzoni
2016-12-08 14:44 ` Geert Uytterhoeven
2016-12-08 15:21 ` Daniel Vetter
2016-12-08 21:34 ` Benjamin Herrenschmidt
2016-12-08 21:57 ` Benjamin Herrenschmidt
2016-12-09 8:34 ` Daniel Vetter
2016-12-09 8:41 ` Daniel Vetter
2016-12-09 11:48 ` Benjamin Herrenschmidt
2016-12-09 13:35 ` Daniel Vetter
2016-12-09 20:27 ` Benjamin Herrenschmidt
2016-12-13 7:18 ` Michel Dänzer
2016-12-09 11:44 ` Benjamin Herrenschmidt
2016-12-09 12:33 ` Geert Uytterhoeven
2016-12-09 13:19 ` Lucas Stach
2016-12-09 13:33 ` Daniel Vetter
2016-12-09 13:57 ` David Herrmann
2016-12-09 14:04 ` Daniel Vetter
2016-12-09 20:29 ` Benjamin Herrenschmidt
2016-12-09 8:30 ` Daniel Vetter
2016-12-08 14:59 ` Jani Nikula
2016-12-08 14:22 ` Daniel Vetter
2016-12-08 21:28 ` Benjamin Herrenschmidt
2016-12-09 0:08 ` Dave Airlie
2016-12-09 8:04 ` Geert Uytterhoeven
2016-12-09 11:40 ` Benjamin Herrenschmidt
2016-12-13 7:33 ` Gerd Hoffmann
2016-12-13 15:17 ` Laurent Pinchart
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=20161209081335.q2bnqmtoo2xtcgri@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=arnaud.patard@rtp-net.org \
--cc=benh@kernel.crashing.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tomi.valkeinen@ti.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).