All of lore.kernel.org
 help / color / mirror / Atom feed
From: "nur" <nurpinar@e-kolay.net>
To: "linux-mtd" <linux-mtd@lists.infradead.org>
Subject: Re: unknown chip id FF
Date: Wed, 30 Apr 2003 18:04:25 +0300	[thread overview]
Message-ID: <002a01c30f29$ca04e4e0$3064000a@nur> (raw)
In-Reply-To: 001b01c30f27$a168d890$3064000a@nur

Ok I found the reason still not understanding why
dinfo tells that window adress is d0000
I don't know how it changes or what it depends.
Anyway sorry to bother



----- Original Message -----
From: "nur" <nurpinar@e-kolay.net>
To: "linux-mtd" <linux-mtd@lists.infradead.org>
Sent: Wednesday, April 30, 2003 5:48 PM
Subject: unknown chip id FF


> First of all, i searched my problem through google.com
> Infradead archive refers to wrong pages for a specific subject
> I mean, i m clicking on "DOC 2000 driver (NFTL) in kernel 2.4.7" link but
it
> goes to "Porting FFS2 on MIPS subject"
> So that, I couldn't find any comment about my problem.
>
> I can boot my diskonchip millennium on a platform without any problem.
DoCs
> window address is e8000
> The problem is that, I can't boot the same chip on another platform even
> though I changed window address to e8000 from bios settings
> If I boot from romdos, i can see the content of diskonchip. When I boot
from
> DoC it says, using configured probe address e8000... possible diskonchip
> with unknown chip id FF found at E8000. So can't mount from DoC.
> Any idea would be appreciated. Thanks in advance
>
>
>
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>

      reply	other threads:[~2003-04-30 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 14:48 unknown chip id FF nur
2003-04-30 15:04 ` nur [this message]

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='002a01c30f29$ca04e4e0$3064000a@nur' \
    --to=nurpinar@e-kolay.net \
    --cc=linux-mtd@lists.infradead.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 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.