From: "B.G. Bruce" <bgb@nt-nv.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: agp and framebuffer (intelfb) - your milage may vary
Date: Thu, 27 Jan 2005 08:25:47 -0400 [thread overview]
Message-ID: <1106828747.4566.82.camel@master.vms.security> (raw)
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
Hi,
with the patches/linux-2.6.9/{agpgart,drm}.patch patches applied
(shouldn't there be a symlink to linux-2.6.10?) and this ultrasimplitic
(and probably WRONG!) patch, I have agp and the intelfb working in
dom0. I'll try other domains later today an post my results. I would
appreciate it if someone who knows the xen agp subsystem (in particular
the agp_acquire_backend) better would look over the intelfb.patch and
post any improvements (I don't like taking out the checks made on
agp_acquire_backend(), but with them left in, I get "intelfb: cannot
acquire agp").
Thanks,
B.
[-- Attachment #2: intelfb.patch --]
[-- Type: text/x-patch, Size: 691 bytes --]
diff -Naur linux-xen/drivers/video/intelfb.orig/intelfbdrv.c linux-xen/drivers/video/intelfb/intelfbdrv.c
--- linux-xen/drivers/video/intelfb.orig/intelfbdrv.c 2005-01-26 12:04:02.000000000 -0400
+++ linux-xen/drivers/video/intelfb/intelfbdrv.c 2005-01-26 12:49:28.000000000 -0400
@@ -605,11 +605,12 @@
}
/* Use agpgart to manage the GATT */
- if (agp_backend_acquire()) {
- ERR_MSG("cannot acquire agp\n");
- cleanup(dinfo);
- return -ENODEV;
- }
+ agp_backend_acquire();
+/* if (agp_backend_acquire()) {
+* ERR_MSG("cannot acquire agp\n");
+* cleanup(dinfo);
+* return -ENODEV;
+* } */
/* get the current gatt info */
if (agp_copy_info(>t_info)) {
next reply other threads:[~2005-01-27 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 12:25 B.G. Bruce [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-28 8:43 agp and framebuffer (intelfb) - your milage may vary Ian Pratt
2005-01-28 12:36 ` B.G. Bruce
2005-01-28 17:21 ` B.G. Bruce
2005-01-28 19:13 ` Jacob Gorm Hansen
2005-02-09 1:18 Ian Pratt
2005-02-09 1:23 ` B.G. Bruce
2005-02-09 2:25 ` Jacob Gorm Hansen
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=1106828747.4566.82.camel@master.vms.security \
--to=bgb@nt-nv.com \
--cc=xen-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.