From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, stf_xl@wp.pl
Subject: Re: [PATCH 2/2] ide: add support for CFA specified transfer modes (take 2)
Date: Mon, 09 Mar 2009 00:05:46 +0300 [thread overview]
Message-ID: <49B4332A.8080206@ru.mvista.com> (raw)
In-Reply-To: <200903081743.49038.bzolnier@gmail.com>
Hello.
Bartlomiej Zolnierkiewicz wrote:
>>> Add support for the CompactFlash specific PIO modes 5/6 and MWDMA modes 3/4.
>>>
>>> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
>>>
>>> ---
>>> Did two changes after Bart's review:
>>> - fixed wrong mask in ide_config_drive_speed();
>>> - clarified comment in ide_pio_cycle_time().
>>>
>>> This patch is against the current pata-2.6 series. Since there were no PIO5
>>> capable hard drives produced and you also need 66 MHz input clock to actually
>>> get the difference WRT the setup timing programmed, I decided to simply replace
>>> the old non-standard PIO mode 5 timings with CFA specified ones.
>>> Phew, hopefully I haven't overlooked anything -- quite a lot had to be changed.
>>>
>>> Stanislaw, please give it a try -- I don't have any CF hardware now.
>>>
>>>
>> [...]
>>
>>> Index: linux-2.6/drivers/ide/ide-iops.c
>>> ===================================================================
>>> --- linux-2.6.orig/drivers/ide/ide-iops.c
>>> +++ linux-2.6/drivers/ide/ide-iops.c
>>> @@ -389,6 +389,8 @@ int ide_config_drive_speed(ide_drive_t *
>>> id[ATA_ID_UDMA_MODES] &= ~0xFF00;
>>> id[ATA_ID_MWDMA_MODES] &= ~0x0F00;
>>> id[ATA_ID_SWDMA_MODES] &= ~0x0F00;
>>> + if (ata_id_is_cfa(id))
>>> + id[ATA_ID_CFA_MODES] &= ~0x0FC0;
>>>
>>>
>> Oops, won't this fragment clear the current DMA mode when setting PIO
>> mode (and so vice versa for CF)?
>>
>
> Indeed, however since we never check selected modes later (except
> ide_id_dma_bug() but its intent is to check for buggy devices)
> there is no much point in all these id hacks and this seems to be
> the perfect opportunity to just remove them.
>
Doesn't this serve for e.g. presenting the current identify data via
procfs? I've been already considering fixing this...
> Thanks,
> Bart
>
MBR, Sergei
prev parent reply other threads:[~2009-03-08 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 17:09 [PATCH 2/2] ide: add support for CFA specified transfer modes (take 2) Sergei Shtylyov
2009-03-07 21:12 ` Sergei Shtylyov
2009-03-08 16:43 ` Bartlomiej Zolnierkiewicz
2009-03-08 21:05 ` Sergei Shtylyov [this message]
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=49B4332A.8080206@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=stf_xl@wp.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.