From: Juan Cuzmar <juan.cuzmar.s@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] call for testing
Date: Sat, 4 Apr 2020 21:48:51 -0300 [thread overview]
Message-ID: <CAMmEtnD32hGk8df0mXeZHoydYpMUPBZgN0KA0sEConxYStBhzA@mail.gmail.com> (raw)
In-Reply-To: <05E00F0CC340421AEDA9D66E230C7510@felloff.net>
My tablet samsung booted fine.
On Sat, Apr 4, 2020 at 2:40 PM <cinap_lenrek@felloff.net> wrote:
>
> i'v just pushed the new memory map code for pc and pc64 kernels:
>
> http://code.9front.org/hg/plan9front/rev/7eba9c247d5d
>
> i'v tested the code on qemu, vmware, t495, x230, x200 and t23
> thinkpads and it works without issues for me.
>
> however, this is a tricky part of code and the new memory map
> code differs in reserving region types (now it uses strict
> priorities: Reserved > ACPI > RAM > UMB > UPA). it is possible
> that some machines just worked by accident before and now stop
> booting.
>
> so if you can, i'd like to encurage you to help test this by
> just booting the current pc or pc64 kernel and see if it can
> still boot.
>
> on the plus side, the new code should be more robust against
> broken uefi and bios memory maps. it works by delaying user
> memory allocation until the acpi tables have been discovered
> and mapped out. this means it can work around acpi tables
> overlapping usable memory which might have prevented us booting
> before (this is the case on the new lenovo t495 which motivated
> the change).
>
> so now would also be a good time to try these machines again.
>
> --
> cinap
next prev parent reply other threads:[~2020-04-05 0:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 17:39 cinap_lenrek
2020-04-05 0:48 ` Juan Cuzmar [this message]
2020-04-05 2:29 ` [9front] " ori
2020-04-05 19:59 ` mike
2020-04-06 14:30 ` stevie
2020-04-07 7:34 ` Iruatã Souza
2020-04-09 9:19 ` Ethan Gardener
2020-04-14 1:39 ` sl
2020-04-06 4:31 qwx
2020-04-06 10:47 ` mike
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=CAMmEtnD32hGk8df0mXeZHoydYpMUPBZgN0KA0sEConxYStBhzA@mail.gmail.com \
--to=juan.cuzmar.s@gmail.com \
--cc=9front@9front.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).