Nice fix.
ok yasuoka
On Sat, 23 Apr 2016 15:55:21 +0200 (CEST)
Mark Kettenis wrote:
>> Date: Sat, 23 Apr 2016 08:25:22 -0400
>> From: Kenneth Westerback
>>
>> > And here is a possible fix. Got the inspiration from the SYSLINUX
>> > bootloader. This forces alignment of the EFI-specific 64-bit
On 4/23/16 10:09 AM, Kenneth Westerback wrote:
On 23 April 2016 at 09:55, Mark Kettenis wrote:
Date: Sat, 23 Apr 2016 08:25:22 -0400
From: Kenneth Westerback
And here is a possible fix. Got the inspiration from the SYSLINUX
bootloader. This forces alignment of the EFI-specific 64-bit types
On 23 April 2016 at 09:55, Mark Kettenis wrote:
>> Date: Sat, 23 Apr 2016 08:25:22 -0400
>> From: Kenneth Westerback
>>
>> > And here is a possible fix. Got the inspiration from the SYSLINUX
>> > bootloader. This forces alignment of the EFI-specific 64-bit types.
>> > It leaves the normal int64
> Date: Sat, 23 Apr 2016 08:25:22 -0400
> From: Kenneth Westerback
>
> > And here is a possible fix. Got the inspiration from the SYSLINUX
> > bootloader. This forces alignment of the EFI-specific 64-bit types.
> > It leaves the normal int64_t/uint64_t alone, but we shouldn't use
> > those dire
On 23 April 2016 at 07:51, Mark Kettenis wrote:
>> Date: Sat, 23 Apr 2016 13:23:49 +0200 (CEST)
>> From: Mark Kettenis
>>
>> > Date: Sat, 23 Apr 2016 12:49:25 +0200 (CEST)
>> > From: Mark Kettenis
>> >
>> > > Could it be this problem is related to
>> > > sys/arch/amd64/stand/efi/include/i386/efi
> Date: Sat, 23 Apr 2016 13:23:49 +0200 (CEST)
> From: Mark Kettenis
>
> > Date: Sat, 23 Apr 2016 12:49:25 +0200 (CEST)
> > From: Mark Kettenis
> >
> > > Could it be this problem is related to
> > > sys/arch/amd64/stand/efi/include/i386/efibind.h using sys/stdint.h
> > > which looks like it wil
> Date: Sat, 23 Apr 2016 12:49:25 +0200 (CEST)
> From: Mark Kettenis
>
> > Could it be this problem is related to
> > sys/arch/amd64/stand/efi/include/i386/efibind.h using sys/stdint.h
> > which looks like it will make uint64_t unsigned long on for BOOTIA32.EFI
> > not unsigned long long?
>
> We
> Date: Sat, 23 Apr 2016 19:27:59 +1000
> From: Jonathan Gray
>
> The 100s is 32 bit uefi only. It requires BOOTIA32.EFI. The
> problems linux has are related to them communicating with the uefi
> runtime after the kernel has booted.
I suppose we will have the same issue once we will have code
w.
>
> I hope a uefi guru (i.e. someone who has a better grasp on the issue
> than my 10 minutes of googling has given me. :-)) can provide more
> information.
>
> Ken
>
>
> On 22 April 2016 at 11:01, wrote:
> >>Synopsis: efiboot ca
s: efiboot can't find OpenBSD GPT partition on Lenovo Ideapad 100s
>>Category: amd64
>>Environment:
> System : OpenBSD 5.9
> Details : OpenBSD 5.9-current (GENERIC.MP) #1983: Mon Apr 4
> 21:50:41 MDT 2016
>
&
>Synopsis: efiboot can't find OpenBSD GPT partition on Lenovo Ideapad 100s
>Category: amd64
>Environment:
System : OpenBSD 5.9
Details : OpenBSD 5.9-current (GENERIC.MP) #1983: Mon Apr 4
21:50:41 MDT 2016
dera...@amd64.op
11 matches
Mail list logo
