Hi,
I'd like to tag flashrom 0.9.1 soon. Preliminary release announcement is here: http://www.coreboot.org/Flashrom/0.9.1 The release announcement will be transferred to flashrom.org at the time of release.
Patches I'd like to have in 0.9.1:
Acked with modifications, commit needed: - fix MSR code in flashrom
Ack needed: - Use correct programmer fallback functions - Improve error messages, protect the user
TODO: - Don't list programmers which weren't compiled in. This means #if inside the usage message and in a lot of other places. Makefile tweaking needed as well. - Don't error out if chipset initialization returned with a warning. - Document serprog usage in the man page. - Loads of testing.
I hope to get the pending patches listed above committed tomorrow, then tag 0.9.1-rc1 to give packagers a base to work with and test.
No new features will be merged between 0.9.1-rc1 and 0.9.1. (I do have one neat new SPI bitbang feature pending, but that one has to wait as well.) I'd rather get 0.9.1 out before the Opensuse package update deadline. That means we also make the Ubuntu Karmic deadline.
Thoughts? Comments?
Regards, Carl-Daniel
On Wed, Aug 12, 2009 at 03:13:34AM +0200, Carl-Daniel Hailfinger wrote:
Hi,
I'd like to tag flashrom 0.9.1 soon. Preliminary release announcement is here: http://www.coreboot.org/Flashrom/0.9.1 The release announcement will be transferred to flashrom.org at the time of release.
Patches I'd like to have in 0.9.1:
Acked with modifications, commit needed:
- fix MSR code in flashrom
Ack needed:
- Use correct programmer fallback functions
- Improve error messages, protect the user
TODO:
- Don't list programmers which weren't compiled in. This means #if
inside the usage message and in a lot of other places. Makefile tweaking needed as well.
- Don't error out if chipset initialization returned with a warning.
- Document serprog usage in the man page.
- Loads of testing.
I hope to get the pending patches listed above committed tomorrow, then tag 0.9.1-rc1 to give packagers a base to work with and test.
No new features will be merged between 0.9.1-rc1 and 0.9.1. (I do have one neat new SPI bitbang feature pending, but that one has to wait as well.) I'd rather get 0.9.1 out before the Opensuse package update deadline. That means we also make the Ubuntu Karmic deadline.
Thoughts? Comments?
Regards, Carl-Daniel
What about board enables, do they always go in, even after rc?
My view on this is that they have no impact on other-than-the-matched boards, and therefor are very safe last minute changes.
Luc Verhaegen.
On 12.08.2009 10:33, Luc Verhaegen wrote:
On Wed, Aug 12, 2009 at 03:13:34AM +0200, Carl-Daniel Hailfinger wrote:
I hope to get the pending patches listed above committed tomorrow, then tag 0.9.1-rc1 to give packagers a base to work with and test.
No new features will be merged between 0.9.1-rc1 and 0.9.1.
What about board enables, do they always go in, even after rc?
My view on this is that they have no impact on other-than-the-matched boards, and therefor are very safe last minute changes.
I'd say they count as bug fixes as long as they don't rewrite any other board enables.
Regards, Carl-Daniel
Hi,
here's the updated status for 0.9.1.
Commit needed: - Board enable for Asus P4P800-E Deluxe
Ack needed: - Only list available programmers in usage() - Improve error messages, protect the user v2
TODO: - Don't error out if chipset initialization returned with a warning. - Document serprog usage in the man page. - Loads of testing.
Not sure: - Fix another SB600 SPI corner case
Regards, Carl-Daniel
-
Carl-Daniel Hailfinger -
Luc Verhaegen