bug in addressspace?
Hello! currently I'm working on my own CardBus card and I test and debug it with your beautiful tools. I have seen that the Linux-system freezes if I plug in my card if I give the card these initial values for address spaces: BAR0 - 0x 9011 BAR1 - 0x 9019 BAR2 - 0x 9021 BAR3 - 0x 9029 BAR4 - 0x 9031 BAR5 - 0x 9001 I know these values are completely bullsh*t but i think a system shouldn't get unstable ore freeze because you plug in something thats not covered by the specs. I tested this with kernel 2.6.35.6. I don't know which other informations you need, so please give me a list or something like this. If you like I could show you some kind of LogicAnalyzer output of the situation (you can probably see there what data got transferred). dmesg and lspci is not possible because the complete PC freezes in that situation. Regards, Arne ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
dump_cis
Hello, at the moment I'm developing a CardBus-Card and I would like to use the dump_$something , especially the dump_cis tool to debug my Card, but it seems like the tools are not in the pccardctl-package included anymore. Is there another way to read out the CardBus-Registers? In case it is needed: I'm running kernel 2.6.32 and PCMCIAutils 0.17 Regards, Arne ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
