From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFC v2] non-blocking flash write/erase/status check functions
Date: Mon, 25 Jan 2010 09:35:08 +0100 [thread overview]
Message-ID: <201001250935.08840.sr@denx.de> (raw)
In-Reply-To: <20100122120340.7FAB53F6C0@gemini.denx.de>
On Friday 22 January 2010 13:03:40 Wolfgang Denk wrote:
> > > More tightly integrated non-blocking variants of some CFI flash access
> > > functions. Enable with CONFIG_SYS_FLASH_CFI_NONBLOCK
> > > These can be useful to erase flash or write complete sectors of flash
> > > during a serial data transfer for software updates.
> >
> > The first version had a strong NACK by Wolfgang Denk because of
> > code duplication. Does this version have a chance for inclusion,
> > or are there other things I have to fix/change to get it to this
> > stage?
>
> The patch is still pretty intrusive - the resulting code is much
> harder to read, to understand and to debug (in both configurations).
>
> From my point of view the disadvantages compared to the advantages
> (and the potential number of users of this new feature) don't justify
> to apply this patch.
>
>
> Stefan, what do you think?
I have the same feeling. Even though Wolfgang Wegner has put bigger effort
into making this less intrusive, it still makes the CFI driver even more
complex and less readable.
So I tend to not pull this patch (Sorry Wolfgang).
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
prev parent reply other threads:[~2010-01-25 8:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 12:51 [U-Boot] non-blocking flash functions - is this possible/acceptable? Wolfgang Wegner
2009-10-27 13:21 ` Jerry Van Baren
2009-10-27 14:03 ` Jerry Van Baren
2009-10-27 15:22 ` Wolfgang Wegner
2009-10-27 15:57 ` Jerry Van Baren
2009-10-27 15:24 ` Wolfgang Wegner
2009-10-27 18:58 ` Wolfgang Denk
2009-10-30 14:48 ` [U-Boot] [RFC PATCH] Implementation of non-blocking flash write/erase/status check functions Wolfgang Wegner
2009-10-30 15:02 ` Wolfgang Wegner
2009-10-30 18:22 ` Wolfgang Denk
2009-11-02 16:26 ` [U-Boot] [PATCH] " Wolfgang Wegner
2009-11-02 16:33 ` [U-Boot] [RFC PATCH] Implementation of " Wolfgang Wegner
2009-12-09 16:00 ` [U-Boot] [PATCH RFC v2] " Wolfgang Wegner
2010-01-22 10:03 ` Wolfgang Wegner
2010-01-22 12:03 ` Wolfgang Denk
2010-01-25 8:35 ` Stefan Roese [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=201001250935.08840.sr@denx.de \
--to=sr@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