02:25.31 | *** join/#openjtag _AchiestDragon (n=dave@whipy.demon.co.uk) |
06:21.42 | *** join/#openjtag vmaster_ (i=vmaster@p549B57BE.dip.t-dialin.net) |
10:56.50 | *** join/#openjtag bullet (n=bullet@114-71.1-85.cust.bluewin.ch) |
12:03.25 | *** join/#openjtag key2 (n=key2@gob75-2-81-56-64-17.fbx.proxad.net) |
12:03.27 | key2 | hi |
12:03.47 | key2 | is there any way to know with linux what adress is a PCI card using? |
12:04.31 | xl0 | key2: lspci? |
12:41.01 | *** join/#openjtag prpplague (n=billybob@216.110.117.16) |
13:09.56 | key2 | xl0: where does it say the adress in lspci |
13:10.37 | vmaster_ | key2: lspci -v |
13:10.56 | vmaster | or -vv if you want it really verbose |
13:16.17 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
13:18.07 | key2 | thx |
13:22.41 | key2 | vmaster: what is the Memmory and IO port? |
13:23.08 | key2 | If I wanna spy the transaction with a PCI analyzer, I should look at the mem or the IO |
13:25.27 | key2 | <PROTECTED> |
13:25.27 | key2 | <PROTECTED> |
13:27.01 | vmaster | probably both? |
13:34.28 | key2 | vmaster: I have a winmodem and I wanna write the drivers for linux |
13:34.43 | key2 | vmaster: Would it be easyer with a debugger or with a pci analyzer |
13:34.46 | key2 | ? |
13:38.15 | vmaster | mhh, the address reported by lspci isn't necessarily the same for windows, i guess |
13:38.46 | vmaster | pci may map the device where it wants |
13:38.51 | key2 | well I could see the adress with windows |
13:38.59 | key2 | but once I got it |
13:39.17 | vmaster | a pci analyzer might be better |
13:39.19 | key2 | can I with a dbg put a bp on the adress to see what's going on ? |
13:39.21 | vmaster | the access happen in kernel mode |
13:40.13 | vmaster | SoftIce allows you to break on I/O accesses and memory accesses |
13:42.10 | key2 | vmaster: yeah but if I do it software, then the IRQ are gonna be fucked up |
13:43.06 | vmaster | that's why i think that a pci analyzer might be better |
13:43.47 | key2 | I have a dragon board from fpga4fun |
13:43.57 | key2 | might be able to use it for that |
13:44.04 | key2 | with their PCI ANALYSER |
14:03.44 | key2 | vmaster: so with softice I could put a bp? |
14:04.09 | key2 | on the PCI adress memory |
14:06.35 | *** part/#openjtag dwery (n=dwery@nslu2-linux/dwery) |
14:14.13 | key2 | vmaster: numega driver studio would do it I guess |
14:17.59 | vmaster | i've used softice to break on ioport accesses, so i guess you could use it to break on memory accesses, too |
14:18.07 | vmaster | i just don't know what sideeffects that causes |
14:38.43 | *** join/#openjtag dwery (n=dwery@nslu2-linux/dwery) |
16:32.34 | *** join/#openjtag ByronT (i=byron-po@nslu2-linux/ByronT) |
21:42.50 | *** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox) |
23:14.50 | *** join/#openjtag prpplague (n=dave@69.73.206.157) |
23:15.13 | AchiestDragon | hi |
23:32.04 | *** join/#openjtag ka6sox-office (n=tking@netblock-66-159-209-16.dslextreme.com) |