**** BEGIN LOGGING AT Mon May 08 09:59:57 2006 May 08 11:52:01 hi May 08 11:52:22 is there any way to know with linux what adress is a PCI card using? May 08 11:53:05 key2: lspci? May 08 12:58:31 xl0: where does it say the adress in lspci May 08 12:59:11 key2: lspci -v May 08 12:59:30 or -vv if you want it really verbose May 08 13:06:41 thx May 08 13:11:15 vmaster: what is the Memmory and IO port? May 08 13:11:43 If I wanna spy the transaction with a PCI analyzer, I should look at the mem or the IO May 08 13:14:02 Region 0: Memory at e2800000 (32-bit, non-prefetchable) [size=64K] May 08 13:14:02 Region 1: I/O ports at 1000 [size=8] May 08 13:15:35 probably both? May 08 13:23:02 vmaster: I have a winmodem and I wanna write the drivers for linux May 08 13:23:17 vmaster: Would it be easyer with a debugger or with a pci analyzer May 08 13:23:20 ? May 08 13:26:49 mhh, the address reported by lspci isn't necessarily the same for windows, i guess May 08 13:27:21 pci may map the device where it wants May 08 13:27:25 well I could see the adress with windows May 08 13:27:33 but once I got it May 08 13:27:51 a pci analyzer might be better May 08 13:27:53 can I with a dbg put a bp on the adress to see what's going on ? May 08 13:27:55 the access happen in kernel mode May 08 13:28:47 SoftIce allows you to break on I/O accesses and memory accesses May 08 13:30:44 vmaster: yeah but if I do it software, then the IRQ are gonna be fucked up May 08 13:31:40 that's why i think that a pci analyzer might be better May 08 13:32:21 I have a dragon board from fpga4fun May 08 13:32:32 might be able to use it for that May 08 13:32:39 with their PCI ANALYSER May 08 13:52:18 vmaster: so with softice I could put a bp? May 08 13:52:44 on the PCI adress memory May 08 14:02:47 vmaster: numega driver studio would do it I guess May 08 14:06:33 i've used softice to break on ioport accesses, so i guess you could use it to break on memory accesses, too May 08 14:06:41 i just don't know what sideeffects that causes May 08 23:03:44 hi May 09 09:41:19 hello **** ENDING LOGGING AT Tue May 09 09:59:56 2006