mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christer Weinigel <wingel@hog.ctrl-c.liu.se>
To: hpa@zytor.com
Cc: robert@schwebel.de, linux-kernel@vger.kernel.org,
	jason@mugwump.taiga.com, anders@alarsen.net, rkaiser@sysgo.de,
	tytso@mit.edu
Subject: Re: [PATCH][RFC] AMD Elan patch
Date: Wed,  2 Jan 2002 01:06:09 +0100 (CET)	[thread overview]
Message-ID: <20020102000609.6B6C136F9F@hog.ctrl-c.liu.se> (raw)
In-Reply-To: <3C322EEE.5040402@zytor.com> (hpa@zytor.com)
In-Reply-To: <Pine.LNX.4.33.0112311900380.3056-100000@callisto.local> <3C322EEE.5040402@zytor.com>


> H. Peter Anvin wrote:

> Do you have documentation which verifies that A20 is enabled by the time 
> the IN instruction returns?  

>From the manual for the SC410 (found on AMD's homepage):

    Alternate Gate A20 Control Register (Port 00EEh) A special 8-bit
    read/write control register provides a fast and reliable way to
    control the CPU A20 signal. A dummy read of this register returns
    a value of FFh and forces the CPU A20 to propagate to the core
    logic, while a dummy write to this register will cause the CPU A20
    signal to be forced Low as long as no other A20 gate control
    sources are forcing the CPU A20 signal to propagate.

I think it's safe to assume that it takes effect immediately.

> Furthermore, I would still like to argue that this does not belong into 
> "processor type and features", because all of these are *chipset* 
> issues; in fact, in this particular case you're more than anything 
> working around a BIOS bug (not having INT 15h AX=2401h do the right thing).

I agree that it might be better to have a chipset option similar to
CONFIG_VISWS:

bool 'SGI Visual Workstation support' CONFIG_VISWS
...
bool 'AMD Elan SC4x0 support' CONFIG_ELAN_SC4x0
if [ "$CONFIG_ELAN_SC4x0" != "n" ]; then
    bool '  Use "inb 0xee" to control A20' CONFIG_ELAN_SC4x0_A20
fi

> I'm also very uncomfortable with putting this where you do; I think it 
> should be put before a20_kbc instead.  If the BIOS is implemented 
> correctly, it should be used.

I disagree, the Elan SC410 is an embedded CPU, it's used in systems
that might not even have a BIOS (such as the Ericsson eBox that I've
been working with).  Since there has to be a config option for this
CPU (the clock frequency selection) and a SC410-enabled kernel won't
work properly on a normal PC anyway, why not modify the boot sequence
so that it _always_ works on this CPU.

  /Christer

-- 
"Just how much can I get away with and still go to heaven?"

  parent reply	other threads:[~2002-01-02  0:06 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-21 21:26 AMD SC410 boot problems with recent kernels Robert Schwebel
2001-12-21 22:09 ` H. Peter Anvin
2001-12-22 16:13   ` Robert Schwebel
2001-12-23  1:44     ` H. Peter Anvin
2001-12-23  9:45       ` Robert Schwebel
2001-12-23 10:19         ` H. Peter Anvin
2001-12-23 13:16         ` Christer Weinigel
2001-12-23 20:02           ` H. Peter Anvin
2001-12-30 22:02             ` Robert Schwebel
2001-12-30 23:15               ` H. Peter Anvin
2002-01-01 12:30 ` [PATCH][RFC] AMD Elan patch Robert Schwebel
2002-01-01 21:49   ` H. Peter Anvin
2002-01-01 23:27     ` Robert Schwebel
2002-01-01 23:38       ` H. Peter Anvin
2002-01-02  0:05         ` Dave Jones
2002-01-02  0:45           ` H. Peter Anvin
2002-01-02 13:49           ` Robert Schwebel
2002-01-02 14:03             ` Dave Jones
2002-01-02 16:10               ` Alan Cox
2002-01-02 22:40                 ` H. Peter Anvin
2002-01-02 23:10                   ` Alan Cox
2002-01-02 23:02                     ` H. Peter Anvin
2002-01-02 23:50                       ` Alan Cox
2002-01-03  9:04                       ` Robert Schwebel
2002-01-02 23:56                     ` Robert Kaiser
2002-01-03  0:10                       ` Alan Cox
2002-01-03  8:52                   ` Robert Schwebel
2002-01-02 16:06             ` Alan Cox
2002-01-02 16:56               ` Robert Schwebel
2002-01-02 17:26                 ` Robert Schwebel
2002-01-02 23:06                   ` Peter Wächtler
2002-01-02 23:21                     ` H. Peter Anvin
2002-01-02  1:07       ` [RFC] Embedded X86 systems Was: " Christer Weinigel
2002-01-02  8:45         ` Alan Cox
2002-01-02  9:05           ` Christer Weinigel
2002-01-02  9:18             ` Alan Cox
2002-01-05 12:23           ` Eric W. Biederman
2002-01-02  0:06   ` Christer Weinigel [this message]
2002-01-02  0:48     ` H. Peter Anvin
2002-01-02  1:10     ` Christer Weinigel
2002-01-02 13:58       ` Robert Schwebel
2002-01-02 20:47         ` Christer Weinigel
2002-01-02 13:55     ` Robert Schwebel
2002-01-02 15:54   ` Robert Schwebel
2002-01-11  9:38   ` [PATCH] " Robert Schwebel
2002-01-21  7:28     ` New version of " Robert Schwebel
2002-01-21 20:44       ` Marcelo Tosatti
2002-01-24  8:09       ` Robert Schwebel
2002-01-24  8:39         ` Robert Schwebel
2002-01-23 10:28     ` [PATCH] " Robert Schwebel
2002-01-23 21:30       ` Marcelo Tosatti
2002-01-22 14:47   ` [PATCH][RFC] " Robert Schwebel
2002-01-22 18:01     ` Dave Jones
2002-01-22 22:55   ` New version of AMD Elan patch available Robert Schwebel
2002-02-01 22:01     ` Robert Schwebel

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=20020102000609.6B6C136F9F@hog.ctrl-c.liu.se \
    --to=wingel@hog.ctrl-c.liu.se \
    --cc=anders@alarsen.net \
    --cc=hpa@zytor.com \
    --cc=jason@mugwump.taiga.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkaiser@sysgo.de \
    --cc=robert@schwebel.de \
    --cc=tytso@mit.edu \
    --cc=wingel@t1.ctrl-c.liu.se \
    /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

Powered by JetHome