--- Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
> > On Fri, 01 Oct 2004 21:11:54 +0100, Keith Whitwell
> > <[EMAIL PROTECTED]> wrote:
> >
> >>Maybe there's a problem with terminology, but when we write to agp
> memory in
> >>the drivers, we are definitely using the GART.
> >
>
Jon Smirl wrote:
On Fri, 01 Oct 2004 21:11:54 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
Maybe there's a problem with terminology, but when we write to agp memory in
the drivers, we are definitely using the GART.
The GART is remapping your addresses, but it's still a normal system RAM access
On Fri, 01 Oct 2004 21:11:54 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
> Maybe there's a problem with terminology, but when we write to agp memory in
> the drivers, we are definitely using the GART.
The GART is remapping your addresses, but it's still a normal system RAM access.
> Keith
>
Jon Smirl wrote:
On Fri, 01 Oct 2004 18:54:50 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
Jon Smirl wrote:
On Fri, 01 Oct 2004 18:05:29 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
Second the DRM code always treats the framebuffer as if it is in
IOMEM. But what about IGP type devices wher
--- Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
> > On Fri, 01 Oct 2004 18:05:29 +0100, Keith Whitwell
> > <[EMAIL PROTECTED]> wrote:
> >
> >>>Second the DRM code always treats the framebuffer as if it is in
> >>>IOMEM. But what about IGP type devices where the framebuffer is in
--- Jon Smirl <[EMAIL PROTECTED]> wrote:
> On Fri, 01 Oct 2004 18:05:29 +0100, Keith Whitwell
> <[EMAIL PROTECTED]> wrote:
> > > This implies that DRM should be passing back two distinct handle
> > > types, one for normal and one for IOMEM, so that the user space app
> > > will use the correct ac
On Fri, 01 Oct 2004 18:54:50 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
> Jon Smirl wrote:
> > On Fri, 01 Oct 2004 18:05:29 +0100, Keith Whitwell
> > <[EMAIL PROTECTED]> wrote:
> >
> >>>Second the DRM code always treats the framebuffer as if it is in
> >>>IOMEM. But what about IGP type device
I note that we (HP)
have just nuked our future IA64 workstations; and as we
shipped the largest volume of such machines (by far), constraints there
will be use of graphics cards on servers, rather than any volume...
- Jim
> I've seen stuff on the web that suggests
Jon Smirl wrote:
On Fri, 01 Oct 2004 18:05:29 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
Second the DRM code always treats the framebuffer as if it is in
IOMEM. But what about IGP type devices where the framebuffer is in
main memory? These only exist on the x86 so treating their framebuffer
a
Jon Smirl wrote:
On Fri, 01 Oct 2004 18:05:29 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
This implies that DRM should be passing back two distinct handle
types, one for normal and one for IOMEM, so that the user space app
will use the correct access function. This is also a pretty good
argume
On Fri, 01 Oct 2004 18:05:29 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
> > Second the DRM code always treats the framebuffer as if it is in
> > IOMEM. But what about IGP type devices where the framebuffer is in
> > main memory? These only exist on the x86 so treating their framebuffer
> > as
On Fri, 01 Oct 2004 18:05:29 +0100, Keith Whitwell
<[EMAIL PROTECTED]> wrote:
> > This implies that DRM should be passing back two distinct handle
> > types, one for normal and one for IOMEM, so that the user space app
> > will use the correct access function. This is also a pretty good
> > argumen
Jon Smirl wrote:
I just spent sometime looking at about a thousand errors from sparse
in the DRM code.
There are two main problems, first DRM makes use of opaque handles
which are passed to user space. These handles can be to normal or
iomem memory. Since the handles are typeless this generates a l
I just spent sometime looking at about a thousand errors from sparse
in the DRM code.
There are two main problems, first DRM makes use of opaque handles
which are passed to user space. These handles can be to normal or
iomem memory. Since the handles are typeless this generates a lot of
sparse err
14 matches
Mail list logo