[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080423.025721.50367920.davem@davemloft.net>
Date: Wed, 23 Apr 2008 02:57:21 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: michel@...gstengraphics.com
Cc: benh@...nel.crashing.org, linux-fbdev-devel@...ts.sourceforge.net,
hollisb@...ibm.com, adaplas@...il.com,
linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
akpm@...ux-foundation.org, dzu@...x.de
Subject: Re: [Linux-fbdev-devel] [PATCH 1/3] radeonfb: Fix 64 bits
resources on 32 bits archs
From: Michel Dänzer <michel@...gstengraphics.com>
Date: Wed, 23 Apr 2008 11:32:07 +0200
> On Wed, 2008-04-23 at 08:21 +1000, Benjamin Herrenschmidt wrote:
> > On Tue, 2008-04-22 at 17:55 +0200, Christian Ehrhardt wrote:
> > > I wanted to ask if there are any known workarounds atm that would
> > > allow me to use my X11 for now?
> >
> > X is doing a mmap of /dev/mem instead of /dev/fb ?
> >
> > You can normally map the fb mapping /dev/fb and then map the registers
> > using /dev/fb at an offset beyond the framebuffer (fix->smem_len).
> >
> > If X is using /dev/mem instead, then it's being stupid and needs to be
> > fixed...
>
> It's up to the driver, and again, the current radeon driver doesn't use
> radeonfb at all anymore...
The only portable thing is for X to use the PCI sysfs mmap() stuff,
which current Xorg servers using libpciaccess do.
I know because I'm typing this from a sparc64 using a Radeon
with current Xorg :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists