From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Matt Fleming <matt@console-pimps.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] x86 EFI boot stub
Date: Thu, 11 Aug 2011 19:55:00 +0200 [thread overview]
Message-ID: <4E441774.2040904@gmail.com> (raw)
In-Reply-To: <1313075678.3436.69.camel@mfleming-mobl1.ger.corp.intel.com>
Hey,
On 08/11/2011 05:14 PM, Matt Fleming wrote:
> On Thu, 2011-08-11 at 15:05 +0200, Maarten Lankhorst wrote:
>> On 08/11/2011 12:59 PM, Matt Fleming wrote:
>>> From: Matt Fleming <matt.fleming@intel.com>
>>>
>>> This series adds support for an EFI boot stub, similar to the existing
>>> BIOS boot stub. The result is that you can boot a bzImage on an EFI
>>> machine without the use of a boot loader by making the bzImage appear
>>> to the EFI firmware to be an EFI application. Also, a single bzImage
>>> can be booted on either a BIOS or EFI machine.
>>>
>>> Using the EFI boot stub has the advantage that the kernel is
>>> responsible for configuring the machine to the point where we can
>>> fully boot the kernel, so we are no longer at the mercy of the boot
>>> loader.
>>>
>> Fails to boot here. I thought changing characteristics from 0x60500020 to 0xe0500020 would help, but no. :/
>> This change would make the code section writable.
> Thanks for testing out the patches Maarten!
>
>> FileAlignment you use is probably wrong, I think it should be 0x200 not 0x2000 .
> Yep, thanks. That looks like a typo.
>
>> Maybe you need to add a data section and fix SizeOfInitializedData too?
> Hmm.. possibly. Is this on x86-64?
Yeah the system I'm testing on is 64-bits, if it you get this one working I can check if my old mac mini supports 32-bits efi too.
>> It just hangs on a blinking cursor, no idea if it actually started executing anything yet or not, since nothing is printed out.
> Hmm.. do you have early printk enabled? Can you hook up a serial console
> to this machine?
>
I get no output on serial console with vmlinuz.efi so it crashes before 'early console in decompress_kernel' is printed.
~Maarten
next prev parent reply other threads:[~2011-08-11 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 10:59 [PATCH 0/9] x86 EFI boot stub Matt Fleming
2011-08-11 10:59 ` [PATCH 1/9] x86: Don't use magic strings for EFI loader signature Matt Fleming
2011-08-11 10:59 ` [PATCH 2/9] efi.h: Add struct definition for boot time services Matt Fleming
2011-08-11 10:59 ` [PATCH 3/9] efi.h: Add efi_image_loaded_t Matt Fleming
2011-08-11 10:59 ` [PATCH 4/9] efi.h: Add allocation types for boottime->allocate_pages() Matt Fleming
2011-08-11 10:59 ` [PATCH 5/9] efi.h: Add graphics protocol guid Matt Fleming
2011-08-11 10:59 ` [PATCH 6/9] efi.h: Add boottime->locate_handle search types Matt Fleming
2011-08-11 10:59 ` [PATCH 7/9] efi: Add EFI file I/O data types Matt Fleming
2011-08-11 10:59 ` [PATCH 8/9] x86, efi: EFI boot stub support Matt Fleming
2011-08-11 18:09 ` Andi Kleen
2011-08-17 11:46 ` Matt Fleming
2011-08-11 10:59 ` [PATCH 9/9] x86, efi: Make efi_call_phys_prelog() CONFIG_RELOCATABLE-aware Matt Fleming
2011-08-11 13:05 ` [PATCH 0/9] x86 EFI boot stub Maarten Lankhorst
2011-08-11 15:14 ` Matt Fleming
2011-08-11 17:55 ` Maarten Lankhorst [this message]
2011-08-26 12:29 ` Matt Fleming
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=4E441774.2040904@gmail.com \
--to=m.b.lankhorst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.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