This website requires JavaScript.
Explore
Help
Register
Sign in
Intravision
/
reactos
Watch
1
Star
0
Fork
You've already forked reactos
0
mirror of
https://github.com/reactos/reactos.git
synced
2025-07-23 13:03:47 +00:00
Code
Issues
Projects
Releases
Packages
Wiki
Activity
A free Windows-compatible Operating System - mirrored from GitHub
c
drivers
gpl
hacktoberfest
kernel
operating-system
os
osdev
reactos
win32
win32api
windows
x86
39484
commits
107
branches
277
tags
2.4
GiB
C
86.1%
C++
11.1%
Python
0.7%
Assembly
0.5%
CMake
0.5%
Other
0.9%
ae81274578
Find a file
HTTPS
Download ZIP
Download TAR.GZ
Download BUNDLE
Open with VS Code
Open with VSCodium
Open with Intellij IDEA
Cite this repository
BibTeX
Cancel
Stefan Ginsberg
ae81274578
- Fix a FreeLdr PCI detection bug introduced in revision 10742 5 years ago when PCI detection was added. FindPciBios was setting the HardwareMechanism entry in the PCI_REGISTRY_INFO structure (then called CM_PCI_BUS_DATA) to the wrong register returned from the PCI BIOS: CL instead of AL. CL is the number of the last PCI bus in the system (0 if you only have 1 bus, 1 if you have 2 buses). AL contains bit-fields for PCI characteristics, and HAL checks the 2 first bits to determine the type of the BUS. My VMWare test environment has 2 PCI buses, so the number happened to be correct. This doesn't work if there is only 1 PCI bus, such as in QEMU and Vbox, as we then get an invalid PCI type of 0. Fix this and re-enable the PCI detection in HAL to properly detect the PCI type instead of assuming type 1.
...
svn path=/trunk/; revision=43924
2009-11-02 21:13:45 +00:00
irc
Give Techbot the ability to check for and ghost existing bots, then rename itself
2008-08-10 13:06:58 +00:00
reactos
- Fix a FreeLdr PCI detection bug introduced in revision 10742 5 years ago when PCI detection was added. FindPciBios was setting the HardwareMechanism entry in the PCI_REGISTRY_INFO structure (then called CM_PCI_BUS_DATA) to the wrong register returned from the PCI BIOS: CL instead of AL. CL is the number of the last PCI bus in the system (0 if you only have 1 bus, 1 if you have 2 buses). AL contains bit-fields for PCI characteristics, and HAL checks the 2 first bits to determine the type of the BUS. My VMWare test environment has 2 PCI buses, so the number happened to be correct. This doesn't work if there is only 1 PCI bus, such as in QEMU and Vbox, as we then get an invalid PCI type of 0. Fix this and re-enable the PCI detection in HAL to properly detect the PCI type instead of assuming type 1.
2009-11-02 21:13:45 +00:00
rosapps
Remove duplicate libjpeg from rosapps, used one is in trunk
2009-10-15 15:19:58 +00:00
rostests
- add dsound winetest
2009-11-02 19:19:39 +00:00
wallpaper
Rename the wallpaper to conform with ISO 9660:1988 and make cdmake happy...
2009-02-03 13:26:30 +00:00