aboutsummaryrefslogtreecommitdiff
path: root/www
diff options
context:
space:
mode:
Diffstat (limited to 'www')
-rw-r--r--www/conduct.md18
-rw-r--r--www/download.md16
-rw-r--r--www/faq.md83
-rw-r--r--www/index.md9
-rw-r--r--www/management.md13
-rw-r--r--www/news/MANIFEST1
-rw-r--r--www/news/libreplanet2018-workshop.md99
7 files changed, 194 insertions, 45 deletions
diff --git a/www/conduct.md b/www/conduct.md
index 313321c0..69dc0ae8 100644
--- a/www/conduct.md
+++ b/www/conduct.md
@@ -82,22 +82,20 @@ Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting one of the moderators privately via IRC private message
(see list below):
-* Andrew Robbins: **and\_who** on Freenode, email <mailto:andrew@libreboot.org>
-* Jason Self: **jxself** on Freenode
-* Leah Rowe: **\_4of7** on Freenode, email <mailto:leah@libreboot.org>
+* Andrew Robbins: **and\_who** on Freenode, email
+ [andrew@libreboot.org](mailto:andrew@libreboot.org)
+* Leah Rowe: **unoccupied** on Freenode, email
+ [leah@libreboot.org](mailto:leah@libreboot.org)
* Paul Kocialkowski: **paulk-X** Freenode (X is variable, for this
- person, email <mailto:paul@libreboot.org>
+ person, email [paul@libreboot.org](mailto:paul@libreboot.org)
check in the channel)
-* Swift Geek: **swiftgeek** on Freenode, email <mailto:swiftgeek@libreboot.org>
+* Swift Geek: **swiftgeek** on Freenode, email
+ [swiftgeek@libreboot.org](mailto:swiftgeek@libreboot.org)
If the complaint is for abuses on the Libreboot subreddit at
[r/libreboot](https://www.reddit.com/r/libreboot/) then there are a separate
group of moderators whom you can contact, via private message on the Reddit
-website:
-
-* hexacat
-* pizzaiolo\_
-* libreleah
+website. The subreddit has a public list of moderators on it.
If you deviate from these guidelines, make sure that it is with good reason.
Treatment of each case will be handled pragmatically, on a case-by-case basis.
diff --git a/www/download.md b/www/download.md
index f88b20af..4b24ec81 100644
--- a/www/download.md
+++ b/www/download.md
@@ -17,7 +17,9 @@ GPG signing key
Releases are signed with GPG.
- $ gpg --recv-keys 0x05E8C5B2
+ gpg --recv-keys 0x969A979505E8C5B2
+
+Full key fingerprint: CDC9 CAE3 2CB4 B7FC 84FD C804 969A 9795 05E8 C5B2
The GPG key can also be downloaded with this exported dump of the
pubkey: [lbkey.asc](lbkey.asc).
@@ -49,10 +51,10 @@ Project, USA)
<https://elgrande74.net/libreboot/> (elgrande74.net, France)
-<https://nephelai.zanity.net/mirror/libreboot/> (zanity.net, New Zealand)
-
<https://mirror.koddos.net/libreboot/> (koddos.net, Netherlands)
+<https://mirror.swordarmor.fr/libreboot/> (swordarmor.fr, France)
+
RSYNC mirrors {#rsync}
-------------
@@ -67,8 +69,6 @@ UK)
<rsync://ftp.linux.ro/libreboot/> (linux.ro, Romania)
-<rsync://libreboot.mirror.si/libreboot/>
-
<rsync://mirror.koddos.net/libreboot/> (koddos.net, Netherlands)
Are you running a mirror? Contact the libreboot project, and the link will be
@@ -89,10 +89,6 @@ if using HTTPS.
<http://mirror.helium.in-berlin.de/libreboot/> (in-berlin.de, Germany)
-<http://libreboot.mirror.si/> (mirror.si, Slovenia)
-
-<http://ginette.swordarmor.fr/libreboot/> (swordarmor.fr, France)
-
FTP mirrors {#ftp}
-----------
@@ -103,8 +99,6 @@ of Kent, UK)
<ftp://ftp.linux.ro/libreboot/> (linux.ro, Romania)
-<ftp://libreboot.mirror.si/libreboot> (mirror.si, Slovenia)
-
Statically linked
------------------
diff --git a/www/faq.md b/www/faq.md
index edcb649a..78aee27b 100644
--- a/www/faq.md
+++ b/www/faq.md
@@ -6,6 +6,63 @@ x-toc-enable: true
Important issues
================
+Is the Libreboot project still active?
+-------------------------------------------
+
+Yes! The [git repository](https://notabug.org/libreboot/libreboot) shows all of
+the work that we're currently doing. Libreboot is quite active.
+
+So when is the next version of Libreboot coming out?
+-------------------------------------------------------
+
+Short answer: It's out when it's out. If you want to help out and submit
+patches, refer to [the Git page](git.md).
+
+We don't issue ETAs.
+
+Long answer:
+
+We've been re-writing the entire Libreboot build system from scratch, since
+the previous release. This has taken longer than we expected, but the new
+build system is reaching maturity. We are polishing it.
+
+Once the new build system is stable, our next priority is ensuring that all
+currently supported build targets build properly in Libreboot.
+
+After that, the priority is to make sure that all current boards in Libreboot
+use the most up to date revision of coreboot, with all of the most recent fixes
+and improvements. Testing those boards will then be a matter of peer review,
+reaching out to the entire community via alpha/beta/RC releases.
+
+Generally, all major release-blocking issues must be addressed before a new
+release can be issued. See:
+<https://notabug.org/libreboot/libreboot/issues>
+
+The most important tasks now are as follows:
+
+- Study the build system of Libreboot (written in BASH), and make fixes to it.
+- Work on new improvements and help with testing once ROMs build for all
+ boards, when the build system is stable.
+- In particular, there are several new boards in coreboot that we can add to
+ Libreboot, as documented on the Libreboot bug tracker. These will also have
+ to be added, and fully tested. Instructions for setting up hardware-based
+ flashing tools can be found in
+ [the Libreboot installation guides](docs/install/)
+- Bugs! Report bugs! <https://notabug.org/libreboot/libreboot/issues>
+- A few new board ports will also come in handy ;)
+ If you've got the skills, we'd really appreciate that. Port them to coreboot
+ first, or make existing coreboot targets work without binary blobs.
+
+More generally:
+
+- Tell your friends about Libreboot! Libreboot wants to liberate as many people
+ as possible.
+- If you have ways to improve the documentation, you can do that too.
+ Refer to [the Git page](git.md) for instructions on submitting patches to the
+ documentation.
+- Encourage companies, or any persons with the skills/resources, to get
+ involved with Libreboot development.
+
What version of libreboot do I have?
----------------------------------------------------------------
@@ -698,23 +755,23 @@ project.
### External GPUs
-The Video BIOS is present on most video hardware. On all current
-libreboot systems, this is implemented using free software. The Video
-BIOS is responsible for initializing any sort of visual display; without
-it, you'd have what's called a *headless* system.
-
-For integrated graphics, the VBIOS is usually embedded as an *option
-ROM* in the main boot firmware. For external graphics, the VBIOS is
+The Video BIOS is present on most video cards. For integrated graphics,
+the VBIOS (special kind of OptionROM) is usually embedded
+in the main boot firmware. For external graphics, the VBIOS is
usually on the graphics card itself. This is usually proprietary; the
-only difference is that SeaBIOS executes it (alternatively, you embed it
+only difference is that SeaBIOS can execute it (alternatively, you embed it
in a coreboot ROM image and have coreboot executes it, if you use a
different payload, such as GRUB).
-We're going to tentatively say no, they're not OK. Unless you're
-actively working to replace the VBIOS, or find out how to get a visual
-display without it (possible in some cases, if the kernel driver can be
-modified to work without it, possibly only needing certain
-non-executable data).
+On current libreboot systems, instead of VBIOS, coreboot native GPU init is used,
+which is currently only implemented for Intel GPUs.
+Other cards with proper KMS drivers can be initialized once Linux boots,
+but copy of VBIOS may be still needed to fetch proper VRAM frequency
+and other similar parameters (without executing VBIOS code).
+
+In configurations where SeaBIOS and native GPU init are used together,
+a special shim VBIOS is added that uses coreboot linear framebuffer.
+
### EC (embedded controller) firmware
diff --git a/www/index.md b/www/index.md
index 8fd886e1..9181a429 100644
--- a/www/index.md
+++ b/www/index.md
@@ -36,12 +36,11 @@ libreboot is fully free software, where anyone can contribute or inspect its
code.
Libreboot is faster, more secure and more reliable than most non-free
-firmware, and can provide many advanced feature, like encrypted
-/boot/, GPG signature checking before booting your kernel, ability to
-load an OS *from the flash chip*, and more.
+firmware. Libreboot provides many advanced features, like encrypted
+/boot/, GPG signature checking before booting your kernel and more!
Libreboot's main upstream provider is [coreboot](https://www.coreboot.org/),
which we deblob. We upstream our custom patches to projects like coreboot,
depthcharge, GRUB, and flashrom where possible. Together, we provide an
-automated build and installation system with nontechnical documentation,
-allowing Libreboot to be widely used.
+automated build and installation system with non-technical documentation,
+allowing Libreboot to be widely used.
diff --git a/www/management.md b/www/management.md
index b05a1826..f09ce9b7 100644
--- a/www/management.md
+++ b/www/management.md
@@ -28,13 +28,14 @@ List of members in the core management team
In alphabetical order:
- Andrew Robbins is a core developer. IRC nick **and\_who**, email
- <mailto:andrew@libreboot.org>
+ [andrew@libreboot.org](mailto:andrew@libreboot.org)
- Paul Kocialkowski is a core developer. IRC nick **paulk-X**
- (**X** is variable, and changes over time), email <mailto:paul@libreboot.org>
+ (**X** is variable, and changes over time), email
+ [paul@libreboot.org](mailto:paul@libreboot.org)
- Leah Rowe is a core developer (and project founder). IRC nick
- **\_4of7**, email <mailto:leah@libreboot.org>
+ **unoccupied**, email [leah@libreboot.org](mailto:leah@libreboot.org)
- Swift Geek is a core developer. IRC nick **swiftgeek**, email
- <mailto:swiftgeek@libreboot.org>
+ [swiftgeek@libreboot.org](mailto:swiftgeek@libreboot.org)
Generally, the people on this list have these responsibilities:
@@ -56,8 +57,8 @@ These people are not part of core management, but still have influence.
Other IRC channel moderators:
- IRC nick **specing** on the Libreboot IRC channel.
-- IRC nick **pizzaiolo** on the Libreboot IRC channel.
-- IRC nick **jxself** on the Libreboot IRC channel.
+
+specing occasionally provides assistance, and moderates the IRC channel.
Additionally, Libreboot has a separate set of operators on the subreddit
r/libreboot. Check Reddit for more information. Actions taken by moderators
diff --git a/www/news/MANIFEST b/www/news/MANIFEST
index 45bc9cae..4f588538 100644
--- a/www/news/MANIFEST
+++ b/www/news/MANIFEST
@@ -1,3 +1,4 @@
+news/libreplanet2018-workshop.md
news/release-testing-20171221.md
news/lenovo-recall.md
news/alyssa-resignation.md
diff --git a/www/news/libreplanet2018-workshop.md b/www/news/libreplanet2018-workshop.md
new file mode 100644
index 00000000..0de75670
--- /dev/null
+++ b/www/news/libreplanet2018-workshop.md
@@ -0,0 +1,99 @@
+% Libreboot installation workshop at FSF LibrePlanet 2018 conference
+% Leah Rowe
+% 21 March 2018
+
+LibrePlanet is the annual conference held by the Free Software Foundation in
+Boston, MA, USA. This year, it's being held at MIT university on March 24th
+and 25th. More details about it are here:
+<https://libreplanet.org/2018/>
+
+The FSF isn't officially hosting a Libreboot workshop at LibrePlanet
+this year. At the 2015 and 2016 LibrePlanet conference, there were workshops
+there run by myself and Patrick McDermott, a former member of the Libreboot
+project. The FSF has confirmed that they don't have a dedicated room for it
+this year, due to increasing number of conference goers.
+
+Therefore, an unofficial workshop is being set up. I've already issued a news
+post about this on the libreplanet-discuss mailing list:
+<https://lists.gnu.org/archive/html/libreplanet-discuss/2018-03/msg00037.html>
+
+With John Sullivan's blessing:
+<https://lists.gnu.org/archive/html/libreplanet-discuss/2018-03/msg00039.html>
+
+If you, the reader, are attending LibrePlanet this year, and you would like to
+get a Libreboot system flashed for you, then take it with you to LibrePlanet.
+There will be knowledgeable people there who can flash Libreboot for you.
+
+Find one of the people on the list below (list will be updated if more people
+volunteer to flash). If it's Kurt, they'll flash for you at the Technoethical
+booth. If it's someone else, they can take you into the speakers' lounge (it does
+not matter if they're not a speaker). John Sullivan of FSF has approved this.
+There are tables, chairs and power sockets in that room.
+There are also tables and chairs outside the speakers' lounge, in the common
+area at the conference, but I highly recommend using the speakers' lounge.
+That's where I took people, on LibrePlanet 2015 and 2016 :)
+It's really comfy in there.
+
+John Sullivan of FSF has also confirmed that that there is a dedicated
+*alcohol-free social and hacking time* at the FSF office on Saturday 24th
+March, between 1900-2130 (7-9:30 PM). You could also flash someone's laptop for
+them there, in the conference room at the FSF, or on a table outside. Or the
+sysadmin room, if that's OK with them.
+
+I've been asking around. The following people have confirmed so far that they
+will be providing Libreboot flashing services at the conference:
+
+- Kurt from Technoethical, an FSF-endorsed Libreboot hardware seller. They will
+ also have their own samples. They'll be at the Technoethical booth there.
+ IRC nick sensiblemn\_ or sensiblemn on #libreboot IRC
+- zyliwax from #libreboot IRC - has confirmed that they will be there
+- Patrick McDermott (pehjota) of Libiquity. Patrick is also present at
+ LibrePlanet, and has brought flashing equipment. What Patrick said on the
+ libreplanet-discuss mailing list: look for the person that is wearing a
+ grey Libiquity polo shirt. They posted this picture on the mailing list,
+ so you know how to find this person:
+ <http://www.libiquity.com/media/images/patrick-mcdermott.jpg>
+ - of note: Patrick is bringing CH341A-based programmer, and can flash D8/D16
+- You could also find an FSF sysadmin and ask them to flash Libreboot for you.
+
+I would be grateful if anyone else would also be willing to provide flashing.
+I myself am not attending the conference physically, unfortunately.
+
+See mailing list post for more info. If you would like to help Kurt and
+zyliwax out, please either reply to that mailing list post on
+libreplanet-discuss or email me directly:
+[leah@libreboot.org](mailto:leah@libreboot.org) and I'll add your name in
+the above list.
+
+Basically, all you need for flashing someone's laptop at the conference is:
+
+- Portable SPI flasher (USB powered. SSH into it via your laptop, use the SPI
+ flasher's own 3v3, etc). Make sure to use the workaround-mx patch on
+ flashrom, so that you can use `--workaround-mx` on Macronix chips, if flashing
+ an X200, otherwise flashing will be unreliable (see mailing list post linked
+ above) - portability is important, in case you sit down with someone in
+ a place without power sockets.
+ See guides on libreboot.org for setting up SPI flashers, but ignore the notes
+ about external PSUs and instead just wire up the flasher's own 3v3 connection.
+ The workaround-mx patch is here:
+ <https://notabug.org/consts/libreboot/raw/2caaac00972d9ea56b0fcd7c95897e90283b05b8/projects/flashrom/patches/0005-Workaround-MX25-reliable-operation.patch>
+ apply this on flashrom src and build with that. To use it, just pass the
+ `--workaround-mx` option in flashrom.
+- Screwdrivers (phillips head 0 *and* 00 - sometimes labelled PH0 or PH00,
+ respectively)
+- Thermal paste and thermal cleaning material, for T400 flashing
+ - arctic mx-4 paste recommended. For cleaning material, use anti-static cloth
+ and isopropyl alcohol - as pure as possible! ideally close to 100%! 70%
+ rubbing alcohol is common in USA, and not suitable for electronics
+- Anti-ESD wrist/ankle strap, to protect against damage from electrostatic
+ discharge when working with circuit boards.
+
+Optionally:
+
+- Bring DIP8 25xx SPI chips with Libreboot, for ASUS KCMA-D8 or KGPE-D16, for the
+ conference goer to put in their D8/D16 when they get home. Also PLCC32 LPC
+ 1MB (or bigger, with padding at the beginning) chips for ASUS KFSN4-DRE
+- Soldering equipment (knife tip, hot air, etc) for X200T flashing. NOTE: FSF has
+ soldering equipment in their office, you could ask them to lend it to you
+ if you're flashing a laptop there at the FSF office. NOTE2: Kurt from
+ Technoethical is also bringing soldering equipment.