Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 01 Jul 2007 09:01:29 +0100
From:      Dieter <freebsd@sopwith.solgatos.com>
To:        Peter B <pb@ludd.ltu.se>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: SII3512 rev0 ? 
Message-ID:  <200707011601.QAA29911@sopwith.solgatos.com>
In-Reply-To: Your message of "Sun, 01 Jul 2007 05:08:30 %2B0200." <200707010308.l6138U24009649@brother.ludd.ltu.se> 

next in thread | previous in thread | raw e-mail | index | archive | help
> >> Any input on the reliability of SII3512 is also welcomed.
> >
> >dmesg | grep 3512
> >satalink0: Silicon Image SATALink 3512 (rev. 0x01)
> >
> >No reliability problems from the 3512.  (up 74 days)
> >
> >This is on an Alpha box running NetBSD.  I haven't tried the 3512
> >with FreeBSD.

I took a quick look at the drivers, and found a difference.

NetBSD:

	dev/pci/satalink.c

        /*
         * Rev. <= 0x01 of the 3112 have a bug that can cause data
         * corruption if DMA transfers cross an 8K boundary.  This is
         * apparently hard to tickle, but we'll go ahead and play it
         * safe.
         */
        if (PCI_REVISION(pa->pa_class) <= 0x01) {
                sc->sc_dma_maxsegsz = 8192;
                sc->sc_dma_boundary = 8192;

FreeBSD:

	dev/ata/ata-chipset.c

    if ((ctlr->chip->cfg2 & SIIBUG) && ch->dma) {
        /* work around errata in early chips */
        ch->dma->boundary = 16 * DEV_BSIZE;
        ch->dma->segsize = 15 * DEV_BSIZE;
    }

And of course there may be other differences I didn't find.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200707011601.QAA29911>