> > Justin,
> > I guess is the second or third report of problems with the new aic7xxx :(
> This issue has already been resolved as a chipset issue requiring
> I/O mapped register access to work around. The "old" aic7xxx driver
> avoids these issues by issuing a register read after every register
> write. This stops up your PCI bus with wasted cycles even if you have
> a perfectly working chipset.
> So, how would you like me to resolve this. We can do the same thing
> as Adaptec's windows drivers and just always use the slower, less
> efficient I/O mapped method for accessing registers. This will "fix"
> the problems people have with broken VIA and Intel chipsets. I can
> make this a compile and run-time option, but should we default to
> I/O mapped or memory mapped?
> Don't you just love broken PC hardware?
Its all fine, then: I thought the problems were caused by some bug in the
Thanks for explaining me the issue clearly. :)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/