linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: i810/i815 2.5 framebuffer driver
Date: 11 Jun 2002 02:45:48 +0800	[thread overview]
Message-ID: <1023734576.553.1.camel@daplas> (raw)

Hi,

Hi, I have ported the i810fb to the 2.5 API.  I've tried to follow the
2.5 API as closely as possible and used only the gen_* functions as much
as possible.

The 2.4 i810 framebuffer driver has been posted in
http://www.sourceforge.net/projects/i810fb for sometime and has been
downloaded quite a number of times.  I've also received a number of mail
from people asking me if I should send the driver to be included to the
mainstream kernel.  I tell them it's not ready yet.  Because the driver
is dependent on agpgart, I have to modify the agpgart code just a bit so
agpgart gets loaded before the framebuffer at boot time.

So, I worked around this "misordered" loading by just having the fb
create and use its own agpgart services until the kernel agpgart becomes
available.  Once the kernel agpgart is available, the driver frees its
own and will start using the kernel's.  

I'm hopefully asking for people who have time to review the code and
perhaps give some thoughts on the agpgart thing.  And for those who have
the hardware, to test it as well.    

Thanks in advance.

Tony

PS:  the diff is against linux-2.5.21

http://i810fb.sourceforge.net/linux-2.5.21-i810fb.diff.gz

The actual source is in:

http://i810fb.sourceforge.net/i810fb.tar.gz






_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

                 reply	other threads:[~2002-06-10 18:43 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=1023734576.553.1.camel@daplas \
    --to=adaplas@pol.net \
    --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 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).