Board.KolibriOS.org

Hi,

I'm trying to work with some PCI device that needs a piece of address space where it can map it's own memory to, so I can access it.
But how do I do such a thing in KolibriOS ? I have used 'map_io_mem' before, when the device tells you the address, but now the device is asking me for the virtual address..

Any help appreciated.

http://wiki.kolibrios.org/wiki/SysFn62/ ... 0.BA.D0.B0

to let users access MMIO, the kernel shoul be compiled with mmio_pci_addr = b:d.f
(http://websvn.kolibrios.org/filedetails ... Fpci32.inc)
or you need to map MMIO in your driver?

art_zh wrote:http://wiki.kolibrios.org/wiki/SysFn62/ ... 0.BA.D0.B0

to let users access MMIO, the kernel shoul be compiled with mmio_pci_addr = b:d.f
(http://websvn.kolibrios.org/filedetails ... Fpci32.inc)
or you need to map MMIO in your driver?

All I need is one virtual physical address (range) that is available for 4096 bytes (If I understand it correctly).

KernelAlloc ?

Asper wrote:KernelAlloc ?

I dont need memory from RAM.

I just need to find a physical address that is still free.
For example, 0x7f000000 worked on my test machine. But there is no guarantee that it will work on others...

hidnplayr
You just need to wait for the forum to come Serge - he will most likely answer your question about the memory manager.

hidnplayr
the only way to detect the MMIO physical range is to read the device's base address registers (BARs) located in its configspace.
use bus/pci/pci32.inc functions (also available in userspace via fn62)

art_zh wrote:hidnplayr
the only way to detect the MMIO physical range is to read the device's base address registers (BARs) located in its configspace.
use bus/pci/pci32.inc functions (also available in userspace via fn62)

For regular PCI devices this has been filled in by the BIOS yes, but not for PCI-pc card bridges.

Then your driver needs to do the work BIOS does.
I tryed this for PCIe hotplug, but stepped back - it takes tons of clever tricks with MRRs, northbridge apertures and IRQ allocations.
Plug-and-restart is much simpler.