Documentation: Difference between revisions
m (Created page with '= Useful information = == Open development == We welcome contributions from every human being, corporate entity or club. If you want to contribute patches or test reports, ple…') |
(→Using flashrom: Add links to WP documentation and fix link to man page source) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
= Using flashrom = | |||
See the [https://review.coreboot.org/plugins/gitiles/flashrom/+/refs/heads/master/flashrom.8.tmpl flashrom manual (<code>man flashrom</code>)] for general information on how to use flashrom. Selected topics are also covered in more detail below. | |||
=== Using write-protection feature === | |||
* [[Firmware updates vs. SPI write-protection]] | |||
* [[Example of partial write-protection]] | |||
= Useful information = | = Useful information = | ||
| Line 5: | Line 14: | ||
We welcome contributions from every human being, corporate entity or club. | We welcome contributions from every human being, corporate entity or club. | ||
If you want to contribute patches or test reports, please send them to our flashrom [[ | If you want to contribute patches or test reports, please send them to our flashrom [[Contact#Mailing_List|mailing list]]. For one-off test reports, you don't have to subscribe, but if you want to contribute patches, we strongly recommend you subscribe to our mailing list to make communication easier. | ||
Flashrom development is volunteer-driven, and our developers tackle the features they're interested in. Most developers have pretty long personal TODO lists, so if you want to suggest a feature, please make sure you have all the datasheets and/or programming guides needed for that feature (preferably without NDA). For testing, our developers usually need physical access to the hardware in question. It also helps to be friendly to the developers. | Flashrom development is volunteer-driven, and our developers tackle the features they're interested in. Most developers have pretty long personal TODO lists, so if you want to suggest a feature, please make sure you have all the datasheets and/or programming guides needed for that feature (preferably without NDA). For testing, our developers usually need physical access to the hardware in question. It also helps to be friendly to the developers. | ||
| Line 15: | Line 24: | ||
== Donations == | == Donations == | ||
See [[Donations]]. | |||
Latest revision as of 15:52, 4 November 2022
Using flashrom
See the flashrom manual (man flashrom) for general information on how to use flashrom. Selected topics are also covered in more detail below.
Using write-protection feature
Useful information
Open development
We welcome contributions from every human being, corporate entity or club.
If you want to contribute patches or test reports, please send them to our flashrom mailing list. For one-off test reports, you don't have to subscribe, but if you want to contribute patches, we strongly recommend you subscribe to our mailing list to make communication easier.
Flashrom development is volunteer-driven, and our developers tackle the features they're interested in. Most developers have pretty long personal TODO lists, so if you want to suggest a feature, please make sure you have all the datasheets and/or programming guides needed for that feature (preferably without NDA). For testing, our developers usually need physical access to the hardware in question. It also helps to be friendly to the developers.
Paid support/development
Some companies and individual developers offer paid flashrom support and development if you desire a particular feature nobody is working on.
Donations
See Donations.