public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Ollie Lho <ollie@sis.com.tw>
Cc: Jason Walker <jasonw@uswo.net>,
	MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: Oddities with MTD/DOC
Date: Wed, 09 May 2001 10:57:21 +0100	[thread overview]
Message-ID: <29986.989402241@redhat.com> (raw)
In-Reply-To: <3AF90A9C.E0FE06F2@sis.com.tw>

ollie@sis.com.tw said:
>  It happens a lot. You got two options: 1. replace it with another, 2.
> wait a few days, sometimes it just come back "magically". 

Eep. Complete death of the hardware? That's not good. How can it happen?

I assume that if it's a DiskOnChip Millennium you've tried probing without 
the CONFIG_DOCPROBE_55AA option, in case it's just overwritten the start of 
the flash?

--
dwmw2

  reply	other threads:[~2001-05-09 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-08 23:38 Oddities with MTD/DOC Jason Walker
2001-05-09  9:15 ` Ollie Lho
2001-05-09  9:57   ` David Woodhouse [this message]
2001-05-09 14:14 ` Shuh C Chang
  -- strict thread matches above, loose matches on Subject: below --
2001-05-09 15:16 Vadim Khamlinsky

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=29986.989402241@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jasonw@uswo.net \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ollie@sis.com.tw \
    /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