David> As for making PCMCIA part of the standard kernel... it is
David> something that I've obviously thought about before. My
David> (possibly outdated, probably exaggerated) impression was that
David> based on the difficulty I've had in getting PCMCIA-friendly
David> changes into the kernel over the years, that Linus was, if not
David> hostile, at best never particularly interested in it. Also,
David> given the size and complexity of the PCMCIA package, it seems
David> more easily maintainable as a separate entity, even if it means
David> I have to deal with the kernel version skew issue from time to
David> time. I'm not sure it was/is the best way to go and may change
David> my mind in the future: I'm sure there's a cost to separate
David> distribution, in that regular kernel developers are less likely
David> to look at the code. But as I'm sure Linus would agree, having
David> final editorial control also has its advantages.
Well the result of this is that for other architectures such as the
m68k; some people (can't remember the names off hand, sorry) have
started to implement driver for PCMCIA devices (mainly NE2K Ethernet
and 16c550 serial) totally independant of the existing PCMCIA
subsystem. Some of these drivers have now been included into the
standard kernel.
I asume this is because these guys don't know about the current PCMCIA
code and where to get it. IMHO keeping PCMCIA out of the kernel is a
pain and I would prefer to see it go in together with the rest of the
strange bus architectures we support these days.
Jes
-
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/