Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751121AbVKJAbI (ORCPT ); Wed, 9 Nov 2005 19:31:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751123AbVKJAbI (ORCPT ); Wed, 9 Nov 2005 19:31:08 -0500 Received: from mailout1.vmware.com ([65.113.40.130]:29448 "EHLO mailout1.vmware.com") by vger.kernel.org with ESMTP id S1751121AbVKJAbG (ORCPT ); Wed, 9 Nov 2005 19:31:06 -0500 Date: Wed, 9 Nov 2005 16:31:01 -0800 Message-Id: <200511100031.jAA0V1HP027702@zach-dev.vmware.com> Subject: [PATCH 0/10] I386 BIOS and cpu fixes / cleanups From: Zachary Amsden To: Andrew Morton , Linus Torvalds , Linux Kernel Mailing List , "H. Peter Anvin" , Zwane Mwaikambo , Pratap Subrahmanyam , Christopher Li , "Eric W. Biederman" , Ingo Molnar , Zachary Amsden X-OriginalArrivalTime: 10 Nov 2005 00:31:05.0653 (UTC) FILETIME=[09724E50:01C5E58E] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1015 Lines: 21 The harmless portion of my current i386 cleanups, including one very nice bugfix to protect the kernel from rampant trampling by the PnP BIOS. The problem was the PnP transfer segments were protected in page increments, not byte increments, so a broken BIOS could overstep the bounds the PnP code was trying to enforce. Turns out I had such a broken BIOS, and discovered a common PnP bug is to use word access (2 bytes) to get and set device IDs, which are supposed to be 1-byte. Rather than let the BIOS trample memory, I added a workaround to copy data to and from a temporary value, which allows the BIOS to smash the high byte safely. The rest of these are (hopefully) obviously correct, nice transforms or removal of dead code. Zachary Amsden - 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/