mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: barebox@lists.infradead.org
Subject: AM335x NAND write hungs
Date: Mon, 25 Jan 2021 11:20:04 +0300	[thread overview]
Message-ID: <CAP1tNvT79QvYYTL9O+V+HR=XVTKHS=UxJtc1ZvNaMu1yQZns9w@mail.gmail.com> (raw)

Hello.

I recently upgraded my barebox from 2020.11 to 2021.01 for a custom board
based on TI AM335x processor.
The update revealed the inoperability of writing to NAND. When trying to write,
the bootloader hangs forever.
Reverting the commit "mtd: nand: omap_gpmc: Fix wrong length check" helps
to solve the problem.
Does anyone have similar problems?

Thanks!

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2021-01-25  8:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25  8:20 Alexander Shiyan [this message]
2021-01-25  8:37 ` Ahmad Fatoum
2021-01-25  8:56   ` Alexander Shiyan
2021-01-25  9:21     ` Ahmad Fatoum
2021-01-25  9:21 ` [PATCH] mtd: nand: omap_gpmc: Fix wrong length check for real Sascha Hauer

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='CAP1tNvT79QvYYTL9O+V+HR=XVTKHS=UxJtc1ZvNaMu1yQZns9w@mail.gmail.com' \
    --to=eagle.alexander923@gmail.com \
    --cc=barebox@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox