From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 5th Edition
Date: Sat, 19 Nov 2016 18:42:52 +0000 [thread overview]
Message-ID: <35766389-472D-49CB-A992-487EA74C86E9@quintile.net> (raw)
In-Reply-To: <d83fbf5b1347538304ab895d4d60addc@felloff.net>
Cinap,
I salute you and the good sense you write.
-Steve
> On 19 Nov 2016, at 16:57, cinap_lenrek@felloff.net wrote:
>
> calling into firmware code is a big can of worms because firmware is full
> of bugs and only works with a small set of the major operating systems that
> the firmware authors tested it with.
>
> and theres not really an option for doing it from userspace.
>
> you need to call it from kernel mode ring zero and make sure the firmware
> has the same idea of the virtual memory mappings as your kernel plus
> work arround the unstated assumptions of the firmware.
>
> linux has a track record of bricked machines and firmware corrupting
> memory.
>
> it is just not worth it.
>
> in 9front, the kernel never calls firmware. it does interpret a limited
> set of acpi methods on boot to figure out pci interrupt mappings and
> and then frees the acpi environment never to return.
>
> all efi/bios calls are done by the bootloader *before* it enters the kernel
> so we never have to rely on efi/bios firmware assumptoins. the bootloader
> collects the information from efi and passes it to the kernel as plan9.ini
> variables.
>
> efi firmware has a boot manager were the user can add and modify entries.
>
> --
> cinap
next prev parent reply other threads:[~2016-11-19 18:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 22:27 Charlie Lin
2016-11-16 22:43 ` Stanley Lieber
2016-11-16 22:44 ` Ole-Hjalmar Kristensen
2016-11-16 23:53 ` Chris McGee
2016-11-17 0:34 ` James A. Robinson
2016-11-17 1:14 ` Charlie Lin
2016-11-17 16:16 ` Dave MacFarlane
2016-11-17 17:50 ` Ori Bernstein
2016-11-17 20:29 ` Chris McGee
2016-11-17 20:32 ` Ori Bernstein
2016-11-17 20:31 ` Chris McGee
2016-11-17 0:21 ` Charlie Lin
2016-11-17 0:30 ` Kurt H Maier
2016-11-18 19:54 ` Charlie Lin
2016-11-18 19:57 ` Charlie Lin
2016-11-18 19:58 ` Charlie Lin
2016-11-18 22:26 ` hiro
2016-11-18 22:28 ` hiro
2016-11-19 16:57 ` cinap_lenrek
2016-11-19 18:42 ` Steve Simon [this message]
[not found] ` <CAEVxPTMKBpWFEGr-k1diNa2BVgCjsL1g-OPZdhn9LmEn3uLB5g@mail.gmail.com>
[not found] ` <CAEVxPTN_KZn_4+s1xr-uiDzEY72wf2AtrXYN_FDgdaPbyqpLbw@mail.gmail.com>
2016-11-18 20:07 ` Jules Merit
2016-11-17 0:55 ` Charlie Lin
2016-11-17 1:02 ` Stanley Lieber
2016-11-17 1:18 ` Kurt H Maier
2016-11-19 22:27 ` David Arnold
2016-11-20 2:39 ` hiro
2016-11-20 4:26 ` Ryan Gonzalez
2016-11-20 6:22 ` Kurt H Maier
2016-11-20 6:54 ` James A. Robinson
2016-11-20 9:44 ` hiro
2016-11-21 2:19 ` Wes Kussmaul
2016-11-21 8:02 ` hiro
2016-11-21 8:02 ` Kurt H Maier
2016-11-21 8:46 ` Sigrid Haflinadóttir
2016-11-21 15:08 ` Wes Kussmaul
2016-11-21 15:42 ` Chris McGee
2016-11-19 20:19 ` Charlie Lin
2016-11-19 20:37 ` Charlie Lin
2016-11-19 21:51 ` Steve Simon
2016-11-19 22:27 ` Stanley Lieber
2016-11-20 15:23 ` Chris McGee
2016-11-20 18:09 ` hiro
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=35766389-472D-49CB-A992-487EA74C86E9@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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).