Home > other >  Windows driver development, peripherals isa peripherals physical address memory mapping, read and wr
Windows driver development, peripherals isa peripherals physical address memory mapping, read and wr

Time:09-17

The great spirit is good, the hard development window drive for two weeks, there are a few problems think impassability,

1, equipment on the PC, if there is no correct drive, in the device manager can see that the device has a yellow warning icon?
Because of a peripheral configuration register? If there is no configuration registers, peripherals in the device manager is out of the show?

2, if there is no configuration registers a isa devices, but know the actual physical address, don't know vendorid and produce id, after using MmMapIoSpace get virtual address, isa peripherals is not successful, speaking, reading and writing, so my physical address mapping is referring to when you get there?

Also, the device driver code under Linux, have already seen, only is simple and crude of mapping the physical addresses to virtual addresses, direct use, is normally,
The following code:
Xd2000 request_mem_region (0, 0 x500000, "dual_ports_ram");
Xd2000 g_device_address=ioremap_nocache (0, 0 x500000);



I stupid, look for a few days data, test for a few days drive, this a few problems did not understand,
Please the great god, please give me a direction, frustration is a bit strong these days, don't know how to go

CodePudding user response:



No one spoke to me, under the answer yourself
Because the two pieces of board, a board addresses d2000 is open to the pci bus,
D2000 physical address should be another bat on-chip peripherals to take up, so I test is to be able to read the data, but can't communication, and the first bat



  • Related