diff options
Diffstat (limited to 'www/faq.md')
| -rw-r--r-- | www/faq.md | 83 |
1 files changed, 70 insertions, 13 deletions
@@ -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 |