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>,
Rik van Riel <riel@redhat.com>
Subject: RE: agp and framebuffer (intelfb) - your milage may vary
Date: Fri, 28 Jan 2005 13:21:08 -0400 [thread overview]
Message-ID: <1106932867.4566.213.camel@master.vms.security> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D123599@liverpoolst.ad.cl.cam.ac.uk>
Well, you can forget the patch - ti's not needed. I don't know what I
was doing wrong, but a rebuild from scratch today (same versions of
everything) and it works correctly WITHOUT the patch. Wednesday, when I
did this (again from scratch)I needed the patch. I must be losing my
mind, however you can add the intelfb with a 865g chipset to your list
of known working. It didn't make much sense to me from the start, so
I'll write it off to user error/stupidity on my part.
B.
On Fri, 2005-01-28 at 04:43, Ian Pratt wrote:
> > with the patches/linux-2.6.9/{agpgart,drm}.patch patches applied
> > (shouldn't there be a symlink to linux-2.6.10?)
>
> There's an argument that we should automatically apply these patches and
> build AGP and DRM support as modules for our xen0 kernels. It would be
> good to know which drivers have actually been tested and work.
>
> Rik: did you have any luck feeding the agpgart and drm patches up
> stream?
>
> > 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").
>
> Which of the error codes is it returning? There's nothing special about
> AGP support on arch xen, its just that Xen is rather stricter about what
> drivers are allowed to get away with, requring some fixes.
>
> int agp_backend_acquire(void)
> {
> if (agp_bridge->type == NOT_SUPPORTED)
> return -EINVAL;
> if (atomic_read(&agp_bridge->agp_in_use))
> return -EBUSY;
> atomic_inc(&agp_bridge->agp_in_use);
> return 0;
> }
>
> Ian
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-28 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2005-01-28 19:13 ` Jacob Gorm Hansen
2005-01-31 13:07 ` Kurt Garloff
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 1:18 Ian Pratt
2005-02-09 1:23 ` B.G. Bruce
2005-02-09 2:25 ` 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=1106932867.4566.213.camel@master.vms.security \
--to=bgb@nt-nv.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=riel@redhat.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.