Re: AWE32 RAM detection problem

Aaron Tiensivu (tiensivu@pilot.msu.edu)
Sun, 22 Nov 1998 14:37:16 -0500

> Thats interesting. My guess would be timing. Is this true both for SMP and
> uniprocessor builds and does sticking "delay++" before the line
>
> /* sample counter */
> awe_set_cmd(AWE_WC_Cmd);
> clock = (unsigned short)inw(port);
>
> (in awe_wait()) change the behaviour ?

Another guess is motherboard IO aliasing, although if it worked with
previous versions, I'm not sure why it would suddenly break. I had one
motherboard in particular that the AWE driver would find random amounts of
memory on the AWE32. Stick the same card in another system and it would find
the correct amount.

--
Which is worse, ignorance or apathy? Who knows? Who cares?
IBM: It may be slow, but at least it's expensive.
Linux: Get it up, keep it up. Viagra for PCs.
AOL doctor to new mother: You've got male!




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/