mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard A. Smith" <rsmith@bitworks.com>
To: "andre@linux-ide.org" <andre@linux-ide.org>,
	"Padraig Brady" <Padraig@AnteFacto.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Steffen Grunewald" <steffen@gfz-potsdam.de>
Subject: Re: Cool Road Runner (was CFA as Ide.)
Date: Mon, 02 Apr 2001 15:25:25 -0500	[thread overview]
Message-ID: <MDAEMON-F200104021529.AA291937MD92027@bitworks.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104020738550.12531-100000@master.linux-ide.org>

On Mon, 23 Apr 2001 21:57:12 -0700 (PDT), Andre Hedrick wrote:

>> OK can we just have a technical discussion?

>Please, lets do, I am tired of the battles

Me three... I am much better at tech than flames although I seemed to have missed all the 
flambe.

BTW... why is this thread called Road Runner?

>>      I.E. no need for PCMCIA or any of that. I understood from your 
>> responses that you didn't realise this?

>This valid that I do not know everything and that CFA does interesting
>things more than what was specified in the past.

The converse is true as well.. Having only used the CFA devices as solid state IDE drives I 
was unaware that there were any that didn't do the True IDE mode.

>Sorry phone call and email got mixed togather.
>But I did explain that there could be a failure to detect if PDIAG/DASP
>if one or the other devices was held to long and the wrong device reported
>a signature in the task register.  Also that the if you reversed the two
>device it would correctly report always.

Yes... Now that I am up on the docs I see exactly how this can happen.  Mishandled signals 
would cause device 0 to go 30 seconds before it gave up on Device 1.

Andre, do you think it's reasonable to assume that if most PC BIOS's will detect the CFA then 
it probally is handling the POR sequence and EXECUTE DEVICE DIAGNOSIC correctly?
If so then I feel pretty confident that it should work ok.. Over the 2 years we have been 
using CFAs as solid state HD's I have never seen a case where the BIOS didn't autodetect it 
properly as master or slave or have I had a problem with a long timeout.  I have plugged it 
up to all manner of machine old and new.. An the usual configuration was that the CFA was 
Device 0 and some random IDE drive we have laying around was device 1.

Now I am not saying it won't happen.. just that I haven't seen it.

>Not quite, the electronic differences and flash in native mode is
>incompatible, if you put it in to a mode that is 5V compatable then it
>does seem possible and reasonable to work.  Your imperical data points
>verify this issue.

Not to mention that the datasheet for the device indicates that this is possible and intended  
not just happenstance.  *grin*

>What really needs to happen is that all the devices that are CFA-like
>which require name parsing for detecting should have the "flash" rule
>imposed.  Whereas the ones that correctly report 0x848A for word 0 of the
>identify page may be exempt.

Yes I think so... Although I haven't done a rigorous reading of the SanDisk datasheet I 
haven't found anything so far that would lead me to believe that operates any different than 
an ATA-2 device when operating in True IDE mode.

IIRC SanDisk was the original people to come out with IDE CFA and everyone else just copied 
them.  I have the SanDisk datasheets that I can send you if you need them to verify stuff.  I 
believe that if you verify it with the SanDisk then all the other MFG's should work as well.

--
Richard A. Smith                         Bitworks, Inc.               
rsmith@bitworks.com               501.846.5777                        
Sr. Design Engineer        http://www.bitworks.com   



  parent reply	other threads:[~2001-04-02 20:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30 15:59 Cool Road Runner Steffen Grunewald
2001-03-30 17:14 ` Gnea
2001-03-30 17:28   ` Steffen Grunewald
2001-03-30 17:52 ` Andreas Dilger
2001-04-02  6:55   ` Steffen Grunewald
2001-04-02  6:55     ` Andre Hedrick
2001-04-02  8:21       ` Steffen Grunewald
2001-04-02  8:01         ` Andre Hedrick
2001-04-02 13:07           ` Padraig Brady
2001-04-24  4:57             ` Andre Hedrick
2001-04-02 18:27               ` Padraig Brady
2001-04-24  6:09                 ` CFA Membership (Re: Cool Road Runner) Andre Hedrick
2001-04-02 19:15                   ` Padraig Brady
2001-04-02 20:25               ` Richard A. Smith [this message]
2001-04-02 20:50                 ` Cool Road Runner (was CFA as Ide.) Adrian Cox
2001-04-02 21:19                   ` Richard A. Smith
2001-04-02 21:50                     ` Adrian Cox
2001-04-02 16:59     ` Cool Road Runner Richard Gooch
2001-04-03  6:59       ` Richard Gooch
2001-04-03  8:16         ` Strange Syslog-Entry and Machine Lockup Andreas Rogge
2001-04-24  5:32       ` Cool Road Runner Andre Hedrick

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=MDAEMON-F200104021529.AA291937MD92027@bitworks.com \
    --to=rsmith@bitworks.com \
    --cc=Padraig@AnteFacto.com \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steffen@gfz-potsdam.de \
    /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

all inboxes | Powered by JetHome®