Skip to contentSkip to conversation

what serial driver restructure is planned?

DISCUSSION Alan Cox 1 participant 1 message Feb 16, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Alan Cox

author
#1 lore raw
Quoted 5 lines

The flip buffer and output tmp_buf logic is not particularly friendly to packetized serial data streams, which are normal with most synchronous serial communications or IP over asynchronous link setups -- especially when the serial interface chip understands PPP frames.

There I disagree with dumber devices

Quoted 6 lines

The current TTY formalism is not particularly
friendly to dial-on-demand synchronous WAN
communications. It is not impossible that
a /dev/ttyraw device, which could easily shift
between asynchronous and synchronous modes,
might be a better approach.

I think thats misunderstanding how to use the existing interfaces. If you have an ioctl to switch the mode of your device, you can exist dually as a network interface (DMA into skbuff, fire at network stack through generic PPP or the cisco hdlc layer) and as a tty interface in async mode.

The byte by byte PPP code we currently have exists primarily for the normal dumb or minimally intelligent devices. If your device is smaller you can simply give it a dual personality. The Z85230 driver I wrote did this although the generic 8530 async code never got ported into the final device and released in that form.