From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: rah@bash.sh, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] hpt366: UltraDMA filter for SATA cards (take 2)
Date: Fri, 24 Aug 2007 22:11:05 +0400 [thread overview]
Message-ID: <46CF1F39.6000908@ru.mvista.com> (raw)
In-Reply-To: <200708212236.10803.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
>>The Marvell bridge chips used on HighPoint SATA cards do not seem to support
>>the UltraDMA modes 1, 2, and 3 as well as any MWDMA modes, so the driver needs
>>to account for this in the udma_filter() method. In order to achieve that, do
>>the following changes:
>>- install the method for all chips, not only HPT36x/370 and impove the code
>> formatting by killing the extra tabs while at it;
> s/impove/improve/
Will fix in the updated patch...
>>- add to the end of the 'switch' statement in the method cases for HPT372[AN]
>> and HPT374 chips upon which the known SATA cards are based;
>>- use hwif->ultra_mask as a default mask for the ide_dma_filter() method to
>> behave correctly;
... and I was actually going to get rid of all explict masks there, just
modifying the 'mask' variable -- this was may paper version but I was in hury
and forgotten to look at this particular place.
>>- move the HPT370[A] cases below the HPT36x case for consistency.
>>While at it, replace the explicit UltraDMA mode masks with ATA_UDMA* constants
>>all over the driver...
This is certainly worth a big patch covering all PCI drivers. Maybe I'll
cook it up. For now, I'm going to drop this part
>>Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> applied
... with imminent recast. :-)
>>---
>>This is against the current Linus tree and unfortunately I was able to only
>>compile test it since that tree gives MODPOST warning and dies early on bootup.
> Is this still case? Not an IDE problem but definitely needs fixing especially
> given that we are already in -rc3...
Yeah, it is, at least on my Geode GX2 testing target.
>>Will hopefully finish with the patch series next weekend...
I'll do my best (althou I've already encountered trouble with displays
suddenly being blanked -- some{one|thing} set the standby timer to 1-2
minutes. :-) Beside that my typing loses as an effect of some pills. +:-)
MBR, Sergei
next prev parent reply other threads:[~2007-08-24 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 19:00 [PATCH 2/4] hpt366: UltraDMA filter for SATA cards (take 2) Sergei Shtylyov
2007-08-21 20:36 ` Bartlomiej Zolnierkiewicz
2007-08-24 18:11 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-25 19:15 Sergei Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46CF1F39.6000908@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rah@bash.sh \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).