Hi folks, JMK and I were talking last night about upci and libpci. I need to do PCI Config access from bfload, to fix a bug where some old BIOSes dont set up the 5i20 board's PCI Command register (in Config space) correctly. bfload currently uses upci to access the boards; upci provides access to the boards' memory and io regions (BARs), but not to the Config space. I looked at libpci; it provides Config space access but not BAR access.
JMK and I tentatively agreed that i would augment upci to provide the Config access we need. In parallel with that conversation I emailed Martin Mares (who maintains libpci), to get his thoughts. He said he'd welcome patches to add BAR access to libpci. I looked at libpci and it looks pretty straightforward to port upci's BAR access code to libpci. This would be preferable to me, because the final code would be useful to more people than just us. It has the drawback (to us) of another outside dependency. We'd probably have to distribute our own copy of libpci with emc2 until the new version gets picked up by the distros we want support... Or just not support mesa-hostmot2 on platforms with older versions of libpci. Thoughts or comments? -- Sebastian Kuzminsky "The brain is [a machine]. The fact that it's made out of meat is a red herring." -- David Adler <http://www.spectrum.ieee.org/print/6268> ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
