Dave Jones wrote:
> > If that's the problem, a test which writes a data pattern to a
> > significant chunk of video RAM in sequence, as fast as possible, and
> > then reads it would be practically guaranteed to spot this and
> > indicate that MTRRs aren't suitable for this card in this mode.
>
> Or you could just add the PCI ID to the quirks list..
My point being that vesafb is used for maximum compatibility, when you
have no other way to drive an unknown framebuffer. It's the emergency
backup driver. Shouldn't it be robust when faced with an unknown
framebuffer type, new or old?
Granted if there are only two cards with this problem and we are
confident that no other cards have the problem, a PCI ID would do it.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri May 23 2003 - 22:00:32 EST