public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: KERNEL BUG: console not working in linux
Date: Mon, 27 Nov 2000 11:59:52 -0800	[thread overview]
Message-ID: <3A22BD38.B5E0B3A7@transmeta.com> (raw)
In-Reply-To: <200011271952.eARJqqw514056@saturn.cs.uml.edu>

"Albert D. Cahalan" wrote:
> >
> > Yes, it can.  Unfortunately, some "legacy-free" PCs apparently
> > are starting to take the tack that the KBC is legacy.  Therefore,
> > the use of port 92h is mandatory on those systems.
> 
> Not just embedded systems?
> 

Nope.  I was rather surprised to find this out, but I got a bug report
about a recent IBM Aptiva not working with SYSLINUX because it lacked
KBC.  It really could use the adaptive-A20 patch; Linus hasn't taken it
yet, though. 

> > Port 92h dates back to at the very least the IBM PS/2.
> >
> > Either way, the video card of the original poster is broken in more
> > ways than that.  Ports 0x00-0xFF are reserved for the motherboard
> > chipset and have been since the original IBM PC.
> 
> His video card is the motherboard. He has built-in video.
> So the port is being used by his motherboard chipset.

I see.  Still an incredibly bad choice.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-27 20:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-26 21:28 KERNEL BUG: console not working in linux Gianluca Anzolin
2000-11-26 23:53 ` Jorge Nerin
2000-11-27 14:05 ` Gianluca Anzolin
2000-11-27 14:50   ` Alan Cox
2000-11-27 18:49     ` Albert D. Cahalan
2000-11-27 19:08       ` H. Peter Anvin
2000-11-27 19:27         ` Petr Vandrovec
2000-11-28  1:36           ` Andries Brouwer
2000-11-28  1:40             ` H. Peter Anvin
2000-11-28  3:14               ` Andries Brouwer
2000-11-28  3:23                 ` H. Peter Anvin
2000-11-27 19:52         ` Albert D. Cahalan
2000-11-27 19:59           ` H. Peter Anvin [this message]
2000-11-28  0:16         ` Gianluca Anzolin
     [not found]           ` <3A22EF3D.B97A0965@transmeta.com>
2000-11-28  9:33             ` Gianluca Anzolin
2000-11-28 18:14               ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2000-11-28  4:09 Dunlap, Randy

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=3A22BD38.B5E0B3A7@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=acahalan@cs.uml.edu \
    --cc=hpa@zytor.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