On Thursday 28 June 2007, Andrew Morton wrote:
> > +#undef DISABLE_TEST_MODE
>
> enabling DISABLE_TEST_MODE seens to enable test mode. Confused.
Blame it on Intel. ISTR that early pxa2[156]x silicon had
something called "test mode". And a boatload of errata, with
a common thread in workarounds: using the "test mode" helped
many things work better, although it was neither necessary nor
sufficient. If one were to #define DISABLE_TEST_MODE, software
could experiment with other workarounds ... and maybe be able
to get the documented "double buffering" feature to work.
Later silicon stopped documenting "test mode" as such, effectively
making certain workarounds become the standard way to use the chip.
Which doesn't explain why pxa270 code has pxa2[156]x devel hooks,
but explains why pxa2[156]x code wants the hardware "test mode"
to be enabled ... except during developer experiments.
- Dave
-
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]
