From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: tbm@cyrius.com
Subject: Re: [PATCH] Fix maxine compilation error
Date: Wed, 24 May 2006 08:20:08 +0800 [thread overview]
Message-ID: <4473A6B8.2040709@gmail.com> (raw)
In-Reply-To: <20060509210114.GA13897@deprecation.cyrius.com>
Martin Michlmayr wrote:
> I have no idea if the patch below is correct.
It's correct.
> Are fb_get_fix/fb_get_var
> still needed?
With 2.6, not anymore.
> Is there any information about converting fb drivers to
> the 2.6 api?
None in terms of conversion. But skeletonfb.c in the video
directory might help.
Tony
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
prev parent reply other threads:[~2006-05-24 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 21:01 [PATCH] Fix maxine compilation error Martin Michlmayr
2006-05-24 0:20 ` Antonino A. Daplas [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=4473A6B8.2040709@gmail.com \
--to=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=tbm@cyrius.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).