From: Egbert Eich <eich@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: Thomas Zehetbauer <thomasz@hostmaster.org>,
linux-kernel@vger.kernel.org, idr@us.ibm.com, eich@suse.de
Subject: Re: status of DRM_MGA on x86_64
Date: Mon, 1 Nov 2004 10:51:43 +0100 [thread overview]
Message-ID: <16774.1839.343824.305232@suse.de> (raw)
In-Reply-To: ak@suse.de wrote on , 30 October 2004 at 03:56:24 +0200
Andi Kleen writes:
> Thomas Zehetbauer <thomasz@hostmaster.org> writes:
>
> > On Fre, 2004-10-29 at 12:47 -0700, Ian Romanick wrote:
> > > The problem, which exists with most (all?) DRM drivers, is that data
> > > types are used in the kernel/user interface that have different sizes on
> > > LP32 and LP64. If your kernel is 64-bit, you will have problems with
> > > 32-bit applications.
>
> That was not the reason I disabled it. I reenabled it now in my tree.
>
> > Then either all or no DRM drivers should be enabled on x86_64, the
> > DRM_TDFX, DRM_R128, DRM_RADEON and DRM_SIS are not currently disabled. I
> > vote for enabling all drivers that work with 64-bit applications.
>
> > I wonder if this should be the first and only place where different
> > kernel/userland bitness causes problems. How has this been solved
> > elsewhere?
>
> It was solved long ago for the Radeon driver by Egbert Eich.
> But for some unknown reason the DRI people never merged his patches.
>
I solved it for RADEON, MGA and R128.
It would be interesting to solve this for the i915 driver, too,
and possibly some others.
That it hasn't been merged into DRI yet is a shame. Appearantly
nobody has ever realized why this stuff is useful. Unfortunately
I don't have the time for lobbying it.
It's a very boring undertaking to have to port this from one DRI
version to the next.
Egbert.
next prev parent reply other threads:[~2004-11-01 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1099052450.11282.72.camel@hostmaster.org.suse.lists.linux.kernel>
[not found] ` <1099061384.11918.4.camel@hostmaster.org.suse.lists.linux.kernel>
[not found] ` <41829E39.1000909@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <1099097616.11918.26.camel@hostmaster.org.suse.lists.linux.kernel>
2004-10-30 1:56 ` status of DRM_MGA on x86_64 Andi Kleen
[not found] ` <21d7e99704103004155d2826fb@mail.gmail.com>
2004-10-30 11:17 ` Dave Airlie
2004-10-30 18:08 ` Thomas Zehetbauer
2004-11-01 9:51 ` Egbert Eich [this message]
2004-11-01 10:16 ` Dave Airlie
2004-11-01 13:48 ` Egbert Eich
[not found] <1099052450.11282.72.camel@hostmaster.org.suse.lists.linux.kernel.suse.lists.linux.kernel>
[not found] ` <1099061384.11918.4.camel@hostmaster.org.suse.lists.linux.kernel.suse.lists.linux.kernel>
[not found] ` <41829E39.1000909@us.ibm.com.suse.lists.linux.kernel.suse.lists.linux.kernel>
[not found] ` <1099097616.11918.26.camel@hostmaster.org.suse.lists.linux.kernel.suse.lists.linux.kernel>
[not found] ` <p734qkd0y0n.fsf@verdi.suse.de.suse.lists.linux.kernel>
[not found] ` <21d7e99704103004155d2826fb@mail.gmail.com.suse.lists.linux.kernel>
[not found] ` <21d7e997041030041748b60ce7@mail.gmail.com.suse.lists.linux.kernel>
2004-10-30 13:57 ` Andi Kleen
2004-10-29 12:20 Thomas Zehetbauer
2004-10-29 14:49 ` Thomas Zehetbauer
2004-10-29 19:47 ` Ian Romanick
2004-10-30 0:53 ` Thomas Zehetbauer
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=16774.1839.343824.305232@suse.de \
--to=eich@suse.de \
--cc=ak@suse.de \
--cc=idr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomasz@hostmaster.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox