From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [PATCH 0/1] Enable ACPI support on ARM64 Date: Thu, 17 Sep 2020 08:14:34 +0100 Message-ID: In-Reply-To: <0c0601d68c94$89616c00$9c244400$@traverse.com.au> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8135192562186048678==" List-Id: --===============8135192562186048678== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, Ah that is good to hear. I didn=E2=80=99t have time to investigate, and so far I have personally only = worked with IPFire aarch64 in KVM virtual machines where it simply boots fine. Best, -Michael > On 17 Sep 2020, at 02:47, Mathew McBride wrote: >=20 > Hello Michael, > Yes - this is the exact same symptom (no serial output after GRUB handoff) I > see if I boot the current core148 image. >=20 > As there is no DTB being presented by the firmware (only ACPI tables), the > kernel won't be able to find the serial UART to use. >=20 > Regards, > Matt >=20 > -----Original Message----- > From: Michael Tremer =20 > Sent: Wednesday, 16 September 2020 10:47 PM > To: Mathew McBride > Cc: development(a)lists.ipfire.org > Subject: Re: [PATCH 0/1] Enable ACPI support on ARM64 >=20 > Hello Matthew, >=20 > Great to hear from you again. >=20 > Do you think this could also resolve this problem? >=20 > https://bugzilla.ipfire.org/show_bug.cgi?id=3D11940 >=20 > Best, > -Michael >=20 >> On 14 Sep 2020, at 02:32, Mathew McBride wrote: >>=20 >> Hi all, >> It's been a while. >>=20 >> This patch enables ACPI support for ARM64 which allows IPFire to boot=20 >> on ARM "server" machines which use EFI/TianoCore to boot. >>=20 >> One such example is the QEMU arm64 "virt" machine with an EFI firmware=20 >> -=20 >> https://releases.linaro.org/reference-platform/enterprise/latest/uefi/ >>=20 >> The arm64 images from "standard" distros (Debian/Ubuntu/Fedora/etc.)=20 >> are designed to work with this EFI+ACPI combination. >>=20 >> There should be no regressions for any current arm64 hardware=20 >> supported by IPFire - Linux will only use ACPI tables if present, if=20 >> not fallback to device tree. >>=20 >> The use case for this is to run our hardware[1] using the muvirt[2] VM=20 >> host, which also allows some "blending" of OpenWrt functions on the=20 >> host, e.g the host can manage bridging of Ethernet ports and WiFi=20 >> hostapd so IPFire can work with simple Ethernet interfaces for the=20 >> Red/Green/Blue/Orange. >>=20 >> You can see the Fireinfo profile for the VM here -=20 >> https://fireinfo.ipfire.org/profile/67aa9a9cff94f3ef8f61866197a57106cc >> dcea4b >>=20 >> I have successfully speedtested ~1Gbps though this virtualized setup=20 >> so this should provide more than adequate performance for most=20 >> situations. >>=20 >> It is not possible to run IPFire directly on our LS1088 (Ten64)=20 >> platform at the moment as 4.14 does not have working Ethernet (DPAA2)=20 >> and PCIe controller drivers. It is possible to backport them from=20 >> later kernels (and I did have a go at this a few months ago) - but it=20 >> is a very large patch (>1M lines) and that is before considering any=20 >> 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 > this. >>=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 >> -- >> 2.19.1 >>=20 >=20 >=20 --===============8135192562186048678==--