Messages in this thread | | | Date | Wed, 21 Jul 2004 10:41:10 +0100 (IST) | From | Dave Airlie <> | Subject | Re: dri ioctl32 problem on amd64/x86_64 on 2.6.8-rc2 and earlier |
| |
> I have a working direct rendering mechanism in my 64-bit userland. However, > 32-bit software running in a 32-bit chroot environment cannot operate with the > 64-bit drm. I get the following error when executing the 32-bit glxinfo inside > the chroot: >
the DRM has some major 64-bit issues that we need to break backwards compatibility we haven't simply be able to declare a time when the people who need to work on it can spare the amount of time needed together...
I think the plan is to fix the issues in the DRM CVS and try and push them to Linus in one big push which breaks all platforms together and we can have a flag day....
One remaining issue is what types to use in the headers used in both kernel/userspace, we don't want to have two separate headers (why should we?) so what types should we use ... surely someone has done this before..
Regards, Dave. [drm-maintainer]
-- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |