public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zehetbauer <thomasz@hostmaster.org>
To: Ian Romanick <idr@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	"DRI developer's list" <dri-devel@lists.sourceforge.net>
Subject: Re: status of DRM_MGA on x86_64
Date: Sat, 30 Oct 2004 02:53:36 +0200	[thread overview]
Message-ID: <1099097616.11918.26.camel@hostmaster.org> (raw)
In-Reply-To: <41829E39.1000909@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

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.

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?

Tom

-- 
  T h o m a s   Z e h e t b a u e r   ( TZ251 )
  PGP encrypted mail preferred - KeyID 96FFCB89
      finger thomasz@hostmaster.org for key

Chemists don't die, they just stop to react.




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

  reply	other threads:[~2004-10-30  1:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 12:20 status of DRM_MGA on x86_64 Thomas Zehetbauer
2004-10-29 14:49 ` Thomas Zehetbauer
2004-10-29 19:47   ` Ian Romanick
2004-10-30  0:53     ` Thomas Zehetbauer [this message]
     [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       ` 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
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

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=1099097616.11918.26.camel@hostmaster.org \
    --to=thomasz@hostmaster.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=idr@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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