Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: IO delay, port 0x80, and BIOS POST codes | Date | 14 Mar 2002 13:11:56 -0800 |
| |
Followup to: <Pine.LNX.4.33.0203141234170.1286-100000@scsoftware.sc-software.com> By author: John Heil <kerndev@sc-software.com> In newsgroup: linux.dev.kernel > > No, the better/correct port is 0xED which removes the conflict. > > We've used 0xED w/o problem doing an embedded linux implementation > at kernel 2.4.1, where SMM issues were involved. (It was recommended > to me by an x-Phoenix BIOS developer, because of its safety as well as > conflict resolution, >
Sorry, causes breakage on quite a few machines. I used it briefly in SYSLINUX. Phoenix doesn't have that issue since they're part of the platform, so they can make it a requirement for their BIOS.
-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 <amsp@zytor.com> - 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/
| |