It's possible that a device on the bus is hanging when probed/dumped. In that case, it might not be possible to solve. How similar to i2c-voodoo3 is it? Can it be rolled into it? Phil On Wed, Oct 31, 2001 at 09:08:24AM -0500, Mark Studebaker wrote: > sure, we'll take it. > You should get i2cdump working first. > > If you are using i2c-algo-bit, you can use > modprobe i2c-algo-bit bit_test=1 debug=2 (IIRC - check the source) > to help debug things > > mds > > > > Alexander Wold wrote: > > > > Hello, > > > > I have recently created an i2c driver for the Savage4. It is based upon > > the i2c-voodoo3 driver. The main motivation was to get access to the > > bt868 connected to S3Savge4`s i2c bus. If this driver is of general > > interest, I will be happy to submit it to the project. The driver is > > complete, and working. There are some issues thow, i2cdump hangs the > > bus, and after starting X, writes to the i2c bus don`t work. When > > reloading/loading the module in X (or while x is running) it works fine. > > > > Regards, > > Alexander Wold -- Philip Edelbrock -- IS Manager -- Edge Design, Corvallis, OR phil at netroedge.com -- http://www.netroedge.com/~phil PGP F16: 01 D2 FD 01 B5 46 F4 F0 3A 8B 9D 7E 14 7F FB 7A
