Re: ((struct pci_dev*)dev)->resource[...].start

2001-05-16 Thread Albert D. Cahalan
Jeff Garzik writes: > "Khachaturov, Vassilii" wrote: >> Can someone please confirm if my assumptions below are correct: >> 1) Unless someone specifically tampered with my driver's device >> since the OS bootup, the mapping of the PCI base address registers >> to virtual memory will remain the

Re: ((struct pci_dev*)dev)->resource[...].start

2001-05-16 Thread Jeff Garzik
Jonathan Lundell wrote: > > At 5:37 PM -0400 2001-05-16, Jeff Garzik wrote: > >This is not a safe assumption, because the OS may reprogram the PCI BARs > >at certain times. The rule is: ALWAYS read from dev->resource[] unless > >you are a bus driver (PCI bridges, for example, need to assign >

Re: ((struct pci_dev*)dev)->resource[...].start

2001-05-16 Thread Jonathan Lundell
At 5:37 PM -0400 2001-05-16, Jeff Garzik wrote: >This is not a safe assumption, because the OS may reprogram the PCI BARs >at certain times. The rule is: ALWAYS read from dev->resource[] unless >you are a bus driver (PCI bridges, for example, need to assign >resources). Would you please

RE: ((struct pci_dev*)dev)->resource[...].start

2001-05-16 Thread Khachaturov, Vassilii
Jeff, Many thanks for the clarifications. > From: Jeff Garzik > "Khachaturov, Vassilii" wrote: [snip] > > bootup, the mapping of the PCI base address registers to > virtual memory will > > remain the same (just as seen in /proc/pci, and as > reflected in )? If > > not, is there a way to freeze

Re: ((struct pci_dev*)dev)->resource[...].start

2001-05-16 Thread Jeff Garzik
"Khachaturov, Vassilii" wrote: > Can someone please confirm if my assumptions below are correct: > 1) Unless someone specifically tampered with my driver's device since the OS > bootup, the mapping of the PCI base address registers to virtual memory will > remain the same (just as seen in

Re: ((struct pci_dev*)dev)-resource[...].start

2001-05-16 Thread Jeff Garzik
Khachaturov, Vassilii wrote: Can someone please confirm if my assumptions below are correct: 1) Unless someone specifically tampered with my driver's device since the OS bootup, the mapping of the PCI base address registers to virtual memory will remain the same (just as seen in /proc/pci,

RE: ((struct pci_dev*)dev)-resource[...].start

2001-05-16 Thread Khachaturov, Vassilii
Jeff, Many thanks for the clarifications. From: Jeff Garzik Khachaturov, Vassilii wrote: [snip] bootup, the mapping of the PCI base address registers to virtual memory will remain the same (just as seen in /proc/pci, and as reflected in subj)? If not, is there a way to freeze it for

Re: ((struct pci_dev*)dev)-resource[...].start

2001-05-16 Thread Jonathan Lundell
At 5:37 PM -0400 2001-05-16, Jeff Garzik wrote: This is not a safe assumption, because the OS may reprogram the PCI BARs at certain times. The rule is: ALWAYS read from dev-resource[] unless you are a bus driver (PCI bridges, for example, need to assign resources). Would you please elaborate?

Re: ((struct pci_dev*)dev)-resource[...].start

2001-05-16 Thread Jeff Garzik
Jonathan Lundell wrote: At 5:37 PM -0400 2001-05-16, Jeff Garzik wrote: This is not a safe assumption, because the OS may reprogram the PCI BARs at certain times. The rule is: ALWAYS read from dev-resource[] unless you are a bus driver (PCI bridges, for example, need to assign

Re: ((struct pci_dev*)dev)-resource[...].start

2001-05-16 Thread Albert D. Cahalan
Jeff Garzik writes: Khachaturov, Vassilii wrote: Can someone please confirm if my assumptions below are correct: 1) Unless someone specifically tampered with my driver's device since the OS bootup, the mapping of the PCI base address registers to virtual memory will remain the same (just as