From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd_sf: add handler for +len arg for all commands
Date: Sat, 11 Oct 2014 18:22:27 +0200 [thread overview]
Message-ID: <201410111822.27688.marex@denx.de> (raw)
In-Reply-To: <CAGduivxdjWbZi62O93AJhGQZ8TUypd72ECKqPztEt9e=Fi9AhA@mail.gmail.com>
On Friday, October 10, 2014 at 11:16:05 PM, Maxime Hadjinlian wrote:
> Hi all,
Hi!
[...]
> >> +CC Altera guys, they might help too.
> >
> > Hmmm.... quite strange to write for sector aligned.
> > Wonder the write related to filesystem access?
> >
> > Within Cadence QSPI controller, read and write access need to be done
> > within a page. But that would be taken care by controller when the
> > access beyond the next page. From software perspective, we just tell
> > controller the numbers of bytes to be transfer (for indirect transfer
> > setup).
>
> My needs have evolved a bit, and I no longer require this function.
> But I wasn't able to right a file tftp into RAM using 'sf update'
> without this patch.
> I could try to reproduce the errors and maybe dig in a little more.
This would be really helpful. Esp. since the Cadence QSPI driver is
coming to mainline in next MW.
Thank you!
Best regards,
Marek Vasut
prev parent reply other threads:[~2014-10-11 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 16:39 [U-Boot] [PATCH] cmd_sf: add handler for +len arg for all commands Maxime Hadjinlian
2014-10-05 17:43 ` thomas.langer at lantiq.com
2014-10-05 18:40 ` Maxime Hadjinlian
2014-10-05 19:12 ` Marek Vasut
2014-10-05 19:19 ` thomas.langer at lantiq.com
2014-10-05 19:27 ` Maxime Hadjinlian
2014-10-05 19:45 ` Marek Vasut
2014-10-05 19:51 ` Maxime Hadjinlian
2014-10-05 20:28 ` Marek Vasut
2014-10-05 20:35 ` Maxime Hadjinlian
2014-10-05 20:55 ` Marek Vasut
2014-10-08 8:35 ` Chin Liang See
2014-10-10 21:16 ` Maxime Hadjinlian
2014-10-11 16:22 ` Marek Vasut [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=201410111822.27688.marex@denx.de \
--to=marex@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox