[lkml]   [2003]   [May]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Use MTRRs by default for vesafb on x86-64
    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
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:35    [W:0.019 / U:14.248 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site