public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: EFI
Date: Tue, 19 Jun 2018 11:26:10 +0100	[thread overview]
Message-ID: <805e82694faee6fa5fda67944b239c3a93b293d9.camel@ipfire.org> (raw)
In-Reply-To: <e73552be4b7c4d058a410ae0ff79b5825de0d70d.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2307 bytes --]

Hello guys,

images for testing are from now on available here:

  https://nightly.ipfire.org/efi/

Best,
-Michael

On Mon, 2018-06-18 at 16:04 +0100, Michael Tremer wrote:
> Hello,
> 
> it is finally time to think about EFI. That's the new kind of BIOS.
> 
> In the past we have been ignoring this since the community did not want to
> fund
> any work in this area and there was enough hardware out there that booted up
> fine without support for EFI.
> 
> Now this has changed, since Hannes told me that there is going to be more and
> more boards without a CSM and we are going to port IPFire to ARM64 soon which
> doesn't have a classic BIOS at all.
> 
> For ARM64, I might even want to push for EFI-only, but Arne disagrees :P
> 
> So what has happened so far?
> 
> I have created a new branch "efi":
> 
>   https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=refs/heads/efi
> 
> This branch collects all the changes to the bootloader, the scripts that
> author
> the images and the installer. Please review and send your comments.
> 
> The build creates two things in the end:
> 
> An ISO image that is bootable in EFI mode. It will install the system for EFI
> whether the system supports EFI or not. That will allow us to move a harddisk
> from one machine to another one. Opposed to the flash image, the installer
> will
> try to create a boot entry in the EFI BIOS.
> 
> The flash image will also boot in EFI mode or normal BIOS mode, depending on
> the
> system and leave the system configuration untouched.
> 
> Since EFI is a tricky standard and other distributions had loads of trouble
> with
> it in the past, we need loads of people to test these images on their
> hardware.
> I hope that we will be able to sort out any boot issues as soon as possible
> with
> this method.
> 
> Existing installations will not be migrated.
> 
> We will support EFI only for x86_64 and aarch64. There is only a few systems
> out
> there that are 32 bit and support EFI. Those are usually not a good choice for
> running IPFire.
> 
> Since I have no images ready right now, there is only code to review. I will
> upload images as soon as possible so that you guys can help testing without
> compiling them yourself.
> 
> Best,
> -Michael

  reply	other threads:[~2018-06-19 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 15:04 EFI Michael Tremer
2018-06-19 10:26 ` Michael Tremer [this message]
2018-07-18 10:28   ` EFI Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=805e82694faee6fa5fda67944b239c3a93b293d9.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox