On Tue, 7 Nov 2006, Eric W. Biederman wrote:
| Huh? As I read the ipath code I am passing you the value that needs to go
| into ipath->int_config and thus into dd->ipath_kregs->kr_interrupt_config.
Yes.
| Sure it is coming as 2 32bit words instead of a one big 64 bit one, but
| that is simple to fix.
It would be cleaner, but not absolutely necessary.
| If your card doesn't pay attention to configuration space access cycles then
| there should be no reason to write the value there. If your card does pay
| attention to the configuration space access cycles it should be trivial to
| make this work.
The card does pay attention, and other programs such as lspci and the
like also look at the config space. They should definitely be kept
in sync, and config writes are fairly cheap, anyway.
| If you really need to write to both the config space registers and your
| magic shadow copy of the register I can certainly do the config space
| writes for you. I just figured it would be more efficient not to.
The HT layer should always do the config updates, since you are trying
to clean up that layer. Only the "extra" stuff (if any) should be done by
the callback.
Dave Olson
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
