All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benedikt Spranger <b.spranger@linutronix.de>
To: Alexander Dahl <ada@thorsis.com>
Cc: u-boot@lists.denx.de, John Ogness <john.ogness@linutronix.de>
Subject: Re: [PATCH 0/5] collected fallout of porting an ATSAMA5D27 based board
Date: Fri, 18 Oct 2024 16:19:08 +0200	[thread overview]
Message-ID: <20241018161908.3f6a13eb@mitra> (raw)
In-Reply-To: <20241018-unsubtle-yield-8ac617356e92@thorsis.com>

On Fri, 18 Oct 2024 15:11:20 +0200
Alexander Dahl <ada@thorsis.com> wrote:

Hello Alexander,

> Am Fri, Oct 18, 2024 at 10:30:00AM +0200 schrieb Benedikt Spranger:
> > OK, you might say the nand_atmel NAND driver is obsolete, but it
> > was the only solution to get booting from NAND running. The new DM
> > based NAND driver refused to do anything usefull, so I dropped it
> > after spending a couple of days debugging it:
> 
> Strange.  I have at least three different boards with SAMA5D27
> successfully booting from NAND flash with the new DM based driver
> (unfortunately none of them upstreamed, which also won't change in the
> foreseeable future, sorry).
OK.
 
> Do you use at91bootstrap as 2nd level bootloader like me or something
> else?
I use the U-Boot SPL. There is no UBI support in at91boostrap. There
were some attemps, but...
No interest at the at91bootstrap side.

> For me it was basically getting the dts for U-Boot correct, but
> I got that running with all U-Boot releases since 2023.04 up to
> 2024.10.  Could you share some more detail?
I face all the trouble in SPL. And since the SPL is the essential part
here (UBI support) I gave up at one point. I simply couldn't any
usefull read data from the NAND flash, but all 0.

Regards
    Benedikt Spranger

  reply	other threads:[~2024-10-18 14:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  8:30 [PATCH 0/5] collected fallout of porting an ATSAMA5D27 based board Benedikt Spranger
2024-10-18  8:30 ` [PATCH 0/5] collected fallout of porting an ATSAMA5D2 " Benedikt Spranger
2024-11-12 13:45   ` Eugen Hristev
2024-11-19 15:46     ` Eugen Hristev
2024-11-21 22:48       ` Michael Nazzareno Trimarchi
2024-10-18  8:30 ` [PATCH 1/5] tiny-printf: Handle NULL pointer argument to %s Benedikt Spranger
2024-10-18  8:30 ` [PATCH 2/5] drivers/mtd/ubispl/ubispl.c: Fix error message Benedikt Spranger
2024-10-18  8:30 ` [PATCH 3/5] mtd: nand: raw: Fix potential NULL pointer dereference Benedikt Spranger
2024-10-18  8:30 ` [PATCH 4/5] mtd: nand: Update NAND manufacturer Ids Benedikt Spranger
2024-11-12 13:39   ` Eugen Hristev
2024-11-12 13:57     ` Benedikt Spranger
2024-11-12 14:48       ` Eugen Hristev
2024-10-18  8:30 ` [PATCH 5/5] mtd: nand: raw: atmel_nand: Add missing nand_scan_ident() Benedikt Spranger
2024-10-18 13:11 ` [PATCH 0/5] collected fallout of porting an ATSAMA5D27 based board Alexander Dahl
2024-10-18 14:19   ` Benedikt Spranger [this message]
2024-10-21  6:03     ` Alexander Dahl
2024-10-21  7:17       ` Eugen Hristev
2024-10-21  7:36         ` Alexander Dahl
2024-10-21 12:49           ` Eugen Hristev
2024-10-21 12:30         ` Benedikt Spranger
2024-10-21 12:47           ` Eugen Hristev
2024-10-21 10:20       ` Benedikt Spranger
2024-10-21 10:51         ` Alexander Dahl

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=20241018161908.3f6a13eb@mitra \
    --to=b.spranger@linutronix.de \
    --cc=ada@thorsis.com \
    --cc=john.ogness@linutronix.de \
    --cc=u-boot@lists.denx.de \
    /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.