From: Kris Moore <kris@pcbsd.org>
To: intel-gfx@lists.freedesktop.org
Subject: Intel Legacy Driver / GEM
Date: Fri, 22 Oct 2010 11:58:19 -0400 [thread overview]
Message-ID: <4CC1B49B.9050402@pcbsd.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Somebody recently pointed us to the intel-legacy driver which is GEM-less:
http://cgit.freedesktop.org/~ickle/xf86-video-intel/commit/?h=legacy
In the FreeBSD/PC-BSD world this interests us quite a bit, since we
don't have
GEM / KMS in our kernel as of yet, and have plenty of users
with Intel video hardware. What I'm wondering is how long do you plan on
maintaining this driver, or are you going to update it further at all?
Obviously the long-term fix will be to get GEM / KMS into our kernel,
and then this becomes a non-issue, however that is a bigger project and
we have systems that could use some sort of working driver now :)
Also I'll mention that the FreeBSD foundation is looking to sponsor a
developer who would be interested in working on our GEM/KMS support here
soon. If anybody who could use some extra $$ and would be
interested in working on this, then feel free to let us know.
- --
Kris Moore
PC-BSD Software
iXsystems
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJMwbSbAAoJEDv6T4U6J2HSgnMH/0nZGI3Csf3pKKitqH2XEfMQ
etikY9HUDcn2DGyuWh1ss+SgTEv4Cj1E5wTGgwTYRfkXuSFyugAVWWY9wqwHF6Kg
+P6dWX1jH8y404pqQYBE+1RIat1AQtYkbTw/o8l9tspoXgqb6a+PJ0zHSUBkQSHw
VYP0jKR6nHl6j/nsGprZsVET8R+XTOWUdijEMjBr/nZ5yc2qUAH6A2z9WpEgKqce
iEGmxb/nPCOEW0xyFZraeivx8olU2LjuGBTcUSEvOfx/GoT7wF2JJ1h3wBqGY/Kv
/r5e0dASkS4EtvhuEkzSrW92TFZTV/1KqkvB6GCKBFRvQsuhdyms8QJIKLKNS80=
=yUo1
-----END PGP SIGNATURE-----
next reply other threads:[~2010-10-22 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 15:58 Kris Moore [this message]
2010-10-22 16:29 ` Intel Legacy Driver / GEM Chris Wilson
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=4CC1B49B.9050402@pcbsd.org \
--to=kris@pcbsd.org \
--cc=intel-gfx@lists.freedesktop.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 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.