Re: [PATCH #upstream-fixes] libata: implement and use HORKAGE_NOSETXFER

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

 



> > Sorry you can't just blindly do this because some of the controllers snoop
> > the SETXFER command to set their timings and whether they expect DMA. Also
> > we've no idea if this is a bug in a specific firmware revision, a quirky
> > pata/sata bridge or a timing problem of some sort.
> 
> I think it'll generally be okay for SATA unless it's bridged over to
> PATA controller.  Any other ideas?

We seem to have one report, from one user, with one configuration, on one
controller, using one firmware set.

That to me isn't meaningful evidence of anything that needs a workaround,
beyond maybe doing what old IDE does and if a setxfer times out
continuing in hope.

(We should of course then re-read the identify pages and check the mode
in use)

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

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux