Subject: Re: cmdide.c: CMD Technology product 0x0680
To: None <port-i386@NetBSD.org>
From: Sean Davis <firstname.lastname@example.org>
Date: 03/08/2004 11:58:25
On Mon, Mar 08, 2004 at 05:27:58PM +0100, Hanspeter Roth wrote:
> On Mar 08 at 16:32, email@example.com spoke:
> > I bought the same controller a week ago. 1.6.x does not have support for it.
> > Just update your kernel to a current one and use the cmdide(4) driver:
> ?Just?? I guess I'll practice upgrading to current on another system
> first. Can one run a current kernel on base system of 1.6.2?
> Shouldn't the base system be upgraded to current too?
> > cmdide0 at pci0 dev 20 function 0
> > cmdide0: Silicon Image 0680 (rev. 0x02)
> > cmdide0: bus-master DMA support present
> > cmdide0: primary channel configured to native-PCI mode
> > cmdide0: using irq 10 for native-PCI interrupt
> > Works fine :)
> In fact I'm trying NetBSD on a system which is running FreeBSD 4.9 now.
> Just it has a little instability. So I thought I'll try NetBSD.
> But current is probably not too stable, is it?
I run -current on four machines (two i386, one alpha, one ultrasparc) here,
and it's quite stable. Of course, I always test a new build of current on a
box which I don't do anything critical on (and can thus reinstall if it
breaks without much hassle) before installing on the others, but I haven't
had any severe problems with current in years, and that was a network driver
bug that was present in the releases as well.
/~\ The ASCII
\ / Ribbon Campaign Sean Davis
X Against HTML aka dive
/ \ Email!