<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/x86/boot/compressed, branch linux-3.7.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.7.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.7.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2013-02-04T00:27:06Z</updated>
<entry>
<title>x86, efi: Fix 32-bit EFI handover protocol entry point</title>
<updated>2013-02-04T00:27:06Z</updated>
<author>
<name>David Woodhouse</name>
</author>
<published>2013-01-07T22:01:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e8298a286761e2e9b3aa1b088b7e8aef0da45c6c'/>
<id>urn:sha1:e8298a286761e2e9b3aa1b088b7e8aef0da45c6c</id>
<content type='text'>
commit f791620fa7517e1045742c475a7f005db9a634b8 upstream.

If the bootloader calls the EFI handover entry point as a standard function
call, then it'll have a return address on the stack. We need to pop that
before calling efi_main(), or the arguments will all be out of position on
the stack.

Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
Link: http://lkml.kernel.org/r/1358513837.2397.247.camel@shinybook.infradead.org
Signed-off-by: H. Peter Anvin &lt;hpa@linux.intel.com&gt;
Cc: Matt Fleming &lt;matt.fleming@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>x86, efi: Fix display detection in EFI boot stub</title>
<updated>2013-02-04T00:27:06Z</updated>
<author>
<name>David Woodhouse</name>
</author>
<published>2013-01-07T21:52:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=23c70dc831ea93fa73b29167cd7ed94147b61386'/>
<id>urn:sha1:23c70dc831ea93fa73b29167cd7ed94147b61386</id>
<content type='text'>
commit 70a479cbe80296d3113e65cc2f713a5101061daf upstream.

When booting under OVMF we have precisely one GOP device, and it
implements the ConOut protocol.

We break out of the loop when we look at it... and then promptly abort
because 'first_gop' never gets set. We should set first_gop *before*
breaking out of the loop. Yes, it doesn't really mean "first" any more,
but that doesn't matter. It's only a flag to indicate that a suitable
GOP was found.

In fact, we'd do just as well to initialise 'width' to zero in this
function, then just check *that* instead of first_gop. But I'll do the
minimal fix for now (and for stable@).

Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
Link: http://lkml.kernel.org/r/1358513837.2397.247.camel@shinybook.infradead.org
Signed-off-by: H. Peter Anvin &lt;hpa@linux.intel.com&gt;
Cc: Matt Fleming &lt;matt.fleming@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>x86, efi: Fix processor-specific memcpy() build error</title>
<updated>2012-11-20T20:52:07Z</updated>
<author>
<name>Matt Fleming</name>
</author>
<published>2012-11-20T13:07:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0f905a43ce955b638139bd84486194770a6a2c08'/>
<id>urn:sha1:0f905a43ce955b638139bd84486194770a6a2c08</id>
<content type='text'>
Building for Athlon/Duron/K7 results in the following build error,

arch/x86/boot/compressed/eboot.o: In function `__constant_memcpy3d':
eboot.c:(.text+0x385): undefined reference to `_mmx_memcpy'
arch/x86/boot/compressed/eboot.o: In function `efi_main':
eboot.c:(.text+0x1a22): undefined reference to `_mmx_memcpy'

because the boot stub code doesn't link with the kernel proper, and
therefore doesn't have access to the 3DNow version of memcpy. So,
follow the example of misc.c and #undef memcpy so that we use the
version provided by misc.c.

See https://bugzilla.kernel.org/show_bug.cgi?id=50391

