From: Igor Plyatov <plyatov@gmail.com>
To: Stanislaw Gruszka <stf_xl@wp.pl>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] ATA: pata_at91.c bugfixes
Date: Thu, 12 May 2011 16:03:40 +0400 [thread overview]
Message-ID: <4DCBCC9C.2040209@gmail.com> (raw)
In-Reply-To: <20110501211716.GA5217@localhost.localdomain>
Hello Stanislaw!
Thank you for patience and detailed explanations!
Sorry for long delays between answers, but I must work with another
projects.
>
>>>> * The NCS signal is not the same as CS1, CS2 ATA signals! It used only to
>>>> enable data bus transceiver U2.
>>> Well, they are different signals but connected together. All of these are
>>> controlled by NCS: CFCE1 (CS1), CFCE2 (CS2), CFRNW (DIR), CFCS0 (OE)
>>> if SMC is configured in True IDE mode.
>> I must repeat again - NCS ("CFCS1" from schematic) are completely
>> different signal for different purpose, then A0, A1, A2, CS0, CS1.
>> It used only to enable data bus transceiver U2.
> So, how in your opinion CS0 and CS1 are controlled? IMO there
> are delivered from CFCE1 and CFCE2, which itself are delivered
> from NCS. Here is corresponding quote from atmel documentation
> you cited above:
>
> "The CFCE1 and CFCE2 waveforms are identical to the corresponding NCSx waveform"
This makes picture completely clean for me now.
I will publish new version patch for pata_at91.c.
Best regards!
--
Igor Plyatov
next prev parent reply other threads:[~2011-05-12 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 11:44 [PATCH] ATA: pata_at91.c bugfixes Igor Plyatov
2011-04-23 9:36 ` Stanislaw Gruszka
2011-04-26 6:38 ` Igor Plyatov
2011-04-27 18:38 ` Stanislaw Gruszka
2011-04-29 7:56 ` Stanisław Gruszka
[not found] ` <4DBA9E2F.3070100@gmail.com>
2011-05-01 21:17 ` Stanislaw Gruszka
2011-05-12 12:03 ` Igor Plyatov [this message]
2011-04-24 15:35 ` Jeff Garzik
2011-05-12 12:05 ` Igor Plyatov
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=4DCBCC9C.2040209@gmail.com \
--to=plyatov@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.