>> 1. The serial port will provide a flag field to indicate
>> its state, with the following states being defined:
>>
>> ....
> Most of this state (RX-TO-TX, RECEIVING, FULL-RX, etc.) should
> be implemented in the line discpline, since it's highly specific
> to the half-duplex transmission discpline.
If you think about it, you'll soon see that such isn't quite the case.
What I think you meant to say was that most of those states are highly
specific to the use of half duplex as opposed to full duplex, and I
have no problem agreeing with that.
However, the state as designed is basically generic to ANY half duplex
line discipline and, as a result, would be best implemented as a core
module for half duplex disciplines, with the individual disciplines
hooking into it.
> The name of the game is to minimize the amount of complexity
> that we need to introduce into each low-level tty driver.
True, and hence why I stated that the design was for generic half
duplex support, with the design aim being to be able to hang ANY half
duplex protocol off the design.
> What you've laid out is a pretty good design of what the
> half-duplex line discpline will need to do; it's where the work
> is done that's critical in terms of managing complexity.
Very true.
Best wishes from Riley.
PS: The kernel versions page is now back online at the URL below, and
includes separate sublists both for each kernel series, and for
each year of development.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* http://www.memalpha.cx/Linux/Kernel/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/