All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: David Schaefer <david.tillmann.schaefer@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc
Date: Mon, 14 Dec 2020 18:16:19 +0100	[thread overview]
Message-ID: <CAK+FTGirwvd5Sdww4kkYCy0BMmnZsP=Tq=cAePxraXa3AcGbiQ@mail.gmail.com> (raw)
In-Reply-To: <2020191742.126461.1607959229137.JavaMail.zimbra@nod.at>

If this is a regression, how can we continue here? Can I give hardware
specs and logs? I have soldered on the board to access UART. I can
provide e.g. boot logs.

/David

Am Mo., 14. Dez. 2020 um 16:20 Uhr schrieb Richard Weinberger <richard@nod.at>:
>
> David,
>
> ----- Ursprüngliche Mail -----
> > I have checked the kernel configuration. For 4.15.18 I have these settings:
> > CONFIG_MTD_NAND_ECC=y
> > CONFIG_MTD_NAND=y
> > CONFIG_MTD_NAND_PXA3xx=y
> >
> > and for 4.16.1
> >
> > CONFIG_MTD_NAND_ECC=y
> > CONFIG_MTD_NAND=y
> > CONFIG_MTD_NAND_MARVELL=y
> >
> > I actually copied the working configuration from 4.15.18 to 4.16.1,
> > did make oldconfig, and compiled it the same way as 4.15.18. Like I
> > said above, 4.15 works, 4.16 does not.
> > I hope this answers your question whether I see the issue with the new
> > and the old marvell drivers because I am not 100% sure what you refer
> > to here (I guess you mean PXA3XX vs NAND).
>
> Ah, right. I forgot that the old driver got removed. I thought we kept it for a few releases. ;-\
> So there is a regression.
>
> Thanks,
> //richard

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

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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14  8:03 WD MyCloud Ex, Armada-370, pxa3xx-nand, marvell-nfc David Schaefer
2020-12-14 13:36 ` Richard Weinberger
2020-12-14 14:58   ` David Schaefer
2020-12-14 15:20     ` Richard Weinberger
2020-12-14 17:16       ` David Schaefer [this message]
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+FTGirwvd5Sdww4kkYCy0BMmnZsP=Tq=cAePxraXa3AcGbiQ@mail.gmail.com' \
    --to=david.tillmann.schaefer@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    /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.