Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 14 Mar 2002 16:58:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 14 Mar 2002 16:58:32 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:11527 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 14 Mar 2002 16:58:22 -0500 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: IO delay, port 0x80, and BIOS POST codes Date: 14 Mar 2002 13:57:40 -0800 Organization: Transmeta Corporation, Santa Clara CA Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2002 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Followup to: By author: Linus Torvalds In newsgroup: linux.dev.kernel > > Port ED is fine for a BIOS, which (by definition) knows what the > motherboard devices are, and thus knows that ED cannot be used by > anything. > > But it _is_ an unused port, and that's exactly the kind of thing that > might be used sometime in the future. Remember the port 22/23 brouhaha > with Cyrix using it for their stuff, and later Intel getting into the fray > too? > > So the fact that ED works doesn't mean that _stays_ working. > It is, in fact, broken on several systems -- I tried ED in SYSLINUX for a while, and it broke things for people. -hpa -- at work, 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 More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/