On Sat, 2007-05-05 at 10:43 -0600, Paul Fulghum wrote: > There is not an input flush method for the tty driver > and individual drivers don't process that ioctl. > The tty drivers I've seen immediately pass receive data to the > tty buffering and I'm not sure why a driver would > behave otherwise. cdc-acm does its own buffering. In your case, the line discipline throttled the tty device because the ldisc buffer was full. If the line discipline throttles the driver input, the cdc-acm driver stops giving data to the tty buffering and instead stores them internally. In the serial driver this usually just results in dropping RTS to signal the remote end to stop sending. The serial driver always immediately gives receive data to the tty buffering without regard to the throttled state. I would argue that cdc-acm should do the same as the serial driver. -- Paul - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Oliver Neukum <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Alan Cox <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Paul Fulghum <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- References:
- [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: "Antonino Ingargiola" <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Paul Fulghum <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: "Antonino Ingargiola" <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Paul Fulghum <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: "Antonino Ingargiola" <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: "Antonino Ingargiola" <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Paul Fulghum <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: "Antonino Ingargiola" <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Paul Fulghum <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Paul Fulghum <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: "Antonino Ingargiola" <[email protected]>
- Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- From: Paul Fulghum <[email protected]>
- [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- Prev by Date: Re: [PATCH] UBI: dereference after kfree in create_vtbl
- Next by Date: [PATCH 4/4] reiserfs: remove inode constructor
- Previous by thread: Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- Next by thread: Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug]
- Index(es):