RE: [PATCH] mptspi : min_period, max_offset, max_width,incorrectlyset, resulting domain validation failing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2006-09-19 at 17:06 -0600, Moore, Eric wrote:
> Also, the algorithm in spi_transport is broke for U160 devices. Its
> sending U320
> nego to U160 devices.  What it should do is check for
> scsi_device_ius(sdev) == 0
> and scsi_device_qas(sdev) == 0, then spi_min_period(sdev)=0x9.  Due to
> this,
> spi transport dv ends up with FAST-40, instead of U160, becuase the nego
> at factor=0x8 failed.

Well, by standard, I'm supposed to start out negotiation with the
fastest I can possibly do and the drive modifies this in its reply.  The
heuristics over DT vs non-DT in the transport class are to cope with
arguably buggy drives in the field.  I've never come across a DT capable
drive on an LVD bus that showed a problem in this regard ... have you
found one?

James


-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux