All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: What's the point of allocating the protected mode code on 0x100000 only (UEFI)
Date: Tue, 16 Feb 2010 12:51:11 +0100	[thread overview]
Message-ID: <4B7A86AF.3020506@gmail.com> (raw)
In-Reply-To: <d516a67d1002160340m2ede743etca61abde2144ad07@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

George Buranov wrote:
> Hello,
>
> I just found another computer with working UEFI (I was testing on UEFI
> simulation) and just found that the kernel load does not work. I found
> out that the problem is in code
>
>   /* Next, find free pages for the protected mode code.  */
>   /* XXX what happens if anything is using this address?  */
>   prot_mode_mem = grub_efi_allocate_pages (0x100000, prot_mode_pages + 1);
>   if (! prot_mode_mem)
>     {
>       grub_error (GRUB_ERR_OUT_OF_MEMORY,
>           "cannot allocate protected mode pages");
>       goto fail;
>     }
>
> This function return with false for me. I am continuing investigation,
> but maybe you know the reason why the allocation is on this special
> address? Can we change it?
As I already said I have a working prototype for this in newreloc branch.
>
> Regards,
> Georgy
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>   


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  reply	other threads:[~2010-02-16 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 11:40 What's the point of allocating the protected mode code on 0x100000 only (UEFI) George Buranov
2010-02-16 11:51 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-02-17  6:00   ` gburanov

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=4B7A86AF.3020506@gmail.com \
    --to=phcoder@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.