[lkml]   [2007]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
    2007/5/5, Alan Cox <>:
    > On Sat, 5 May 2007 20:07:15 +0200
    > Oliver Neukum <> wrote:
    > > should I understand this so that, if tty_buffer_request_room() returns
    > > less than requested, the rest of the data should be dropped on the
    > > floor?
    > If it returns NULL then either there is > 64K buffered (we can adjust
    > that if anyone shows need - its just for sanity) or the system is out of
    > RAM.

    For my use case would be more sensible to accept the new data and
    discard the older one in the tty buffer: the tty buffer would be a
    moving window of the most recent incoming data. This because if
    someone does not read the incoming data maybe he's not interested in
    it. When he finally reads the data (assuming there was buffer
    underrun) he's likely interested to the more recent chunk of incoming
    data and not to an "head" of the data firstly received. Since I
    acquire measurement data from serial this make perfect sense for me.
    But does this make sense in general too?

    However, whatever policy the buffer uses, the fundamental point it's that
    when I flush the input buffer I should be sure that each byte read
    after the flush is *new* (current) data and not old one. This because
    when the input stream can be stopped I can check that there are 0 byte
    in the buffer, but when the stream can't be stopped I must use a
    flush-and-sleep (multiple times) heuristic before I can read a single
    *reliable* byte.

    > Alan


    ~ Antonio
    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: 2007-05-06 09:33    [W:0.028 / U:13.308 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site