I386 BIOS and cpu fixes / cleanups
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest10 patches 44 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/10 | Cr4 is valid on some 486sarch/ include/ | +14 | 153 replies | |
| 2/10 | Pnp segments in segment hdrivers/ include/ | +14 | 0 replies | |
| 3/10 | Always relax segmentsarch/ | +17 | 0 replies | |
| 4/10 | Apm seg in gdtarch/ arch/ | +5 | 0 replies | |
| 5/10 | Deprecate obsolete ldt accessorsinclude/ | +0 | 0 replies | |
| 6/10 | Pnp byte granularityarch/ drivers/ include/ | +11 | 0 replies | |
| 7/10 | Fixed pnp bios limitsarch/ drivers/ | +12 | 0 replies | |
| 8/10 | Stop deleting ntarch/ | +0 | 0 replies | |
| 9/10 | Apm is on cpu zero onlyarch/ | +12 | 0 replies | |
| 10/10 | Deprecate useless bugarch/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/10] I386 BIOS and cpu fixes / cleanups
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 <[email protected]>