[parisc-linux] depi?
Philipp Rumpf
Philipp.H.Rumpf@mathe.stud.uni-erlangen.de
Thu, 18 Nov 1999 00:25:54 +0100
> The problem is that no matter how obvious it is to us software folks that it
> would be braindead, illogical, or nearly impossible for the hardware to
> behave in strange ways, the hardware folks are incredibly devious at making
> the hardware more effective, within the constraints of the architecture
> (and, on occasion, outside the constraints). This results in behaviour that
> may seem unreasonable to a software person.
If the hardware gives us cache problems, it is not in compliance with the
architecture specification (OR my proof is wrong, but you "didn't bother to
read it").
If it doesn't, we're just fine. (OR ...).
> ***** I attempt to code within the ARCHITECTURE, not to implement what
> specific hardware implementations let me get away with. That way I don't
> get burnt by the creative hardware engineers, who might be pushing the
> envelope. *****
Shrug. Both versions are in compliance with the architecture. (OR ...)
Note especially that on PA2.0 in wide mode, there is an explicit exception as
well, so mapping the memory at 0x0000 0000 0000 0000, 0x4000 0000 0000 0000,
0x8000 0000 0000 0000 or 0xc000 0000 0000 0000 is all okay.
Philipp Rumpf