From: Alex Buell <alex.buell@munted.org.uk>
To: linux-fbdev@vger.kernel.org
Subject: Framebuffer HOWTO 1.3 released today!
Date: Mon, 09 Aug 2010 13:15:27 +0000 [thread overview]
Message-ID: <1281359727.29955.22.camel@lithium> (raw)
After ten years' hiatus, I have converted the original Framebuffer HOWTO
document from LinuxDoc to DocBook xml. It is now up on my programming
page at http://www.munted.org.uk/programming/
A copy has also gone to the Linux Documentation Project website and
replaces all previous versions.
Enjoy!
I am now about to start writing release 2.0 of this document with
updated details. I know that between kernel 2.2.x and 2.6.x there was a
huge amount of changes made on the framebuffers. In order to bring up to
date I need to know about changes and updates that were made between
2001 to 2010.
All comments welcome!
--
http://www.munted.org.uk
One very high maintenance cat living here.
reply other threads:[~2010-08-09 13:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1281359727.29955.22.camel@lithium \
--to=alex.buell@munted.org.uk \
--cc=linux-fbdev@vger.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;
as well as URLs for NNTP newsgroup(s).