From: "B.G. Bruce" <bgb@nt-nv.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>,
Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Subject: RE: agp and framebuffer (intelfb) - your milage may vary
Date: Tue, 08 Feb 2005 21:23:53 -0400 [thread overview]
Message-ID: <1107912233.9884.165.camel@master.vms.security> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1237CD@liverpoolst.ad.cl.cam.ac.uk>
Yes, my issue has disappeared and at least for me the agp patch works
great.
B.
On Tue, 2005-02-08 at 21:18, Ian Pratt wrote:
> If you apply the agp.patch, I'd be interested to know if this issue is
> now fixed.
>
> I think there's a pretty good argument for applying the patch be default
> now...
>
> Ian
>
> > 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.
> >
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-09 1:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 1:18 agp and framebuffer (intelfb) - your milage may vary Ian Pratt
2005-02-09 1:23 ` B.G. Bruce [this message]
2005-02-09 2:25 ` Jacob Gorm Hansen
-- strict thread matches above, loose matches on Subject: below --
2005-01-28 8:43 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-01-27 12:25 B.G. Bruce
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=1107912233.9884.165.camel@master.vms.security \
--to=bgb@nt-nv.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.