Today I had a meeting with my mentors Felix and Anastasia.
The project plan has been broken into phases.
I'll work on the first phase, which will entail creating an
alternative to extract_programmer_param() that will parse the
programmer's sub-arguments according to the data type in which they
have to be utilized in the code.
So, I'll be reading through the code and working out a solution for
this task, as well as analyzing all of the other parameters that the
The topic initially came up in the “Gatekeeping” thread. However it
was suggested that it should be a separate thread, which makes sense
so I am starting one.
So, straight to the point: it looks like we have a decision making
process emerging! (below).
What do people think about it?
Discuss things on the mailing list first. It could be ongoing for
months - so that everyone who is interested has time to read and
respond. However, it doesn’t have to be for months.
When/if the discussion seems to be settled and people are in
agreement, the item can be added to the agenda of the meeting.
At the meeting the item can be discussed again, and a decision can be
made (or not made, if people disagree).
After the meeting we send an email with meeting notes and “Decisions
summary” on the top of the email.
Since stuff never gets done immediately, there always be some time to
react on #4
If someone has objections/concerns, it would be great if you can
propose improvements or alternative solutions. Please don’t just say
“this is all wrong!”
Many thanks for sharing your thoughts!
I decided to take a look at https://ticket.coreboot.org/issues/372 and I
would like to get a better understanding of what is being requested on the
issue tracker. I took a look at the submitted patch (comments and code
diff) and everything seems in order to me.
I appreciate any assistance you can provide,
Today I had my first meet with my mentors Thomas and Simon, and we
discussed a few things involving the timeline and initial tasks for the
There are mainly two parts to the project :
1. Developing a strategy to optimize the selection of the erase function to
reduce the overall time required to do the operation
2. Filtering out the erase functions that the programmer does not support
For now, I'm working on the first one. Also, I will be writing a test case
to check whether the erase functions in the flashchips struct are sorted
according to the block size.
I have a Spansion chip I want to read but it seems not supported by
flashrom. I can connect and read JEDEC ID with BusPirate: it says
01-60-18 which corresponds with the Spansion S25FL128L (specs available
online). Flashrom does not detect it. I tried reading it while forcing
any of the other 128Mbit Spansion chips, but could not make anything of
the rom with Binwalk.
What would be the best strategy to get to the contents of this chip?
Thanks in advance,
for a while now, we have some functions in the libflashrom API to query
information about supported devices and such. The original patch left
some questions open. And, alas, as there was some broken code and no
feedback, parts of it were dropped.
So, I wonder if there are any users of this API already? Anything that
might break if we change it?
Why I'm picking this up is that there are some issues with the design.
For instance, the exposed structs form an ABI that might need versioning
if somebody wants to link a shared library. And the cleanup part of the
API is too simple, i.e. flashrom_data_free() doesn't allow anything but
a shallow free().
There's also an associated ticket.
I am very proud because I have great news: we have 3 students joining
the flashrom community to do projects!
Aarya will be doing a GSoC project “Optimize Erase-Function Selection”
with Thomas (Mentor), Simon (backup Mentor) and Nikolai.
Chinmay will be doing a GSoC project “Refactor arguments parser” with
Felix (Mentor), Anastasia (backup Mentor) and Evan.
Joursoir is joining as an independent contributor and will be working
on a project “Restructure shutdown functions and remove global state”
with me and Thomas. This will be a more open-ended project and largely
a continuation of the effort I was doing last year.
Anyone who is also interested in supporting the projects and our
students, yes please, you are very welcome! :)
Aarya, Chinmay, Joursoir,
it would be really great if you can join the next flashrom dev meeting
on 2nd June, so that we can say hello to each other! Info in this
Between today and 2nd June you will be talking to your Mentors and
discussing project plans in more detail. Please prepare: look at the
timeline (https://developers.google.com/open-source/gsoc/timeline) and
tell if you plan for example vacations so that we can adjust the
You will have a conversation with your Mentor(s) once a week. You will
need to post to the mailing list at least once a week, to share with
the community what’s going on your project.
Remember if you have any questions, you can always ask your Mentor(s)
and/or me or Felix. Especially if you are confused, not sure what to
do: keep calm and talk to your Mentor(s) or Admin(s).
So, what to do now? Celebrate! ;)
And then prepare for next week's conversation with your Mentors.