From: ng0 <ng0@n0.is>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: omvf firmware
Date: Thu, 15 Mar 2018 20:29:37 +0000 [thread overview]
Message-ID: <20180315202937.dtnuqfkh6h34nzcy@abyayala> (raw)
In-Reply-To: <20180315194815.GA1080@macbook41>
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 <efraim@flashner.co.il> אפרים פלשנר
> 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
next prev parent reply other threads:[~2018-03-15 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 19:48 omvf firmware Efraim Flashner
2018-03-15 20:29 ` ng0 [this message]
2018-03-15 20:47 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180315202937.dtnuqfkh6h34nzcy@abyayala \
--to=ng0@n0.is \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).