Now finds PCI cards connected to second pci-pci bridge on my motherboard.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@446 a95241bf-73f2-0310-859d-f6bbb57e9c96
config_manager and busses works, and this is a large correction based on
my current working thoughts.
I also think we need to have a new interface between the bus modules and
the config_manager to allow them to work together. I have some ideas
on it and will start fleshing it out next week.
This update basically moves all PCI stuff back to the PCI module and
cleans up config_manager.c. We now print a small amount of info for
devices and more for bridges. My system only has a single bridge, but if
anyone has a more exotic system and tries this can they let me know
what sort of results they see?
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@444 a95241bf-73f2-0310-859d-f6bbb57e9c96
power management states for cards that support it.
ISTR that Be forced all devices to full power, so we do the same
for the moment.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@439 a95241bf-73f2-0310-859d-f6bbb57e9c96
don't do anything and Axel has started replacing them anyway.
At some point we need to remove the files, but I'll wait until
things have had a few days first.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@437 a95241bf-73f2-0310-859d-f6bbb57e9c96
- add finding the PCI IRQ Routing table
- add pci_get_capability and some simple uses to test it
Thanks to Michael N for his help on getting the region working as
I expected it to :)
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@435 a95241bf-73f2-0310-859d-f6bbb57e9c96
which allows better seperation and stops the module code trying to
load device drivers. This should speed up the boot a little and reduce
the debug messages that Marcus loves so much :)
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@430 a95241bf-73f2-0310-859d-f6bbb57e9c96
printfs, etc in here. But some bug fixes and better code.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@426 a95241bf-73f2-0310-859d-f6bbb57e9c96
for accessing the config space! So, become a good citizen and add locking
to ensure we only have one dabbler at a time in config space.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@424 a95241bf-73f2-0310-859d-f6bbb57e9c96
These will need to be reviewed as beos drivers expect them to be available
and using #define won't cover that.
The doxygen stuff doesn't all work though I can't figure out why :(
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@423 a95241bf-73f2-0310-859d-f6bbb57e9c96
A couple of changes in various interrupt and thread functions and structures.
These make it now possible to change the stack at any time without making the kernel crash. This is needed for calling VESA 3.0 VBE functions through the protected mode interface.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@422 a95241bf-73f2-0310-859d-f6bbb57e9c96
(I just stole it from StorageKit::BasicTest, the version of
which has been proven many times over ;-)
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@417 a95241bf-73f2-0310-859d-f6bbb57e9c96
+ Finally checked in my remaining BMimeType tests... :-)
NOTE -- The BMimeType::GetSupportingApps() test is
not yet finished. For some reason GetSupportingApps()
is returning a few strange signatures that don't appear
to be in the database. I'm still figuring out where they're
coming from.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@408 a95241bf-73f2-0310-859d-f6bbb57e9c96
This now reports better and starts configuring the busses we find.
There is still a long way to go but this another step on the way.
NB the information comes from 2 different methods and presently doesn't
agree This is known and will be fixed, so please don't start yelling
that it's broken! If people have strange debug information please
let me have a copy so I can try to debug further :)
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@403 a95241bf-73f2-0310-859d-f6bbb57e9c96
