Re: fastest UltraSPARC hardware NetBSD runs on?

[Michael <macallan%netbsd.org@localhost>]

Hello,

On Oct 28, 2008, at 12:37 PM, Jochen Kunz wrote:

> On Tue, 28 Oct 2008 11:07:43 -0400
> Michael <macallan%netbsd.org@localhost> wrote:
>
> > Umm, there's prior art for this in the kernel which does not require
> > rototilling all i2c drivers. See sys/arch/macppc/dev/ki2c.c and
> > ki2c_dbcool.c.
> > It does just what you try to do - attach i2c devices using
> > information from OpenFirmware.
> I saw this and found it to be a bad idea. It is unable to attach any
> existing i2c device. Instead it introduces a new "bus": ki2c. This way
> any i2c device, that wants to attach to ki2c, needs a special MD ki2c
> attachment stub. Thus existing i2c drivers would need to be split up  
> in
> a MI backend and a MD / bus dependent frontend. If this isn't
> rototilling, what else is rototilling?

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?

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.

have fun
Michael