Re: [Linux-fbdev-devel] [PATCH 1/3] radeonfb: Fix 64 bits resources on 32 bits archs
On Wed, 2008-04-23 at 02:57 -0700, David Miller wrote: > > 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 :-) True :-) But I'd still like to fix the fb API for the sake of things like directfb etc... Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [Linux-fbdev-devel] [PATCH 1/3] radeonfb: Fix 64 bits resources on 32 bits archs
From: Michel Dänzer <[EMAIL PROTECTED]> 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 :-) ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [Linux-fbdev-devel] [PATCH 1/3] radeonfb: Fix 64 bits resources on 32 bits archs
On Wed, 2008-04-23 at 11:32 +0200, Michel Dänzer wrote: > > 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... Right. And I'm happy to go fix what remains, don't get me wrong here :-) We all know how stupid legacy code can be ! I'll try to get some patches to expose a new version of the structure sometimes in the upcoming week or two (we'll see what time permits) and then see about fixing X drivers that need fixing, though hopefully with pci-rework being upstream now, that shouldn't be many. The main issue is directfb. I hope they'll catch up with the new ioctls. Ben. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [Linux-fbdev-devel] [PATCH 1/3] radeonfb: Fix 64 bits resources on 32 bits archs
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... -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
