4 ms·
Anyone explain what "splitting a driver" in kernel parlance and code sharing is? Modularization is just breaking large pieces of the program up into small piece
by jtchang 13y ago
Anyone explain what "splitting a driver" in kernel parlance and code sharing is? Modularization is just breaking large pieces of the program up into small pieces right? Is code sharing just the same thing or are they talking about something different?
- deleted 13y ago[deleted]
- lukecampbell 13y agoI believe in this case that the driver existed as one piece or module and each hardware version was handled as a different case in branch logic in an attempt to keep the code consolidated and modular (code sharing). As the hardware matured and new versions came to be it gets harder to reuse existing code and that's the context of this thread. Linus wants to split the driver and create a new module to house that handles only that specific flavor of hardware instead of adding new edge-cases to the existing code. At least, that's how I read it. I wasn't working on the Kernel back in 2000 so I can't say.
- drivers99 13y agoCheck the links in this comment: https://news.ycombinator.com/item?id=7220508 https://news.ycombinator.com/item?id=7220508 Specifically: https://lkml.org/lkml/2000/8/22/52 https://lkml.org/lkml/2000/8/22/52