From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 0/1] Enable ACPI support on ARM64
Date: Wed, 16 Sep 2020 13:46:49 +0100
Message-ID: <D60D3E6F-4282-45BB-AE48-A478A9DBAA12@ipfire.org>
In-Reply-To: <20200914013249.30733-1-matt@traverse.com.au>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============3491264335091620503=="
List-Id: <development.lists.ipfire.org>

--===============3491264335091620503==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Matthew,

Great to hear from you again.

Do you think this could also resolve this problem?

  https://bugzilla.ipfire.org/show_bug.cgi?id=3D11940

Best,
-Michael

> On 14 Sep 2020, at 02:32, Mathew McBride <matt(a)traverse.com.au> wrote:
>=20
> Hi all,
> It's been a while.
>=20
> This patch enables ACPI support for ARM64 which allows IPFire to boot on ARM
> "server" machines which use EFI/TianoCore to boot.
>=20
> One such example is the QEMU arm64 "virt" machine with an EFI firmware -
> https://releases.linaro.org/reference-platform/enterprise/latest/uefi/
>=20
> The arm64 images from "standard" distros (Debian/Ubuntu/Fedora/etc.) are
> designed to work with this EFI+ACPI combination.
>=20
> There should be no regressions for any current arm64 hardware supported
> by IPFire - Linux will only use ACPI tables if present, if
> not fallback to device tree.
>=20
> The use case for this is to run our hardware[1] using the muvirt[2] VM host,
> which also allows some "blending" of OpenWrt functions on the host, e.g
> the host can manage bridging of Ethernet ports and WiFi hostapd
> so IPFire can work with simple Ethernet interfaces for the
> Red/Green/Blue/Orange.
>=20
> You can see the Fireinfo profile for the VM here -
> https://fireinfo.ipfire.org/profile/67aa9a9cff94f3ef8f61866197a57106ccdcea4b
>=20
> I have successfully speedtested ~1Gbps though
> this virtualized setup so this should provide more than adequate
> performance for most situations.
>=20
> It is not possible to run IPFire directly on our LS1088 (Ten64) platform
> at the moment as 4.14 does not have working Ethernet (DPAA2) and PCIe
> controller drivers. It is possible to backport them from later kernels
> (and I did have a go at this a few months ago) - but it is a very large
> patch (>1M lines) and that is before considering any of the features and
> fixes in more recent kernels (e.g backporting PHYLINK).
>=20
> When IPFire moves to a newer kernel that would be a good time to revisit th=
is.
>=20
> [1] - https://traverse.com.au/products/ten64-networking-platform/
> [2] - https://gitlab.com/traversetech/muvirt
>=20
> Mathew McBride (1):
>  kernel: enable ACPI support on ARM64
>=20
> config/kernel/kernel.config.aarch64-ipfire | 99 +++++++++++++++++++++-
> 1 file changed, 96 insertions(+), 3 deletions(-)
>=20
> --=20
> 2.19.1
>=20


--===============3491264335091620503==--