> term, since I've in the past fixed bugs in serial.c that don't get fixed
> in other drivers that have borrowed huge amounts of code from serial.c
> --- in many cases, I have no idea they've borrowed code, so I couldn't
> notify them even if I had the time to track all of the places that have
> borrowed from serial.c
A simple make modules for them would have told you the problem ones.
> The other solution (for now) is to use the generic_serial.c by
> R.E.Wolff@BitWizard.nl, but I don't personally like that approach since
> it introduces yet another abstraction layer, when in fact most of this
> functionality should be going into the tty layer.
Does it belong in the tty layer when it appears relevant purely to physical
port hardware ? (Just curious)
Also btw, post 2.4 can we have a rule that anyone who submits a new different
Z8530 chipset driver gets told to write a generic one. Especially since we
even now have different includes with different names for the same register.
It puts the lance drivers in the shade 8)
Alan
-
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/
This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:13 EST