[PATCH 5/5] drm: Enable markdown^Wasciidoc for gpu.tmpl

Daniel Vetter daniel at ffwll.ch
Sat Dec 12 03:13:45 PST 2015


On Fri, Dec 11, 2015 at 03:12:26PM -0700, Jonathan Corbet wrote:
> On Wed, 25 Nov 2015 18:07:59 +0100
> Daniel Vetter <daniel.vetter at ffwll.ch> wrote:
> 
> > Unfortunately the entire improved docbook project died at KS in a
> > massive bikeshed. So we need to carry this around in drm private trees
> > forever :(
> 
> I don't think that's an entirely helpful way to look at things, honestly.
> Changing how the docs system works affects a lot of people, they're going
> to have input on the matter.
> 
> And I sure hope it hasn't "died".  The posting of these patches suggests
> that perhaps it has not.

Hm, I think I fumbled the cc for the cover letter:

http://www.spinics.net/lists/intel-gfx/msg81351.html

In short it hasn't died, and 4.5 will have a few thousand more lines of
doc already employing asciidoc (and ofc also the other stuff that already
landed in 4.4). I just figured there's no way this could get it, and I'd
much rather improve the docs themselves than trying to convince core
kernel folks that this might be useful.

> Anyway, I wanted to say that, my silence notwithstanding, I haven't just
> dropped these.  I had some hassles to deal with (replacing the entire LWN
> server infrastructure, for example) but those are done; I hope to be able
> to mess with this stuff a bit in the very near future.
> 
> Have the table-rendering issues that Graham talked about before gotten any
> better with the newer scheme?

I haven't tackled the table conversion story yet, but one reason for me to
switch to asciidoc (besides that Dave thought it was a good idea) was the
better table support. I haven't tried, but it /should/ be powerful enough.
Another bonus is in-line figures as asciiart that get rendered to png. But
haven't done the integration work on that yet either.

Anyway things seem to work and I'm happy.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch


More information about the dri-devel mailing list