public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: DRI Devel <dri-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Dri-devel] [2.6 patch] disallow DRM on 386
Date: Wed, 21 Jan 2004 01:28:27 +0100	[thread overview]
Message-ID: <20040121002827.GG6441@fs.tum.de> (raw)
In-Reply-To: <1074643498.25861.14.camel@dhcp23.swansea.linux.org.uk>

On Wed, Jan 21, 2004 at 12:04:59AM +0000, Alan Cox wrote:
> On Maw, 2004-01-20 at 21:24, Adrian Bunk wrote:
> > I got the following compile error in 2.6.1-mm5 with X86_CMPXCHG=n.
> > This problem is not specific to -mm, and it always occurs when you 
> > include support for the 386 cpu (oposed to the 486 or later cpus) since 
> > in this case X86_CMPXCHG=n and therefoore cmpxchg isn't defined in 
> > include/asm-i386/system.h .
> > 
> > The patch below disallows DRM if X86_CMPXCHG=n.
> 
> Ugly.
> 
> Fix system.h to always define cmpxchg.h and check its presence at
> runtime when the DRM module loads, then you can build 386 kernels that
> support DRI on higher machines.
> 
> The problem isnt that cmpxchg definitely doesn't exist, so system.h is
> wrong IMHO

???

AFAIR cmpxchg wasn't present in cpus earlier than the 486.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-01-21  0:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 21:24 [2.6 patch] disallow DRM on 386 Adrian Bunk
2004-01-20 22:44 ` Diego Calleja
2004-01-20 23:03   ` Adrian Bunk
2004-01-20 23:31     ` Andrew Morton
2004-01-21  0:37       ` Adrian Bunk
2004-01-21  0:04 ` [Dri-devel] " Alan Cox
2004-01-21  0:28   ` Adrian Bunk [this message]
2004-01-21 17:56     ` Alan Cox

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=20040121002827.GG6441@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dri-devel@lists.sourceforge.net \
    --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