linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Workaround bogus CF cards
Date: 04 May 2003 17:08:25 +0100	[thread overview]
Message-ID: <1052064504.1240.12.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <1052043277.4107.76.camel@gaston>

On Sul, 2003-05-04 at 11:14, Benjamin Herrenschmidt wrote:
> Hi !
> 
> I had a problem with an "APACER" Compact Flash card. It seems that
> beast is allergic to WIN_READ_NATIVE_MAX.

Thats probably a drive->flash check you need looking at the docs I have
I don't see where any CF supports READ_NATIVE_MAX (of course it shouldnt
die either)


  reply	other threads:[~2003-05-04 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-04 10:14 [PATCH] Workaround bogus CF cards Benjamin Herrenschmidt
2003-05-04 16:08 ` Alan Cox [this message]
2003-05-04 17:10   ` Benjamin Herrenschmidt

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=1052064504.1240.12.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).