All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: David Schaefer <david.tillmann.schaefer@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
Date: Mon, 14 Dec 2020 09:03:21 +0100	[thread overview]
Message-ID: <CAK+FTGhwM02y_eg6cE=GNcOH8G8eQjia0PD+JVrR=eSedQxWAA@mail.gmail.com> (raw)

Hi,

I am trying to upgrade to a more recent kernel. I face the issue that
I am missing the /dev/mtdblock1-6 devices. I have tracked down that
issue shows up the first time with 4.16.1 and does not exist with
4.15.18.

Also I have this initalization during 4.15.18:

> f10d0000.nand: This platform can't do DMA on this device
> nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
> nand: Hynix H27U2G8F2CTR-BC
> nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048
> Bad block table found at page 131008, version 0x01
> Bad block table found at page 130944, version 0x01
> nand_read_bbt: bad block at 0x00000e7c0000
> 7 ofpart partitions found on MTD device pxa3xx_nand-0
> Creating 7 MTD partitions on "pxa3xpxa3xx-nand x_nand-0":
> 0x000000000000-0x000000500000 : "u-Boot"
> 0x000000500000-0x000000a00000 : "uImage"
> 0x000000a00000-0x000000f00000 : "ramdisk"
> 0x000000f00000-0x00000d800000 : "image.cfs"
> 0x00000dd00000-0x00000ec00000 : "rescue firmware"
> 0x00000ec00000-0x000010000000 : "config"
> 0x00000d800000-0x00000dd00000 : "reserve"

and this with 4.16.1:

> nand: device found, Manufacturer ID: 0xad, Chip ID: 0xda
> nand: Hynix H27U2G8F2CTR-BC
> nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> marvell-nfc f10d0000.nand: Timeout on CMDD (NDSR: 0x00000080)
> marvell-nfc f10d0000.nand: Timeout on CMDD (NDSR: 0x00000280)
> Bad block table not found for chip 0
> Bad block table not found for chip 0
> Scanning device for bad blocks
> Bad eraseblock 1854 at 0x00000e7c0000

I have tried 4.19.161 and 5.4.83 as well but my /dev/mtdblock1-6
devices keep being missing.

What do I have to do to turn them back on? Do I have to modify my dts
file for the new driver marvell_nand?
https://fox-exe.ru/WDMyCloud/WDMyCloud-Mirror/Developing/kernel-4.15.0-rc6/armada-370-wdmc-mirror-gen1.dts

I've read whatever I found and do not know how to continue here.

Kind regards
David

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2020-12-14  8:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14  8:03 David Schaefer [this message]
2020-12-14 13:36 ` WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc Richard Weinberger
2020-12-14 14:58   ` David Schaefer
2020-12-14 15:20     ` Richard Weinberger
2020-12-14 17:16       ` David Schaefer
2020-12-14 21:24         ` Richard Weinberger
2020-12-14 23:03           ` Miquel Raynal
2020-12-15 10:14             ` David Schaefer
2020-12-15 15:50         ` David Schaefer
2020-12-15 15:56           ` Miquel Raynal
2020-12-15 16:34             ` David Schaefer
2020-12-15 16:46               ` Miquel Raynal
2020-12-15 21:20                 ` David Schaefer
2020-12-15 22:04                   ` David Schaefer
2020-12-16  7:51                     ` Miquel Raynal
2020-12-17 20:15                       ` David Schaefer

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='CAK+FTGhwM02y_eg6cE=GNcOH8G8eQjia0PD+JVrR=eSedQxWAA@mail.gmail.com' \
    --to=david.tillmann.schaefer@gmail.com \
    --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.