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: Sun, 5 Oct 2014 21:45:33 +0200 [thread overview]
Message-ID: <201410052145.34019.marex@denx.de> (raw)
In-Reply-To: <CAGduivxZuc6z0x9zQn4-6Gw9bRcLZwC_W6SQo9xM_+57LECgrQ@mail.gmail.com>
On Sunday, October 05, 2014 at 09:27:00 PM, Maxime Hadjinlian wrote:
> On Sun, Oct 5, 2014 at 9:19 PM, <thomas.langer@lantiq.com> wrote:
> >> On Sunday, October 05, 2014 at 08:40:26 PM, Maxime Hadjinlian wrote:
> >> > Hi Thomas, all,
> >> >
> >> > On Sun, Oct 5, 2014 at 7:43 PM, <thomas.langer@lantiq.com> wrote:
> >> > > Hello Maxime,
> >> > >
> >> > > can you explain the usecase?
> >> > > I think, only the erase is executed per sector, all other commands
> >> > > are working fine with a byte oriented length.
> >> >
> >> > I need to write a file that is downloaded through TFTP. So I can get
> >> > the filesize through the variable of the same name, but if it's not
> >> > rounded, the write command may fail.
> >> > I can save the filesize in another variable, but at next boot, when I
> >> > need to read this file, I can't read the file, since I only know it's
> >> > size in byte, I need to be able to round it again.
> >>
> >> I wonder, do all SPI flashes need to do sector-aligned writes ?
> >
> > All the serial flashes I have seen so far do support reading and writing
> > with any length, independent from the erase size.
> > Otherwise the current implementation of env_sf.c would also not work.
>
> Well the QSPI, I used, does not. Every read and write has to be
> aligned. That's why I needed that in the first place.
Aligned how exactly?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-10-05 19:45 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 [this message]
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
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=201410052145.34019.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 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.