Hello, On Oct 28, 2008, at 4:41 PM, Jochen Kunz wrote:
On Tue, 28 Oct 2008 12:58:05 -0400 Michael <macallan%netbsd.org@localhost> wrote:What on earth are you talking about? You'd rather change /every single/ i2c driver than put a slightly different bus attachment into a select few?I talk about a small modification (addition) to the match-function ofevery i2c device driver. With your method you will have to reinvent thebus attachment wheel over and over again in several places for many ports and devices.
No, I can use the exact same thing over and over again, just need to pull a few lines out of ki2c and put then into a header.
With that addition to the i2c device match function you will get a universal, MI solution for the problem that will work for all ports and devices in a uniform way.
Same with mine.
Besides, you might want to look at Paul Goyette's work in dbcool. If your i2c devices can be probed for then there is no problem either.I remember the discussion on tech-kern. I have to and will reinvestigate the issue again before I add the direct configuration stuff. And it needs to be discussed on tech-kern pre-commit.
True.
OK. I'll rip out the direct configuration stuff and commit the plain device drivers. We'll see more once we are at 5.99.0..
We can already wildcard i2c addresses - if your hw can be probed ( as in - has chip ID registers of some sort ) there really isn't much of a problem.
have fun Michael