Re: support for SATA port multipliers

[Reinoud Zandijk <reinoud%NetBSD.org@localhost>]

Hi folks, hi Kiyohara,

On Thu, Feb 02, 2012 at 04:18:10PM +0000, David Brownlee wrote:
> > I think both are equally urgent. As most SATA drives comes with a
> > large write-back cache enabled by default, I'm not sure NCQ will give
> > a lot of performances improvements in the common case.
> 
> What sort of hardware are we looking at here for the port multiplier?
> Something like http://www.cooldrives.com/siseata5pomu.html ?

AFAIK my LG NAS has a SATA multiplexer that is not understood/supported...
Last time i tried at allow cd* attach to atapibus? it crashed. It was
configured as:

cd*    at atapibus? drive ? flags 0x0000

I added ``MAIL TO kiyohara@ it crashes on boot -> SATA multiplexer?'' but
euhh...  i think i forgot to write that mail :-) so here it is!

Currently the dmesg now tells:
----
mvsata0 at mvsoc0 unit 0 offset 0x80000-0x87fff irq 21: Marvell Serial-ATA
    Host Controller (SATAHC)
mvsata0: GenIIe, 1hc, 2port/hc
atabus0 at mvsata0 channel 0
atabus1 at mvsata0 channel 1
mvsata0 port 1: device present, speed: 3.0Gb/s
wd0 at atabus1 drive 0
wd0: <Hitachi HDS721010CLA332>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect x 1953525168 sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
mvsata0:0:1: device disconnect
wd0(mvsata0:1:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)

> dmesg | grep atabus0
atabus0 at mvsata0 channel 0
> dmesg | grep atabus1
atabus1 at mvsata0 channel 1
wd0 at atabus1 drive 0
----

This might be the DVD+RW recoder:
    mvsata0:0:1: device disconnect

With regards,
Reinoud