Reported-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Reported-by: Ryan Underwood &lt;nemesis@icequake.net&gt;
Cc: H. Peter Anvin &lt;hpa@zytor.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: Matt Fleming &lt;matt.fleming@intel.com&gt;
</content>
</entry>
<entry>
<title>x86, EFI: Calculate the EFI framebuffer size instead of trusting the firmware</title>
<updated>2012-09-17T12:29:24Z</updated>
<author>
<name>Matthew Garrett</name>
</author>
<published>2012-07-27T21:20:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e9b10953edbccd3744e039ffc060ab2692f17856'/>
<id>urn:sha1:e9b10953edbccd3744e039ffc060ab2692f17856</id>
<content type='text'>
Seth Forshee reported that his system was reporting that the EFI framebuffer
stretched from 0x90010000-0xb0010000 despite the GPU's BAR only covering
0x90000000-0x9ffffff. It's safer to calculate this value from the pixel
stride and screen height (values we already depend on) rather than face
potential problems with resource allocation later on.

Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Tested-by: Seth Forshee &lt;seth.forshee@canonical.com&gt;
Signed-off-by: Matt Fleming &lt;matt.fleming@intel.com&gt;
</content>
</entry>
<entry>
<title>efifb: Skip DMI checks if the bootloader knows what it's doing</title>
<updated>2012-09-17T12:29:23Z</updated>
<author>
<name>Matthew Garrett</name>
</author>
<published>2012-07-27T16:58:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f462ed939de67c20528bc08f11d2fc4f2d59c0d5'/>
<id>urn:sha1:f462ed939de67c20528bc08f11d2fc4f2d59c0d5</id>
<content type='text'>
The majority of the DMI checks in efifb are for cases where the bootloader
has provided invalid information. However, on some machines the overrides
may do more harm than good due to configuration differences between machines
with the same machine identifier. It turns out that it's possible for the
bootloader to get the correct information on GOP-based systems, but we
can't guarantee that the kernel's being booted with one that's been updated
to do so. Add support for a capabilities flag that can be set by the
bootloader, and skip the DMI checks in that case. Additionally, set this
flag in the UEFI stub code.

Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Acked-by: Peter Jones &lt;pjones@redhat.com&gt;
Signed-off-by: Matt Fleming &lt;matt.fleming@intel.com&gt;
</content>
</entry>
<entry>
<title>efi: Build EFI stub with EFI-appropriate options</title>
<updated>2012-09-17T12:29:21Z</updated>
<author>
<name>Matthew Garrett</name>
</author>
<published>2012-07-26T22:00:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9dead5bbb825d7c25c0400e61de83075046322d0'/>
<id>urn:sha1:9dead5bbb825d7c25c0400e61de83075046322d0</id>
<content type='text'>
We can't assume the presence of the red zone while we're still in a boot
services environment, so we should build with -fno-red-zone to avoid
problems. Change the size of wchar at the same time to make string handling
simpler.

Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Signed-off-by: Matt Fleming &lt;matt.fleming@intel.com&gt;
</content>
</entry>
<entry>
<title>X86: Improve GOP detection in the EFI boot stub</title>
<updated>2012-09-17T12:29:20Z</updated>
<author>
<name>Matthew Garrett</name>
</author>
<published>2012-07-26T22:00:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=38cb5ef4473c6f510fae3a00bdac3acd550e3796'/>
<id>urn:sha1:38cb5ef4473c6f510fae3a00bdac3acd550e3796</id>
<content type='text'>
We currently use the PCI IO protocol as a proxy for a functional GOP. This
is less than ideal, since some platforms will put the GOP on output devices
rather than the GPU itself. Move to using the conout protocol. This is not
guaranteed per-spec, but is part of the consplitter implementation that
causes this problem in the first place and so should be reliable.

Signed-off-by: Matthew Garrett &lt;mjg@redhat.com&gt;
Signed-off-by: Matt Fleming &lt;matt.fleming@intel.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'x86-efi-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip</title>
<updated>2012-07-26T20:13:25Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2012-07-26T20:13:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=0a2fe19ccc4bc552a8083a595a3aa737b8bea727'/>
<id>urn:sha1:0a2fe19ccc4bc552a8083a595a3aa737b8bea727</id>
<content type='text'>
Pul x86/efi changes from Ingo Molnar:
 "This tree adds an EFI bootloader handover protocol, which, once
  supported on the bootloader side, will make bootup faster and might
  result in simpler bootloaders.

  The other change activates the EFI wall clock time accessors on x86-64
  as well, instead of the legacy RTC readout."

* 'x86-efi-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  x86, efi: Handover Protocol
  x86-64/efi: Use EFI to deal with platform wall clock
</content>
</entry>
<entry>
<title>x86, boot: Exclude cmdline.c if you can't use it</title>
<updated>2012-07-21T18:07:39Z</updated>
<author>
<name>Gokul Caushik</name>
</author>
<published>2012-07-20T01:04:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bd448d4d0a1bd88dc6fdc41217b2c25383fa8529'/>
<id>urn:sha1:bd448d4d0a1bd88dc6fdc41217b2c25383fa8529</id>
<content type='text'>
CONFIG_EARLY_PRINTK is the only feature that might use command line
parsing in the decompression stage.  If it is disabled then we can
exclude the related code to save space. This can result in an estimated
space savings of 2240 bytes from the compressed kernel image.

Signed-off-by: Joe Millenbach &lt;jmillenbach@gmail.com&gt;
Link: http://lkml.kernel.org/r/1342746282-28497-8-git-send-email-jmillenbach@gmail.com
Signed-off-by: Gokul Caushik &lt;caushik1@gmail.com&gt;
Reviewed-by: Josh Triplett &lt;josh@joshtriplett.org&gt;
Signed-off-by: H. Peter Anvin &lt;hpa@zytor.com&gt;
</content>
</entry>
<entry>
<title>x86, boot: Exclude early_serial_console.c if can't use it.</title>
<updated>2012-07-21T18:07:34Z</updated>
<author>
<name>Joe Millenbach</name>
</author>
<published>2012-07-20T01:04:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cec49df9d331feaa2fea3d24c07147c7659940d1'/>
<id>urn:sha1:cec49df9d331feaa2fea3d24c07147c7659940d1</id>
<content type='text'>
Removes early_serial_console.c code if we don't have the config option that
enables it (EARLY_PRINTK). When disabling this code, make early_serial_base a
constant 0 to allow the compiler to optimize away the code that checks for
early_serial_base.

Signed-off-by: Joe Millenbach &lt;jmillenbach@gmail.com&gt;
Link: http://lkml.kernel.org/r/1342746282-28497-7-git-send-email-jmillenbach@gmail.com
Signed-off-by: Gokul Caushik &lt;caushik1@gmail.com&gt;
Reviewed-by: Josh Triplett &lt;josh@joshtriplett.org&gt;
Signed-off-by: H. Peter Anvin &lt;hpa@zytor.com&gt;
</content>
</entry>
</feed>
