In case it wasn't clear: when there's a known-to-crash device driver (e.g., DEC PDQ w/ varrious bus attachments), and no-one to support it,, then IMHO removing it from -current is the right thing to do.
However, now that there's an (obviously required) one-line fix, and someone actively using it, willing to maintain, (even improve!) handling of Etnernet-like multicast addresses, and even willing to ship a pair of thin-client systems with DEFPA interfaces to someone if the volunteer isn't suitable.... then also IMHO restoring the code (and required FDDI machinery), then restoring said driver in -current also seems, IMHO, the right thing to do. (See earlier in thread for why faster-than-10Mbit Ethernet cannot replace FDDI on a number of buses and arches, where Ethernet faster than 10Mbit were either never implemented, or no longer available, or not affordable.)
