[lkml]   [2002]   [Nov]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Re: time() glitch on 2.4.18: solved
    On Tue, 2002-11-05 at 18:57, Richard B. Johnson wrote:
    > No! You will break many machines. You cannot use out_p() when
    > writing the latch it __must__ be out(). the "_p" puts a write
    > to another port between the two writes. That will screw up
    > the internal state-machine of most PITs including AMD-SC520.

    The delay is required for the PIT. Your AMD-SC520 is simply a bit wacko.
    The right way to fix this is actually to switch inb_p to use udelay(8)
    and to load a conservative bogomip number at boot time (we inb_p before
    we compute udelay values in a few spots)

    BTW if your SC520 is broken that way I just broke 2.5.4x support for it
    fixing some more standards compliant platforms 8)

    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:30    [W:0.031 / U:25.116 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site