t; try to fix the situation now, in the year 2024.
>
> Victor, maybe you know, is it possible to find datasheets for
> GD25LR256E and GD251R512ME? I could finish the old patch and get chips
> into the tree.
>
> This is a separate question to Avinash's issue with internal
> progr
Brian, thank you for your work! The patch is submitted.
> Honestly, I don't know how to move forward on assertions about
> "know[ing] for sure whether this delay is no longer needed". We have
> no actionable information about the original problem, so we can never
> be sure.
I have been thinking
with internal
programmer, but for this we need the very verbose log (which is log
with -VVV option on command line).
Thank you!
On Thu, May 9, 2024 at 11:03 PM Anastasia Klimchuk wrote:
>
> Avinash, I read the thread and I see you are saying "I am attaching
> the log here" but I don't
Avinash, I read the thread and I see you are saying "I am attaching
the log here" but I don't see the log? maybe you can re-send it again,
now with the mailing list? (perhaps you sent it to Victor only?)
Yes it is also important to know your board, since you are saying the
chip worked successfully
arely used nowadays. I want to
discuss, but as a topic by itself.
I don't think we need to resolve all of the problems in one patch :)
On Fri, Apr 26, 2024 at 8:54 AM Brian Norris wrote:
>
> Hi Angel,
>
> On Thu, Apr 25, 2024 at 11:44:47AM +, Angel Pons wrote:
> > On Thu, Apr 25
Angel, great to see you here again! Also, you provided very useful information.
> Did you conside making it so that only SPI programmers / flash chips
> skip the delay? The SPI bus' strict timing leaves no room for this
> problem to occur, so it should be safe to skip this delay. And this
> would
t; remote: SUCCESS
> remote:
> remote: https://review.coreboot.org/c/flashrom/+/81970 :
> adding a few new SPI NOR part numbers [NEW]
> remote:
> To https://review.coreboot.org/flashrom
> * [new reference] HEAD -> refs/for/main
>
>
>
28E: 3V 128Mbit
> GD25R128E: 3V 128Mbit RPMC
> GD25B256E: 3V 256Mbit QE = 1
> GD25Q256E: 3V 256Mbit
> GD25R256E: 3V 256Mbit RPMC
> GD25B512MF: 3V 512Mbit QE = 1
> GD25R512MF: 3V 512Mbit RPMC
> GD25F64F: 3V 64Mbit
> GD25F128F: 3V 128Mbit
patch?
>
> Files I have modified are Flashchip.c and .h.
>
> Regards,
>
> Victor
>
> ____
> From: Anastasia Klimchuk
> Sent: Friday, April 12, 2024 02:25
> To: Vlim ; Nikolai Artemiev ;
> flashrom@flashrom.org ; Peter Marheine
>
>
gt; Erase/write done from 0 to 7f
> Write Failed!Uh oh. Erase/write failed. Checking if anything has changed.
> Reading current flash chip contents...
> cb_out: error: LIBUSB_TRANSFER_TIMED_OUT
>
> cb_in: error: LIBUSB_TRANSFER_TIMED_OUT
>
> cb_in: error: LIBUSB_TRANSFE
h the datasheet?
>
> Regards,
>
> Victor
>
>
>
> From: Vlim
> Sent: Friday, April 5, 2024 20:37
> To: Nikolai Artemiev ; Anastasia Klimchuk
>
> Cc: flashrom@flashrom.org ; Peter Marheine
>
> Subject: Re: [flashrom] Re: ad
Hello,
> I checked the MXIC comparison of these chips and they are very similar.
> The main difference with the 35E is the physical pinout is different.
Do you mean you compared the datasheets?
I suspect that multi-chip definition
MX25L12835F/MX25L12845E/MX25L12865E (which at head already grew
> do you want to keep around such legacy code
> (increasing the maintenance load) in the codebase forever?
No I don't want to keep such code forever to maintain, mainly because
it won't be needed forever.
But dropping support for DOS will be a separate effort (with dedicated
threads and
Hello Sol,
If you have time and energy, you can try and add the support yourself.
Do you have the chip to test it?
There are two relevant docs on the topic:
Dev guide https://www.flashrom.org/dev_guide/development_guide.html
and how to add chip
Sol, thank you for reporting. I created a patch to mark the chip as
tested https://review.coreboot.org/c/flashrom/+/78069
--
Anastasia.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org
# 14th September 2023, 6.00-7.00am UTC+0
Attendees: Stefan, Anastasia
## Decision summary
* Renaming flashrom branch from "master" to "main" in the very near
future. All patches in Gerrit will be converted with the script.
## Agenda
* [Stefan] Renaming flashrom branch from "master" to "main"
# 31th August 2023, 6.00-7.00am UTC+0
Attendees: Stefan, Alex, Anastasia
## Decision summary
* not much
## Agenda
* Who is using libpayload, which state it is in, how to test it before release?
* write a post to the mailing list
* see how it goes. if no one responds, can we at least
Ryne, do you have logs by any chance? From two different times you ran
flashrom and got different ids?
You can attach or you can use paste.flashrom.org
Thank you!
On Thu, Aug 24, 2023 at 1:53 PM Ryne Everett wrote:
>
> Hello group,
>
> I'm attempting to flash a W25Q64FW with a CH341A. Despite
Hello everyone,
An announcement to everyone who is doing (or planning to do) any
flashrom development.
Since today, we are enabling the feature in Gerrit which blocks patch
submit until all comments are resolved. You can see it in Gerrit if
you open any patch, in the top-left section,
# 17th August 2023, 6.00-7.00am UTC+0
Attendees: Joursoir, Stefan, Anastasia
## Decision summary
* logo files will be copied from flashrom-media to flashrom repo (into
doc/ to display on website)
* enable Gerrit feature to not submit with unresolved comments
## Agenda
* [aklm] is it okay to
Hi Johnny,
Question marks mean that the operation in that column is untested for
this chip, untested on hardware. Usually it happens when chip
definition is added based on datasheets information, but without
testing on hw. Later if someone runs operations on the chip
successfully, the chip can be
Hi Johnny,
Good that you reached out. Indeed we are in the process of moving
documentation to the new website, so the links have changed. Old
website is available at wiki.flashrom.org address.
In your case, for overall dev guides, new link is:
# 3th August 2023, 6.00-7.00am UTC+0
Attendees: Stefan, Carl-Daniel, Anastasia
## Decision summary
* 3 developers get submit rights: Joursoir (Alexander Goncharov),
Peter Marheine, Nikolai Artemiev
* document the process of getting commit rights and send for review (todo aklm)
## Agenda
*
Hello,
Redirect was on the plan, let me check about it.
Emergency help message: can you send a patch? That would be great!
--
Anastasia.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org
Good Day,
> We have the friendliness document
> which serves as a sort of Code of Conduct.
It does not serve though.
Code of conduct is meant to protect members of the community from
unacceptable behavior, and Friendliness failed to do that.
Friendliness doc definitely has lots of potential and
I see. I think commit message to the patch gives an answer to your
question, I will copy commit message here just in case you maybe
missed it:
> For now link to coreboot's one, in the absence of our own.
It is always possible to create our own later, if desired,
but meanwhile we can share code of
Carl-Daniel,
Thank you so much for your message! I know you don't post to the
mailing list often, I appreciate you took the time to do this!
Of course I want flashrom to be a safe place for everyone. And
everyone else wants this too!
You are very welcome to send a patch to convert the
Update: this is now live!
https://www.flashrom.org/dev_guide/development_guide.html
--
Anastasia.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org
And now,
New website is live!
Thanks heaps to Thomas, Stefan, Patrick, Peter, Joursoir, me, and
everyone else who did code reviews and supported the effort in any
other way! <3
flashrom.org is the new website
wiki.flashrom.org is officially the old one, and it is already locked
for editing
# 20th July 2023, 6.00-7.00am UTC+0
Attendees: Stefan, Edward, Anastasia
## Decision summary
* flashrom.org is new, wiki.flashrom.org is old (will be a dedicated
post on the ML)
## Agenda
* New website: let's do it right now!
* Done: flashrom.org is new, wiki.flashrom.org is old, and old
# 22th June 2023, 6.00-7.00am UTC+0
Attendees: Stefan, Edward, Anastasia
## Decision summary
* More documentation coming soon, patches will be sent for review (see below)
## Agenda
* License for docs, do we just create a page with license text like
coreboot?
Update: this has progressed into a patch under review
https://review.coreboot.org/c/flashrom/+/75906
--
Anastasia.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org
Hello, thank you for the patch!
There is currently a patch under review adding the same chip:
https://review.coreboot.org/c/flashrom/+/68557
Do you have a Gerrit account? If yes, you can add yourself to the
patch and watch the progress. If not, just check the link.
I see your patch has more, so
Leonard,
Thank you so much for your ideas and patches! Will have a look at these.
As for signing off the patches, we recently updated the policy (in the
same way as Linux did) so now it doesn't have to be a real real name.
However it still needs to be a known identity, for example if everyone
I really like how we collectively debugged the issue and identified
the root cause, even without Alex responding. This is so cool, thanks
everyone! <3
Alex,
Yes it's true that makefile will be deleted soon, probably later this
year. It's a very good time to switch to meson, and please complain
Hi Alex,
This is definitely not intended behaviour: sphinx is optional. If it
is not present, flashrom can be built, just without docs.
I didn't have sphinx locally for a while, and was building the sources
without it. Only installed it very recently, because I started to add
docs.
Can you tell
# 22th March 2023, 21:00 - 22:00 UTC+0
Attendees: Thomas, Stefan, Edward, Prakhar, Anastasia
## Decision summary
* We need to update Signed-off-by guidelines , like Linux kernel did
recently: strict real names not required to sign-off, can be a
preferred known nickname (but not anonymous). DONE
Hello everyone,
Just a reminder that from April and until September flashrom meetings
move to Thursday 6.00-7.00am UTC+0
Next one is 13th April 6.00-7.00am UTC+0, and then every two weeks as usual.
More details here https://www.flashrom.org/Contact#Dev_meeting
--
Anastasia.
Thank you! I just checked, the chip marked tested on head, so it
should go to the next release. Good to have confirmation that it
works!
--
Anastasia.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to
Adam, thank you!
I looked at your logs, it seems like you are running not the latest
version (1.2 in the logs vs 1.3 is the latest). In the latest version,
this chip is marked as tested.
But thank you anyway! :)
--
Anastasia.
___
flashrom mailing list
# 8th March 2023, 21:00 - 22:00 UTC+0
Attendees: Thomas, Prakhar, Anastasia
## Decision summary
* We will be using CreativeCommons license for documentation, CC-BY-4.0
* 26th April on this meeting will be a “development guidelines
brainstorming session”. Everyone with ideas on how to improve
Good Day flashrom,
We had an important decision about flashrom release schedule recently,
and it went to the mailing list as a part of dev meeting notes
(22.02.2023). However, the topic is big enough to have a dedicated
thread on the mailing list.
We decided to make releases twice a year: one in
I have created a patch for this chip:
https://review.coreboot.org/c/flashrom/+/73429
Alex, do you have logs from that successful write that you did?
And also, I still think it would be a good idea to create a gerrit
account, to be able to send or review a patch one day! ;)
--
Anastasia.
Alex, thank you so much for the report!
I have a question for you: do you think you can send a patch to
flashrom, to mark AM29LV040B as write-tested? That would be so great!
--
Anastasia.
___
flashrom mailing list -- flashrom@flashrom.org
To
Thomas this is fantastic, thank you so much! Sorry that it took me so
long to respond.
And that it can help with migrating and upgrading the
homepage/website, make it even better!
--
Anastasia.
___
flashrom mailing list -- flashrom@flashrom.org
To
# 22th February 2023, 21:00 - 22:00 UTC+0
Attendees: Thomas, Stefan, Prakhar, Anastasia
## Decision summary
* New flashrom home page generated with sphinx coming soon. And then
we eventually move relevant content from wiki and deprecate wiki.
Details below in notes.
* We will have two release
Apologies for the delay, these are notes from two weeks ago.
# 8th February 2023, 21:00 - 22:00 UTC+0
Attendees: Thomas, Stefan, Prakhar, Anastasia
## Decision summary
* Few upgrades for Easy Projects page (TODO aklm)
## Agenda
* [aklm] Easy Projects page needs some love.
* How about
Good Day flashrom community,
flashrom release v1.3.0 is out!
Tag name: v1.3.0
Branch name: 1.3.x
Tarball: download.flashrom.org/releases/flashrom-v1.3.0.tar.bz2
Signature: download.flashrom.org/releases/flashrom-v1.3.0.tar.bz2.asc
Fingerprint: 6E6E F9A0 BA47 8006 E277 6E4C C037 BB41 3134 D111
# 25th January 2023, 21:00 - 22:00 UTC+0
Attendees: Thomas, Stefan, Prakhar, Nico, Edward, Anastasia
## Decision summary
* Flashrom is not applying as a mentorship organisation for gsoc 2023
(no capacity to do all admin work, tight timelines). Independent
contributors (outside of scope of gsoc)
Hello flashrom community,
Second release candidate v1.3.0-rc2 (and likely the final one) has
been tagged. It includes the fix for int-to-pointer-cast warnings for
32-bit Linux.
Let's start the countdown until the end of January, and if no
emergency happens, we will cut the release.
I am copying
Branden, I made a patch with that:
https://review.coreboot.org/c/flashrom/+/72038
If you could have a look and say whether this is what you have tested?
If you have an account in Gerrit you can approve the patch, if not you
can just reply here.
Would you like to be added as Tested-By tag? That
Very good news, thank you for the update!
Would you agree to send a patch to Gerrit? Have you used Gerrit before?
I think you are the best person to send a patch, because you have the
environment, and you did the actual testing.
As a plan B I could send a patch and add you as Tested-By , and a
Hello Branden,
First of all, thanks heaps for testing v1.3.0-rc1 and posting on the list!
I looked at the logs, it seems you have this issue which was
discovered some time earlier: https://ticket.coreboot.org/issues/407
The issue has been reported on the #flashrom irc channel, and
potential
The initial list of tickets for the release was created from Nico’s
list of issues to check before the release. (see earlier thread about
the release). Some of these are bugs, some others were in the form
“what do we do with this?”. I understand that since a few months ago
things could have
Nico what was the goal why you started this thread?
I thought for a moment, you have a *quick* question. So I answered.
Now you seem to be unhappy to learn that we are closer to the release
than 1/2 yr ago.
You are saying "But I don't believe you", what was the point of asking then?
--
Hello,
A quick answer first:
We are closer to the release, and the state of the master is better
than a half year ago.
More details.
In general, the progress is visible here https://ticket.coreboot.org/issues/353
There is one issue that came up around May
https://ticket.coreboot.org/issues/390
Hello Sergii,
To the question whether the documentation is useful: IMO Yes, I 100%
think it is useful. I did a quick read through the links.
Where to put it, this is an interesting question.
The advantage of Documentation/ directory in the repository is that it
allows other people (anyone who
Hello Prakhar,
Thank you for your introduction!
> I am new to the open source world and I will be trying for GSOC'23.
For the program year 2022 (which is wrapping up already) we made a
page with guidelines for contributors: https://www.flashrom.org/GSoC
Most of the information is still
Okay looks like people either fine or don't care (no one is against),
so non-negative response.
Let's move to 23 Sept then. I will modify the event, so that will be
an email generated with "Updated invitation".
Thanks everyone!
--
Anastasia.
___
Hello,
The next dev meeting is scheduled for 22 Sept, but it turns out there
are some things happening:
1) This is a day right after OSFC which many people are attending.
Joining a meeting early in the morning right after the last day of
conference, from a hotel room, is not ideal.
2) All of a
Hi Dhiren,
> the idea about bash auto completion sounds interesting to me and I would like
> to work on it
Awesome! You are in :)
> Do you recommend to first play more with flashrom and then work on this
> feature?
Yes, I recommend to do few small things first. For example, this is
one more
Hello Dhiren, and welcome!
I know you got lots of advice on the irc channel (which is great), I
wanted to add a few more things to that.
> I'm not a student anymore I cannot do it as part of GSOC, but I have done
> open source contribution since 2 years
That "student" requirement has been
Hello People,
We just got a flashrom’s own MAINTAINERS file! I wanted to share the
news with everyone.
https://github.com/flashrom/flashrom/blob/master/MAINTAINERS
There is a script which will automatically add people as reviewers to
the patch, if the patch is touching the files/area they are
Hello! Good to know the chip is working, If you can send logs that
would be great! Thank you.
On Sat, Jul 9, 2022 at 2:56 AM Tygert Baggins wrote:
>
> Hello,
> I builded flashrom from source (2022-07-02) on Odroid C4 board (raspberry
> clone) and tested flash chip FM25F01, everything was
# 30th June 2022, 6:00 - 7:00 UTC+0
Attendees: Edward, Thomas, Stefan, Nikolai, Anastasia, Felix
## Decisions Summary
* Raiden_debug_spi: Thomas will do a review of this programmer and add
comments to the bug
[https://ticket.coreboot.org/issues/358](https://ticket.coreboot.org/issues/358)
* As
Hello Eduardo,
This feature is super recent, so if you are using v1.2 then it's not
there. You can, if you want, build flashrom from the latest code and
you will see progress if you add `--progress` to the command line.
But, a fair warning: building from the latest code means you get
*everything
Thanks for your thoughts!
> one important point is the scope I guess, i.e. when to apply this
> process. There are certainly things that we could call a "big
> decision". The upcoming flashrom-reviewers group for Gerrit comes
> to mind, for instance. However, for many smaller decisions the
>
Hello People,
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
Hello Daniel, Nico,
I noticed this:
> I think it would
> be best to have somebody have a thorough look through all the changes.
> Preferably somebody who didn't work on the patch because it's not easy
> to spot one's own errors.
Looking at the patch, it seems like almost everyone already worked
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
Hello,
I wanted to add two more FAQs here.
#5 Do I need to create an account anywhere?
No, you can join without an account.
Also you can view and comment on the meeting doc without an account.
#6 How do I add a topic to the agenda?
Add comments/suggestions on the meeting doc, and they will be
Thanks so much for your thoughts everyone!
I have important information for this thread. Next flashrom dev
meeting which is this Thursday (in two days), specifically:
19th May 2022, 6:00 - 7:00 am UTC+0
will be discussing flashrom release!
There are two parts in the topic: next release v1.3 and
Hi Aarya,
Things are going well, we (Org Admins) have submitted all the
"paperwork" for the projects and are now waiting for the official
announcement!
Nico is absolutely correct, announcement will be on May 20. We are
waiting for it as much as you ;)
--
Anastasia.
Hello,
I am also not a native English speaker, and need to always concentrate
on the language. Sometimes I can't understand the person who has just
spoken, in this case I am trying to clarify for example by asking "do
I understand you correctly, do you mean ABCXYZ?". Also I remember a
few times
Hello Everyone,
First of all let's summarize what has happened. Today is May 12.
Two months ago (Mar 6) Nico started this thread on the mailing list:
"Gatekeeping, ACLs and Review Rules". I recommend everyone [who is
interested] re-read the opening email in this thread. It is well
written,
of the group (as it is suggested in the starter email)
is a copy of “flashrom developers”, and then we can add people on the
top.
Thank you!
Given the existing "flashrom developers" , maybe a new group can be
called "flashrom reviewers"?
On Sat, Mar 26, 2022 at 9:11 PM Anast
I have great news: I created items for the release in our bugtracker!
Here is a parent issue “Release v1.3” https://ticket.coreboot.org/issues/353
and it has 23 subtasks. The subtasks are the items from the original
starter email. Thank you so much Nico for going through the long history
and
Hello People,
Few weeks ago at the flashrom meeting we had a discussion about code
reviews and the situations that sometimes happen. We decided that it
would be good to have some guidelines… and then we decided that I will
start writing something. I have been thinking about it since then. I
even
Hello People,
I wanted to summarise the information on the time of Dev meeting. At some
point there was an idea to alternate times, but then we discovered that we
got really lucky and there is one time which everyone agrees on. That was
an open question at the last meeting, to confirm the time
Aarya,
This is amazing news, I am super happy to get your project proposal!
It is nice to have you with us :)
We have long public holidays here (in AU), but I had a quick look and
the proposal looks fine.
Once the holidays are over, we, together with mentor(s), will go
through the proposal
g.
> Eventually, are we not going to remove shutdown() func from the struct
> spi_master and move it in struct programmer_entry? Will we keep shutdown()
> in the struct spi_master and not in the struct programmer_entry for SPI
> programmers?
>
> --
> Joursoir
>
> On Sat, 9 A
Hi Joursoir,
Sorry for some delay, I wanted to respond more to the topic and
finally found time :)
> As I understood, they use the following approaches:
>
> 1. Register a callback by its own
>
> if (register_shutdown(serprog_shutdown, NULL))
> goto init_err_cleanup_exit;
>
> 2. Fill `struct
the following time work for you between Apr and Sept?
Thursday 6.00-7.00 am UTC+0
which is
Wednesday 11pm-Midnight Pacific Time UTC-7
Thursday Midnight-1am Mountain Time UTC-6
Thank you!
On Wed, Apr 6, 2022 at 9:30 AM Anastasia Klimchuk wrote:
>
> ATTENTION ATTENTION
>
> We are lock
Hi Sayed,
You should start by reading our guidelines here: https://www.flashrom.org/GSoC
On Thu, Apr 7, 2022 at 3:22 AM Sayed Mohsen wrote:
>
> I also need to know if am I late for joining or its good time for me to join
> Thank you
>
> On Wed, Apr 6, 2022 at 5:59 PM Sayed wrote:
>>
>> Hello
Hi Wynn,
Nice to have you interested in Flashrom! Yes of course we are
interested in applicants for 2022, it is the good time now: the
application window has just opened a few days ago.
> As many of the projects require programmers, flash chips, and hardware, I was
> wondering to what extent I
is optimised for EU/US. However, if you are in the US and you are okay
with this time (start between 11pm and 2am) you are welcome to join of
course!
Thank you everyone.
On Mon, Apr 4, 2022 at 8:25 PM Anastasia Klimchuk wrote:
>
> Hello People,
>
> I wanted to say that
Hello People,
I wanted to say that the meeting will be happening this week! If you
have any preferences for days/times, please vote on the poll, it is
not too late.
At the moment there are 3 slots on Thursday that look good, and if
there are no other votes we will pick one of them (that would be
Hi Prakhar,
It is nice to know that you are interested in Flashrom. However, by
the nature of our projects students need to have a deep level of
knowledge and experience in C language. I would encourage you to learn
more C, and maybe find out the answers to your questions by yourself.
Good Luck!
Hello Israa,
Thank you for contacting us! Unfortunately, "Modernize the flashrom
website" project is not available for GSoC 2022 anymore. I really
apologize for the inconvenience, and confusion.
The reason is, we had some discussion recently about the project and
realised that the project is not
I realised one thing that I need to answer:
> I have completed a rough draft for my proposal, can someone review it?
So just to be very very clear: the answer is no, we won't be
pre-reviewing your proposal(s). You will submit them to the gsoc
website, they will go through the system and then
I can add a few bits from me.
You can only do one project as gsoc, because the rules say so:
https://summerofcode.withgoogle.com/rules
See 7.3.b
The rules also say that you can submit up to 3 proposals, but only one
of them we can select. In theory, you can write 2 proposals for 2
projects that
t time the patch was reviewed
Last time patch was send to review
Last time patch was merged
How long active on the project
Any topics on the mailing list
Reachable via email or channel
…..
On Fri, Mar 18, 2022 at 2:44 AM Nico Huber wrote:
>
> Hi Anastasia,
>
> On 17.03.22 12:32, Anastasi
Hi Aarya,
I fully agree with Simon, you are doing great!
I have just submitted the first one out of your patches, congrats! Well
done :)
Few more of them seem to be almost ready, just some comments about commit
messages need to be resolved.
Don't be surprised that you are getting so many
gt; Thanks for your reply and suggestions.
>
>
>
> >You can do one of "Fix scan-build issues".
>
>
>
> In the description of this task, it said, “Run scan-build in the tree.” I
> am a little confused about the words “in the tree.” How can I find it?
>
>
>
> Reg
tps://docs.google.com/document/d/18qKvEbfPszjsJJGJhwi8kRVDUG3GZkADzQSH6WFsKqw/edit?usp=sharing>
document.
On Wed, Mar 9, 2022 at 10:08 AM Anastasia Klimchuk
wrote:
> Reminder: this is happening tomorrow! 9th March 21.00-22.00 UTC+0
> Meeting id is added to meeting notes
> <https://docs.goo
.”
Thanks Martin! There is a patch currently for man page:
https://review.coreboot.org/c/flashrom/+/62768
But did you mean more than that?
On Fri, Mar 18, 2022 at 2:56 AM Nico Huber wrote:
> On 13.03.22 16:28, Nico Huber wrote:
> > On 13.03.22 08:28, Anastasia Klimchuk wrote:
> >>&
Thanks Nikolai! Since there was no feedback, I updated the page :)
On Tue, Mar 15, 2022 at 5:24 PM Nikolai Artemiev
wrote:
> Hi everyone!
>
> As a follow up to https://review.coreboot.org/c/flashrom/+/58477 and
> https://review.coreboot.org/c/flashrom/+/58480, I want to update
> the section
Hello Joursoir,
Nice to have you very interested in flashrom!
One thing I wanted to say: it would be great to include the mailing list if
you have discussions about the project. That would mean the community can
join and potentially help too, and this is really useful.
Thomas, thank you so much
“For example, the flashrom project doesn't require that all comments
be resolved before merge. That can be enabled if you'd like, but currently
it
isn't.”
Oh this explains! I was wondering where those “patches merged with
unresolved comments” are coming from. I am 100% voting for this setting to
Hi Karani,
The place to start is this page: https://www.flashrom.org/GSoC
Read all the information, click all the links and read them too. And then
you can start setting up your local dev environment.
On Mon, Mar 14, 2022 at 10:04 AM Karani Vinay Kumar <
karani.vinaykum...@gmail.com> wrote:
>
1 - 100 of 126 matches
Mail list logo
