On Jan 9, 2008 11:12 AM, Cédric Rousseau <[EMAIL PROTECTED]> wrote: > The difference is that I've created a PCIController class (that is the > equivalent of your PCI class) that maintain an array of PCIDevice > instances. This controller is a stub class that is initialized at boot time. > PCIDevice is implementation independant and make call to PCIController > methods. I've been trying to do that, but had problems with not complete objects support - good to know that it's possible.
> Now, we have to implement a VendorID/DeviceID lookup table (such a list can > be found in the net), and to create specialized implementations of PCIDevice > using the PCIDevice.Class property. http://pciids.sourceforge.net/pci.ids is distributed under GPL >= 2 and BSD, so it should be ok to just transform it into an array, or gzip into some new section of kernel. > I've already created an enumeration for class types and the 'pci' command > could be more descriptive if Enum.ToString() member exist. Should we go for a device tree based on class codes? ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
