linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [FBDEV]: Framebuffer driver for Intel 810/815 chipsets
Date: 11 Dec 2002 15:46:21 +0500	[thread overview]
Message-ID: <1039603490.1147.80.camel@localhost.localdomain> (raw)

James,

It seems the fbdev framework is stable enough, and already in the
development tree.  So, I'm submitting a driver for the Intel 810/815 for
review and perhaps inclusion to your tree (to get more testing), and
hopefully merge with Linus's tree.

The patch is against linux-2.5.51, but will not work yet because of 2
reasons:

1. agpgart is not working for the i810
2. support for early agp initialization needs to be added.

Once #1 is fixed, the driver should work as a module.  And once #2 gets
included, the driver can be compiled statically.  Dave Jones (thanks for
the help, by the way) has already #2 in his tree (tested and works), and
is currently working on #1 (I have a hacked version at home).

The driver should be compliant with fbdev-2.5, and should support most
if not all features that are to be expected (modularity, state saving
and restoring, full hardware support, etc).  One thing also that's very
important for many people is that the driver will work with XFree86 with
its native i810 drivers without further modification, and quite stably
too.

The patch is at
http://i810fb.sourceforge.net/linux-2.5.51-i810fb.diff.gz

Thanks,

Tony

             reply	other threads:[~2002-12-11 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 10:46 Antonino Daplas [this message]
2002-12-12 18:45 ` [FBDEV]: Framebuffer driver for Intel 810/815 chipsets James Simmons
2002-12-20 21:22 ` James Simmons

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=1039603490.1147.80.camel@localhost.localdomain \
    --to=adaplas@pol.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@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).