> Date: Sun, 21 Aug 2005 00:33:48 +0100 (BST) > From: Mark Underwood <[EMAIL PROTECTED]> > > ... > Interestingly (we for me at least ;-) I have been > working on an SPI subsystem that was/is a copy of the > I2C subsystem with changes as SPI doesn't have a > protocol like I2C. ... > > To me, what I have, like I2C, doesn't tie in very well > with the new driver model (although I'm not overly > familiar with it, I think I finally understand > platform devices :-).
Yes, it takes maybe a little while to sort out what the driver model does for you, especially if you're coming from whatever strange dimension the I2C model did. :) > I wonder how much work the new kernel subsystems can > do for us to cut down the size of i2c-core (and thus > also spi-core). > I guess there is no escaping the fact that I'm going > to gave to do some more homework and study the code. > Any thoughts or insights would be very welcome. Well, I've just posted a sketch of how to use the driver model in a more traditional way for SPI. That same approach could be taken with I2C if/when anyone gets motivated to make it happen ... except that, unlike SPI, I2C can actually use hardware probing in common usage. (It could kick in right after the pre-declared devices Get initialized.) - Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
