Re: sata_inic162x driver for 2.6.19 timeouts etc

[Tejun Heo <htejun@gmail.com>]

Hello,

Bob Stewart wrote:
> Is there an easy way to tell whether the command was sent as 
> LBA48, say, in the driver's bmdma_start function or even in the 
> hardreset function after the fact?  One of my tests was using a 64 
> sector limit, with pretty much the same results.  I always test against 
> the same file, and the results, including the number of timeouts, are 
> different from test to test.

The driver is seriously broken regarding LBA48 support.  The timeout
goes away if max_sectors is decreased to ATA_MAX_SECTORS - 1, doh.  But
both the reading and writing are seriously broken.  I can't tell whether
they end up in the wrong sectors or garbage is transferred to/from the
right sectors.

I'm really close to marking this device broken or we'll need to
implement a mechanism to veto LBA48 device from LLD (may be negative
return from ->dev_config).

Reading the sunix driver, I can't find any relevant workaround.  It
never seems to initialize ctl address.  I'm curious whether the sunix
driver can do LBA48.  Bob, are you interested in testing this?

Thanks.

-- 
tejun