80MB/s is also LVD. The fastest you can go on a SE narrow chain is in
> >Channel A Target 0 Negotiation Settings
> > User: 40.000MB/s transfers (40.000MHz DT, offset 255)
> > Goal: 20.000MB/s transfers (20.000MHz, offset 31)
> > Curr: 20.000MB/s transfers (20.000MHz, offset 31)
> Hardware thinks the disk just can do Goal=20Mb/s. Why ?
The 29160 card detects which cable a device is hooked to and the driver
then sets the maximum allowed speed according to that. When you plug a
drive into a SE cable, the driver knows it and sets the maximum speed to
> It says nothing about 16 bits... Are you forcing it to narrow
> with a jumper ??
16bit is off in the BIOS settings, so it wouldn't get used regardless.
> >Channel A Target 2 Negotiation Settings
> > User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit)
> > Goal: 20.000MB/s transfers (20.000MHz, offset 15)
> > Curr: 20.000MB/s transfers (20.000MHz, offset 15)
> It recognizes the drive can do wide, but as the first device in the
> chain forced narrow, goal is narrow.
No, the order of devices has no impact on this. No device has any impact
on any other device's speed settings unless they are both connected to the
same physical cable and one of the devices is forcing a cable that *could*
be in LVD mode into SE mode instead. Short of that, all device
negotiations are 100% independant of each other.
-- Doug Ledford <email@example.com> 919-754-3700 x44233 Red Hat, Inc. 1801 Varsity Dr. Raleigh, NC 27606 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/