|To:||Sergei Shtylyov <email@example.com>|
|Subject:||Re: [PATCH 1/2] libata: Add three more columns to the ata_timing table.|
|From:||David Daney <firstname.lastname@example.org>|
|Date:||Tue, 25 Nov 2008 11:09:45 -0800|
|References:||<492B56B0.email@example.com> <firstname.lastname@example.org> <492BDB28.email@example.com> <492C2BCE.firstname.lastname@example.org> <492C4936.email@example.com>|
|User-agent:||Thunderbird 22.214.171.124 (X11/20080723)|
Sergei Shtylyov wrote:
David Daney wrote:Wrong, -DIOR hold time is 5 ns for MWDMA0 as well as for all other modes.Point taken.Besides, I'm not sure how useful that timing could be for the host controller since it's apparently not determined by the host side -- it's for how long the device holds valid data after -DIOR is released IIRC.
Yes, I think you are correct. This is a property of the device and cannot be controlled by the driver, so I will just remove this column in the next version of the patch.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||[PATCH] Alchemy: cpu feature override constants., Manuel Lauss|
|Next by Date:||[PATCH v2] Alchemy: cpu feature override constants., Manuel Lauss|
|Previous by Thread:||Re: [PATCH 1/2] libata: Add three more columns to the ata_timing table., Sergei Shtylyov|
|Next by Thread:||Re: [PATCH 1/2] libata: Add three more columns to the ata_timing table., Jeff Garzik|
|Indexes:||[Date] [Thread] [Top] [All Lists]|