Hi,
On efiboot for arm64
boot> boot sd0k:bsd.rd
or
boot> set device sd0l
doesn't work properly.
The diff makes it can boot from paritions other than "a".
ok?
comments?
Index: sys/arch/arm64/arm64/autoconf.c
===
RCS file: /dis
nothing else does, and i want to clean up the code.
ok?
Index: if_trunk.c
===
RCS file: /cvs/src/sys/net/if_trunk.c,v
retrieving revision 1.137
diff -u -p -r1.137 if_trunk.c
--- if_trunk.c 12 Aug 2018 23:50:31 - 1.137
+++ i
On Tue, Jan 08, 2019 at 05:13:11PM +0100, Jeremie Courreges-Anglas wrote:
> >> reading the cvs man page I realized that there are a lot of references to
> >> the cvshome.org site , but it is not the cvs home page anymore.
>
> I remember some people being confused in the past, maybe this could be
>
> Date: Tue, 8 Jan 2019 18:02:27 +0100 (CET)
> From: Mark Kettenis
>
> > Date: Tue, 8 Jan 2019 17:46:37 +0100 (CET)
> > From: Mark Kettenis
> >
> > I have a Shuttle NC02U "nano" PC that ends up with the the acpi0
> > kernel thread blocked on the "acpievt" wait channel. I tracked this
> > down
> Date: Tue, 8 Jan 2019 17:46:37 +0100 (CET)
> From: Mark Kettenis
>
> I have a Shuttle NC02U "nano" PC that ends up with the the acpi0
> kernel thread blocked on the "acpievt" wait channel. I tracked this
> down to an incorrect implementation of the Signal() and Wait()
> operations.
>
> This c
I have a Shuttle NC02U "nano" PC that ends up with the the acpi0
kernel thread blocked on the "acpievt" wait channel. I tracked this
down to an incorrect implementation of the Signal() and Wait()
operations.
This changes the implementation to be a proper semaphore. It also
releases the acpi inte
(top-posting edited)
> On Mon, 7 Jan 2019 at 11:01, Matteo Niccoli wrote:
>
>> Hello,
>>
>> reading the cvs man page I realized that there are a lot of references to
>> the cvshome.org site , but it is not the cvs home page anymore.
I remember some people being confused in the past, maybe this
Hi,
I have written this driver that allows to access qemu's fwcfg key/value
store with the hostctl tool. At the moment, it's usefulness to me is not
very high because it uses acpi to detect the device, qemu only exposes the
device in the acpi tables in the q35 machine type, but libvirt configur