Hi Peter
> If you want to play with one of the system SMBus devices, you need to be in the
BIOS.
Really. How do you realize it? Did you read my post? I explain 2 ways without BIOS.
> So, my suggestion is: Connect it via SPI or I2C if you want to write a driver
for it in Windows
I have another a suggestion. Why don’t make a filter driver for hard disk and redirect I/O to SPI bus to send data to I2C via SMBus. It is faster. Great idea.
Hi Tim,
> Neither is recommended for SMBus access.? The SMBus resources are yypically assigned to and owned by an SMBus Controller driver.? You can’t just steal resources that belong to another driver.
If you install any windows system with correct drivers you will realize there’s no SMBus driver and resource is free. Why is not detected in device manager. No idea. So I don’t steal any resource. It’s there and there’s no for it. 100%.
> Board management is handled by board vendors, who write the SMBus Controller drivers and know how to arbitrate between competing users
Absolute correct. Can you explain me how they succeeded to communicate with SMBus controller from user mode driver and how they can detected it? Practicaly they should have a way to enumerate all PCI devices and get SMBus memory. Because so far I didn’t find any clear explanation in UMDF V2 documentation.