From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Andrew Walrond <andrew@walrond.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Fbdev programming info
Date: Tue, 22 Jun 2004 08:36:54 +0800 [thread overview]
Message-ID: <200406220836.54090.adaplas@hotpop.com> (raw)
In-Reply-To: <200406220011.51968.andrew@walrond.org>
On Tuesday 22 June 2004 07:11, Andrew Walrond wrote:
> Where is the best place to look for fbdev programming information/examples?
> A hour's googling didn't bring up much at all :(
I think you meant user apps for fbdev. I also haven't seen any docs for that.
You can look at the fbutils code for an example. Should be available on the
same site (linux-fbdev.sf.net)
Tony
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-06-22 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 23:11 Fbdev programming info Andrew Walrond
2004-06-22 0:13 ` Antonino A. Daplas
2004-06-22 0:36 ` Antonino A. Daplas [this message]
2004-06-22 12:19 ` Andrew Walrond
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=200406220836.54090.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=andrew@walrond.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.