Attention is currently required from: Simon Buhrow, Nico Huber, Angel Pons.
Hello build bot (Jenkins), Nico Huber,
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/flashrom/+/58467
to look at the new patch set (#4).
Change subject: flashchips.c: big erase blocksize first
......................................................................
flashchips.c: big erase blocksize first
Choosing the best fitting erase block size can safe
a significant amount of runtime. Changing the order
of entries of block_erasers in flashchips.c going
from the bigger block size to lower block size does
a better job.
I am running flashrom inside a VirtualBox so the
gained time is quite big.
Setup: IS25LP064 flash + ft2232H programmer
Saved time: > 2 min for single '-E' operation
Change-Id: I862ce0b5f8912565e43c340578d8126aa2e6aa3b
Signed-off-by: Simon Buhrow <simon.buhrow(a)posteo.de>
---
M flashrom.c
1 file changed, 67 insertions(+), 20 deletions(-)
git pull ssh://review.coreboot.org:29418/flashrom refs/changes/67/58467/4
--
To view, visit https://review.coreboot.org/c/flashrom/+/58467
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: flashrom
Gerrit-Branch: master
Gerrit-Change-Id: I862ce0b5f8912565e43c340578d8126aa2e6aa3b
Gerrit-Change-Number: 58467
Gerrit-PatchSet: 4
Gerrit-Owner: Simon Buhrow
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Attention: Simon Buhrow
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-MessageType: newpatchset
Attention is currently required from: Simon Buhrow, Nico Huber, Angel Pons.
Hello build bot (Jenkins), Nico Huber,
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/flashrom/+/58467
to look at the new patch set (#3).
Change subject: flashchips.c: big erase blocksize first
......................................................................
flashchips.c: big erase blocksize first
Choosing the best fitting erase block size can safe
a significant amount of runtime. Changing the order
of entries of block_erasers in flashchips.c going
from the bigger block size to lower block size does
a better job.
I am running flashrom inside a VirtualBox so the
gained time is quite big.
Setup: IS25LP064 flash + ft2232H programmer
Saved time: > 2 min for single '-E' operation
Change-Id: I862ce0b5f8912565e43c340578d8126aa2e6aa3b
Signed-off-by: Simon Buhrow <simon.buhrow(a)posteo.de>
---
M flashchips.c
M flashrom.c
2 files changed, 68 insertions(+), 21 deletions(-)
git pull ssh://review.coreboot.org:29418/flashrom refs/changes/67/58467/3
--
To view, visit https://review.coreboot.org/c/flashrom/+/58467
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: flashrom
Gerrit-Branch: master
Gerrit-Change-Id: I862ce0b5f8912565e43c340578d8126aa2e6aa3b
Gerrit-Change-Number: 58467
Gerrit-PatchSet: 3
Gerrit-Owner: Simon Buhrow
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Attention: Simon Buhrow
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-MessageType: newpatchset
Attention is currently required from: Nico Huber, Angel Pons.
Hello build bot (Jenkins), Nico Huber,
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/flashrom/+/58467
to look at the new patch set (#2).
Change subject: flashchips.c: big erase blocksize first
......................................................................
flashchips.c: big erase blocksize first
Choosing the best fitting erase block size can safe
a significant amount of runtime. Changing the order
of entries of block_erasers in flashchips.c going
from the bigger block size to lower block size does
a better job.
I am running flashrom inside a VirtualBox so the
gained time is quite big.
Setup: IS25LP064 flash + ft2232H programmer
Saved time: > 2 min for single '-E' operation
Change-Id: I862ce0b5f8912565e43c340578d8126aa2e6aa3b
Signed-off-by: Simon Buhrow <simon.buhrow(a)posteo.de>
---
M flashchips.c
M flashrom.c
2 files changed, 70 insertions(+), 23 deletions(-)
git pull ssh://review.coreboot.org:29418/flashrom refs/changes/67/58467/2
--
To view, visit https://review.coreboot.org/c/flashrom/+/58467
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: flashrom
Gerrit-Branch: master
Gerrit-Change-Id: I862ce0b5f8912565e43c340578d8126aa2e6aa3b
Gerrit-Change-Number: 58467
Gerrit-PatchSet: 2
Gerrit-Owner: Simon Buhrow
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-MessageType: newpatchset
Attention is currently required from: Nico Huber, Edward O'Callaghan, Angel Pons, Anastasia Klimchuk.
Nikolai Artemiev has posted comments on this change. ( https://review.coreboot.org/c/flashrom/+/58475 )
Change subject: [RFC] spi25_statusreg: make register read/write functions generic
......................................................................
Patch Set 6:
(1 comment)
File chipdrivers.h:
https://review.coreboot.org/c/flashrom/+/58475/comment/1bec0e70_0fb0e99c
PS6, Line 65: /* FIXME: replace spi_read_status_register() calls with spi_read_register() */
I have a separate patch for this, but it touches a lot of files so I'm leaving it out for now.
--
To view, visit https://review.coreboot.org/c/flashrom/+/58475
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: flashrom
Gerrit-Branch: master
Gerrit-Change-Id: I0a3951bbf993f2d8d830143b29d3ce16cc6901d7
Gerrit-Change-Number: 58475
Gerrit-PatchSet: 6
Gerrit-Owner: Nikolai Artemiev <nartemiev(a)google.com>
Gerrit-Reviewer: Anastasia Klimchuk <aklm(a)chromium.org>
Gerrit-Reviewer: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Reviewer: Edward O'Callaghan <quasisec(a)chromium.org>
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Paul Menzel <paulepanter(a)mailbox.org>
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Edward O'Callaghan <quasisec(a)chromium.org>
Gerrit-Attention: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Attention: Anastasia Klimchuk <aklm(a)chromium.org>
Gerrit-Comment-Date: Fri, 29 Oct 2021 05:08:48 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
Attention is currently required from: Nico Huber, Edward O'Callaghan, Angel Pons, Anastasia Klimchuk.
Nikolai Artemiev has posted comments on this change. ( https://review.coreboot.org/c/flashrom/+/58474 )
Change subject: [RFC] writeprotect, cli_classic: delete old writeprotect code
......................................................................
Patch Set 6:
(3 comments)
File cli_classic.c:
https://review.coreboot.org/c/flashrom/+/58474/comment/849a7fdb_8885f4d0
PS5, Line 778: set_wp_disable should be done before setting the range
> Or even have `set_wp_range` disable WP beforehand (bail out if it fails) and restore the WP state af […]
The comment is misleading, the only real requirement is that wp_set_range() should be called before before wp_enable() to avoid locking the status register before the desired range is selected.
However calling wp_disable() before wp_set_range() won't help, since wp_disable() will only succeed if protection is already disabled or if the WP pin is inactive, and in either case wp_set_range() would succeed anyway.
https://review.coreboot.org/c/flashrom/+/58474/comment/ec3a1c99_3d6c7f8e
PS5, Line 783: set_wp_range must happen before set_wp_enable
> Same question as previous, can set_wp_enable check that set_wp_range has been called? […]
There isn't really anything to check, though we probably should keep the comment in some form. Something like "do this last" before the wp_enable code.
File writeprotect.c:
PS3:
> The only reason I was thinking to temporarily keep struct wp, is to keep cli_classic compiling. So that _wp_ functions can be added one at a time, with implementation. At the end of the patch series there would be no struct wp, one way or the other.
> I thought this can be another approach on how to add one function at a time.
In the end I decided to delete all the old code in this commit and add things back as when they are ready. I think that will be easiest to review.
--
To view, visit https://review.coreboot.org/c/flashrom/+/58474
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: flashrom
Gerrit-Branch: master
Gerrit-Change-Id: I67e9b31f86465e5a8f7d3def637198671ee818a8
Gerrit-Change-Number: 58474
Gerrit-PatchSet: 6
Gerrit-Owner: Nikolai Artemiev <nartemiev(a)google.com>
Gerrit-Reviewer: Anastasia Klimchuk <aklm(a)chromium.org>
Gerrit-Reviewer: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Reviewer: Edward O'Callaghan <quasisec(a)chromium.org>
Gerrit-Reviewer: Nico Huber <nico.h(a)gmx.de>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Paul Menzel <paulepanter(a)mailbox.org>
Gerrit-Attention: Nico Huber <nico.h(a)gmx.de>
Gerrit-Attention: Edward O'Callaghan <quasisec(a)chromium.org>
Gerrit-Attention: Angel Pons <th3fanbus(a)gmail.com>
Gerrit-Attention: Anastasia Klimchuk <aklm(a)chromium.org>
Gerrit-Comment-Date: Fri, 29 Oct 2021 05:04:26 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Angel Pons <th3fanbus(a)gmail.com>
Comment-In-Reply-To: Anastasia Klimchuk <aklm(a)chromium.org>
Comment-In-Reply-To: Nikolai Artemiev <nartemiev(a)google.com>
Gerrit-MessageType: comment
Hello build bot (Jenkins),
I'd like you to reexamine a change. Please visit
https://review.coreboot.org/c/flashrom/+/58484
to look at the new patch set (#6).
Change subject: [RFC] writeprotect: implement wp_print_ranges()
......................................................................
[RFC] writeprotect: implement wp_print_ranges()
BUG=b:195381327,b:153800563
TEST=flashrom --wp-list
BRANCH=none
Change-Id: I82441c60c239a5b947b5a2a87b61e7bdf60bee89
Signed-off-by: Nikolai Artemiev <nartemiev(a)google.com>
---
M cli_classic.c
M writeprotect.c
M writeprotect.h
3 files changed, 52 insertions(+), 2 deletions(-)
git pull ssh://review.coreboot.org:29418/flashrom refs/changes/84/58484/6
--
To view, visit https://review.coreboot.org/c/flashrom/+/58484
To unsubscribe, or for help writing mail filters, visit https://review.coreboot.org/settings
Gerrit-Project: flashrom
Gerrit-Branch: master
Gerrit-Change-Id: I82441c60c239a5b947b5a2a87b61e7bdf60bee89
Gerrit-Change-Number: 58484
Gerrit-PatchSet: 6
Gerrit-Owner: Nikolai Artemiev <nartemiev(a)google.com>
Gerrit-Reviewer: build bot (Jenkins) <no-reply(a)coreboot.org>
Gerrit-CC: Paul Menzel <paulepanter(a)mailbox.org>
Gerrit-MessageType: newpatchset