From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] split floppy support off biosdisk
Date: Tue, 17 Jun 2008 19:23:05 +0200 [thread overview]
Message-ID: <1213723385.6330.35.camel@localhost> (raw)
In-Reply-To: <ca0f59980806170752i1a809977qf0053f112ec4e780@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
El mar, 17-06-2008 a las 22:52 +0800, Bean escribió:
> Hi,
>
> I think memory is not a problem here, as grub2 can use upper memory:
>
> src = raw data
> dest = 0x100000
> buf = dest + kernel_size
>
We could do that, but since the code would execute at the very first
stages, where we still don't have a memory map, we could overwrite
something important and wreak havoc. It's unlikely, since most computers
have a wide space at 1MB with most or all of the RAM, before the ACPI
structures and the BIOS area at the end. However, we should contemplate
the possibility of things going awry and prepare to receive bug reports
about failures on esoterically nonstandard computers, such as "GRUB
triple-faults my HP Vectra 75".
Alternatively, we could first check the BDA and, if we have enough
"lower" memory for the operation, use it before venturing into post-1MB
territory.
I'm currently checking the memory requisites of LZMA decompression
depending on the -1..9 compression setting, and will report back when
finished
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-06-17 17:22 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 17:48 [RFC] split floppy support off biosdisk Robert Millan
2008-06-16 0:32 ` Pavel Roskin
2008-06-16 6:30 ` Bean
2008-06-16 9:15 ` Robert Millan
2008-06-16 11:03 ` Bean
2008-06-16 11:20 ` Javier Martín
2008-06-16 11:47 ` Bean
2008-06-16 12:09 ` Javier Martín
2008-06-16 12:37 ` Bean
2008-06-16 21:31 ` Robert Millan
2008-06-17 2:03 ` Bean
2008-06-17 2:47 ` Javier Martín
2008-06-17 3:06 ` Bean
2008-06-17 14:39 ` Javier Martín
2008-06-17 14:52 ` Bean
2008-06-17 17:23 ` Javier Martín [this message]
2008-06-17 17:35 ` Bean
2008-06-18 3:14 ` Javier Martín
2008-06-18 3:49 ` Pavel Roskin
2008-06-18 6:55 ` Bean
2008-06-18 7:36 ` Pavel Roskin
2008-06-18 8:01 ` Bean
2008-06-18 11:29 ` Bean
2008-06-18 17:37 ` Robert Millan
2008-06-18 11:40 ` Javier Martín
2008-06-18 13:12 ` Bean
2008-06-18 13:28 ` Bean
2008-06-18 13:33 ` Javier Martín
2008-06-18 17:32 ` Isaac Dupree
2008-06-18 17:38 ` Robert Millan
2008-06-18 3:48 ` Javier Martín
2008-06-17 15:02 ` Bean
2008-06-17 15:54 ` Pavel Roskin
2008-06-18 17:53 ` Yoshinori K. Okuji
2008-06-17 12:22 ` Robert Millan
2008-06-17 12:33 ` Robert Millan
2008-06-17 12:54 ` Robert Millan
2008-06-18 17:52 ` Yoshinori K. Okuji
2008-06-18 22:15 ` Robert Millan
2008-06-18 23:56 ` Pavel Roskin
2008-06-19 2:14 ` Yoshinori K. Okuji
2008-06-19 2:37 ` Pavel Roskin
2008-06-19 12:20 ` Robert Millan
2008-06-19 19:22 ` Pavel Roskin
2008-06-16 13:06 ` Pavel Roskin
2008-06-16 14:06 ` Bean
2008-06-16 14:38 ` Pavel Roskin
2008-06-16 21:13 ` Robert Millan
2008-06-16 21:12 ` Robert Millan
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=1213723385.6330.35.camel@localhost \
--to=lordhabbit@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.