![]() | |||||||||||||
Messages in this thread |
On Thu, 19 Dec 2002, Denis Vlasenko wrote: > On 19 December 2002 08:19, Andre Hedrick wrote: > > Promise knows this point. > > Thus they moved the setting to a push/pull in the vendor space in the > > dma_base+1 and dma_base+3 respectively. > > lspci -vvvxxx fails when the content is located in bar4 io space. > > Neither I nor original bug reporter (I think) did understand > a bit what you said. Can we plead for IDE -> English translation? > ;) > If lspci is of no help, what can we use instead? They move the setting which were readable in the asic from PCI space in the 20246/47/62/65/67 into a sense mode of the asic sniffing the contents of the taskfile registers to internally do the same thing but hide it all. The new 20268/69/7* report all zeros in the PCI space. ioperm() But be prepared to roast your data. I do not have a good answer! Andre Hedrick LAD Storage Consulting Group - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:31 [W:0.544 / U:0.040 seconds] ©2003-2008 Jasper Spaans | |||||||||||||