[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: omvf firmware
From: |
ng0 |
Subject: |
Re: omvf firmware |
Date: |
Thu, 15 Mar 2018 20:29:37 +0000 |
Efraim Flashner transcribed 2.0K bytes:
> I succesfully built ovmf firmware for aarch64 on my aarch64 board.
> Currently it builds for x86_64 and i686 on %intel platforms only. I
> think it's best to create a make-ovmf-firmware procedure to build the
> firmware for x86_64/i686/aarch64/armhf, but there's not a clear
> cross-grade path from our current x86_64 & i686 package to x86_64 or
> i686.
>
> The two other options I've thought of are adding aarch64 and armhf
> support to our current package, which would balloon the native-inputs
> with cross compilers, or leave the current package and add 1 or 2 new
> pacakges, but then I feel like that's almost back to my original intent
> of creating a procedure and 4 packages.
>
> Suggestions? Comments?
I don't know omvf. Does it involve kernel space modules? I've started
experimenting with a path to a generalized kernel-module support (which
needs the "source" we currently throw away of the kernel, etc).
Or what this firmware like?
> --
> Efraim Flashner <address@hidden> אפרים פלשנר
> GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
> Confidentiality cannot be guaranteed on emails sent or received unencrypted
--
A88C8ADD129828D7EAC02E52E22F9BBFEE348588
https://n0.is
- omvf firmware, Efraim Flashner, 2018/03/15
- Re: omvf firmware,
ng0 <=