From: Adrian Bunk <bunk@fs.tum.de>
To: Diego Calleja <grundig@teleline.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] disallow DRM on 386
Date: Wed, 21 Jan 2004 00:03:14 +0100 [thread overview]
Message-ID: <20040120230313.GA6441@fs.tum.de> (raw)
In-Reply-To: <20040120234403.73be7b2a.grundig@teleline.es>
On Tue, Jan 20, 2004 at 11:44:03PM +0100, Diego Calleja wrote:
> El Tue, 20 Jan 2004 22:24:21 +0100 Adrian Bunk <bunk@fs.tum.de> escribió:
>
> > 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.
>
> I got a "cmpxchg not defined" error when compiling the drm stuff in -mm5.
> When I looked at the configuration, I saw that all the cpus types had been selected
> (I didn't even realize of your stuuf and menuconfig put the defaults). I removed
> all types of cpus except PIII and it compiled.
Yup, that's exactly the problem.
Selecting CPU_386 in -mm4 or -mm5 or selecting M386 in other kernels
triggers it.
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
next prev parent reply other threads:[~2004-01-20 23:03 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 [this message]
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
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=20040120230313.GA6441@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=grundig@teleline.es \
--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