public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Cox <adrian@humboldt.co.uk>
To: "Richard A. Smith" <rsmith@bitworks.com>
Cc: "andre@linux-ide.org" <andre@linux-ide.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Padraig Brady <Padraig@AnteFacto.com>,
	Steffen Grunewald <steffen@gfz-potsdam.de>
Subject: Re: Cool Road Runner (was CFA as Ide.)
Date: Mon, 02 Apr 2001 22:50:47 +0100	[thread overview]
Message-ID: <3AC8F437.2000601@humboldt.co.uk> (raw)
In-Reply-To: <MDAEMON-F200104021623.AA231904MD92067@bitworks.com>

Richard A. Smith wrote:

> On Mon, 02 Apr 2001 21:50:59 +0100, Adrian Cox wrote:
>> If only. In my limited experience SanDisk cards have been the most 
>> tolerant. I suspect that Sandisk actually implement the full range of 
>> timings documented in the spec, and nobody else bothers.
[...]

> We do actually use SST (Silcon Storage Technolog) CF's as well and they seem to function just 
> identical to the SanDisk but not quite as robust... I have had several of the SST's develope 
> a problem in the partition table and as thus the just error when you try to mount them.
> Several people on the liunx-embedded list also have similar experiences.
> 
> That seems to follow your observations...
> 
> Will it be worth while for you if I break out the scope and examine how our CF's handle the 
> PDIAG signal or can we just go on faith that they do indeed work as expected?

Might be interesting to see. The worst trouble I've had has been with 
noname parts from high street computer stores, and I don't know who the 
original manufacturer was. If I knew what subset of functionality 
digital cameras used I'd know what could be relied on.

- Adrian


  reply	other threads:[~2001-04-02 21:52 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               ` Cool Road Runner (was CFA as Ide.) Richard A. Smith
2001-04-02 20:50                 ` Adrian Cox
2001-04-02 21:19                   ` Richard A. Smith
2001-04-02 21:50                     ` Adrian Cox [this message]
2001-04-02 16:59       ` Cool Road Runner Richard Gooch
2001-04-24  5:32         ` Andre Hedrick
2001-04-03  6:59           ` Richard Gooch
2001-04-03  8:16             ` Strange Syslog-Entry and Machine Lockup Andreas Rogge

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=3AC8F437.2000601@humboldt.co.uk \
    --to=adrian@humboldt.co.uk \
    --cc=Padraig@AnteFacto.com \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rsmith@bitworks.com \
    --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