From: Clem Cole <clemc@ccc.com>
To: Dan Cross <crossd@gmail.com>
Cc: Paul Ruizendaal <pnr@planet.nl>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Porting the SysIII kernel: boot, config & device drivers
Date: Sat, 31 Dec 2022 16:39:31 -0500 [thread overview]
Message-ID: <CAC20D2NpQdY+oRj-qK45=LR6GuLR3w7ZVmu9SWBd4s6v_Mvepw@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W4_ZwOst9yo2GiM4qO4EwapEFia9X7kDZjwQUuhxaEVVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On Sat, Dec 31, 2022 at 4:11 PM Dan Cross <crossd@gmail.com> wrote:
>
> I'm going to push back on this slightly: UEFI+ACPI get a bad rap
> because, well, they're really pretty bad. Oh sure, some things are
> reasonable: the ACPI table formats aren't awful. But I've been inside
> a couple of these now and phew golly, they stink pretty badly.
>
Fair enough. UEFI+ACPI started from BIOS and really should have been a
full re-think and write by senior OS people.
It was not. The problem for us techies, is that doing that was not going
to save or make anyone $s.
The problem for management was they wanted to keep the old BIOS around
(that's what the customer wanted - cheapest path forward) and unless there
was a reason to break from tradition, they were not going too. Apple
could (and did) but HP/Dell et al did not want too.
ᐧ
[-- Attachment #2: Type: text/html, Size: 1919 bytes --]
next prev parent reply other threads:[~2022-12-31 21:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 18:25 [TUHS] " Paul Ruizendaal
2022-12-30 18:56 ` [TUHS] " Steve Nickolas
2022-12-31 14:59 ` Dan Cross
2022-12-31 19:08 ` Clem Cole
2022-12-31 21:10 ` Dan Cross
2022-12-31 21:39 ` Clem Cole [this message]
2022-12-31 21:52 ` Dan Cross
2022-12-31 23:25 ` Dave Horsfall
2023-01-01 1:02 ` Rob Pike
2023-01-01 1:16 ` George Michaelson
2023-01-01 1:40 ` Larry McVoy
2023-01-01 2:29 ` Warner Losh
2023-01-01 1:24 ` Larry McVoy
2022-12-31 22:38 ` Theodore Ts'o
2022-12-31 22:55 ` Marc Donner
2023-01-01 3:55 ` Dan Cross
2023-01-01 20:29 ` Paul Ruizendaal
2023-01-01 21:26 ` G. Branden Robinson
2023-01-01 21:31 ` Rob Pike
2022-12-31 21:11 ` Paul Ruizendaal
2022-12-31 20:02 ` Paul Ruizendaal
2022-12-31 21:04 ` Warner Losh
2022-12-31 21:41 ` Dan Cross
2023-01-01 3:08 ` Warner Losh
2023-01-01 4:40 ` Dan Cross
2023-01-01 8:05 ` Jonathan Gray
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='CAC20D2NpQdY+oRj-qK45=LR6GuLR3w7ZVmu9SWBd4s6v_Mvepw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=crossd@gmail.com \
--cc=pnr@planet.nl \
--cc=tuhs@tuhs.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.
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).