From: Ulrich Eckhardt <eckhardt@satorlaser.com>
To: linux-mips@linux-mips.org
Subject: Re: fb documentation
Date: Thu, 2 Jun 2005 17:34:47 +0200 [thread overview]
Message-ID: <200506021734.47704.eckhardt@satorlaser.com> (raw)
In-Reply-To: <685359936.20050602164049@wicomtechnologies.com>
Jerry wrote:
> Can anyone point me out to any available information about writing
> framebuffer drivers, fb structure, internals, interactions, driver
> requirements, etc...?
There is a whole mailinglist devoted to writing framebuffer which is hosted at
sourceforge's called fbdev[1], you should try there.
Uli
[1]: linux-fbdev-devel@lists.sourceforge.net
prev parent reply other threads:[~2005-06-02 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 13:40 fb documentation Jerry
2005-06-02 15:34 ` Ulrich Eckhardt [this message]
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=200506021734.47704.eckhardt@satorlaser.com \
--to=eckhardt@satorlaser.com \
--cc=linux-mips@linux-mips.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