> 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?
It works just fine. Just you can't enable MTRRs for framebuffer memory.
Losing a bit of performance for what is (by todays standards) a crap
performing card anyways, is no big deal.
Dave
-
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/