proxmox-mirrors/fwupd
1
0
Fork 0
mirror of https://git.proxmox.com/git/fwupd synced 2025-08-07 22:57:14 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #9 from vanillajonathan/patch-3

Browse Source 
More markup
This commit is contained in:
Richard Hughes 2015-05-05 09:38:20 +01:00
commit 7504191ee9
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -110,18 +110,20 @@ ColorHug Support
You need to install colord 1.2.9 which may be newer that your distribution You need to install colord 1.2.9 which may be newer that your distribution
provides. Compile it from source https://github.com/hughsie/colord or grab the provides. Compile it from source https://github.com/hughsie/colord or grab the
RPMS here http://people.freedesktop.org/~hughsient/fedora/ RPMs here http://people.freedesktop.org/~hughsient/fedora/
If you don't want or need this functionality you can use `--disable-colorhug` If you don't want or need this functionality you can use the
`--disable-colorhug` option.
UEFI Support UEFI Support
------------ ------------
If you're wondering where to get fwupdate from, either compile it form source If you're wondering where to get `fwupdate` from, either compile it form source
(you might also need a newer efivar) from https://github.com/rhinstaller/fwupdate (you might also need a newer `efivar`) from https://github.com/rhinstaller/fwupdate
or grab the RPMs here https://pjones.fedorapeople.org/fwupdate/ or grab the RPMs here https://pjones.fedorapeople.org/fwupdate/
If you don't want or need this functionality you can use `--disable-uefi` If you don't want or need this functionality you can use the `--disable-uefi`
option.
Vendor Firmware Updates Vendor Firmware Updates
======================= =======================
@ -136,7 +138,7 @@ plugin and there would need to be interfaces available to be able to write
What do I have to do? What do I have to do?
--------------------- ---------------------
As per the [ Microsoft guidelines](https://msdn.microsoft.com/en-us/library/windows/hardware/dn917810%28v=vs.85%29.aspx), As per the [Microsoft guidelines](https://msdn.microsoft.com/en-us/library/windows/hardware/dn917810%28v=vs.85%29.aspx),
package up your firmware into a `.cab` file, with these files inside: package up your firmware into a `.cab` file, with these files inside:
* The actual `.cap` file your engineers have created * The actual `.cap` file your engineers have created
@ -210,8 +212,8 @@ If the firmware is not redistributable you have to indicate it in in the
It is then **very important** you also provide a download location in the It is then **very important** you also provide a download location in the
`.metainfo.xml` file. `.metainfo.xml` file.
Questions: Questions
---------- ---------
### Where will this data be used? ### Where will this data be used?
@ -258,7 +260,7 @@ An example commit to the ColorHug project can be found [here](https://github.com
Adding Trusted Keys Adding Trusted Keys
=================== ===================
Introduction: Introduction
------------ ------------
Installing a public key to `/etc/pki/fwupd` allows firmware signed with a Installing a public key to `/etc/pki/fwupd` allows firmware signed with a