[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <477AF679.1060900@zytor.com>
Date: Tue, 01 Jan 2008 18:27:05 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Christer Weinigel <christer@...nigel.se>
CC: Rene Herman <rene.herman@...access.nl>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
"David P. Reed" <dpreed@...d.com>,
Rene Herman <rene.herman@...il.com>,
Ingo Molnar <mingo@...e.hu>, Paul Rolland <rol@...917.net>,
Pavel Machek <pavel@....cz>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
rol@...be.net
Subject: Re: [PATCH] x86: provide a DMI based port 0x80 I/O delay override.
Christer Weinigel wrote:
>
> Both 0xed and 0xf0 are mapped to internal functions on the AMD Elan
> SC400 processor. It is an AMD 486 based system on a chip and since AMD
> just knew that it would never have a math coprocessor, they reused the
> 0xf0-0xf2 range for the PCMCIA controller. I guess the AMD Elan SC500
> will have similar problems.
>
> I seem to recall that back when I was working with the Elan SC400
> (sometime around 1998?) there were discussions about finding an
> alternate delay port because outb to 0x80 messed up the debug port. I
> think the Elan stopped those discussions because just about every port
> on the Elan was reused for some alternate purpose.
>
Yeah, the Elan is not supportable anyway without a CONFIG option (it's
broken in so many ways), so it doesn't really apply. It's a fuckwit design.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists