From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: maobibo <maobibo@loongson.cn>,
gaosong@loongson.cn, jiaxun.yang@flygoat.com,
qemu-devel@nongnu.org, thomas@t-8ch.de, xry111@xry111.site,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
Jinyang He <hejinyang@loongson.cn>,
Tiezhu Yang <yangtiezhu@loongson.cn>
Subject: Re: LoongArch without CONFIG_ACPI and CONFIG_EFI
Date: Sat, 7 Sep 2024 04:48:22 +0200 [thread overview]
Message-ID: <Ztu-9qgiKS98c0hl@zx2c4.com> (raw)
In-Reply-To: <CAAhV-H5CbyemhjoYLXqW3pLPtp4Ne3wcOZXzv2k5=jJCpi3rfg@mail.gmail.com>
On Sat, Sep 07, 2024 at 09:47:38AM +0800, Huacai Chen wrote:
> On Sat, Sep 7, 2024 at 9:44 AM maobibo <maobibo@loongson.cn> wrote:
> >
> > Add huacai who is maintainer of Loongarch Linux kernel.
> >
> > On 2024/9/6 下午10:55, Jason A. Donenfeld wrote:
> > > Hi,
> > >
> > > It appears that as of QEMU 9.1, it's possible to boot LoongArch machines
> > > that don't provide EFI or ACPI.
> > >
> > > Would you consider removing the `select ACPI` and `select EFI` from the
> > > arch Kconfig, so that kernels built for this minimal QEMU environment
> > > can be a bit leaner and quicker to build?
> Very difficult, at least removing EFI is difficult. Even if booting to
> a FDT environment, we still get information from EFI now.
Makes sense. !ACPI is the more interesting one for me, anyway, as that
takes a while to build.
prev parent reply other threads:[~2024-09-07 2:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 14:55 LoongArch without CONFIG_ACPI and CONFIG_EFI Jason A. Donenfeld
2024-09-07 1:44 ` maobibo
2024-09-07 1:47 ` Huacai Chen
2024-09-07 2:48 ` Jason A. Donenfeld [this message]
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=Ztu-9qgiKS98c0hl@zx2c4.com \
--to=jason@zx2c4.com \
--cc=chenhuacai@kernel.org \
--cc=gaosong@loongson.cn \
--cc=hejinyang@loongson.cn \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=thomas@t-8ch.de \
--cc=xry111@xry111.site \
--cc=yangtiezhu@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).