On Tue, Mar 01, 2022 at 09:13:04PM +0200, Liav Albani wrote:
>
> On 3/1/22 13:21, Michael S. Tsirkin wrote:
> > On Tue, Mar 01, 2022 at 08:29:57AM +0530, Ani Sinha wrote:
> > >
> > > On Mon, 28 Feb 2022, Liav Albani wrote:
> > >
> > > > After changing the IAPC boot flags register to indicate sup
On Wed, Mar 2, 2022 at 12:43 AM Liav Albani wrote:
>
>
> On 3/1/22 13:21, Michael S. Tsirkin wrote:
> > On Tue, Mar 01, 2022 at 08:29:57AM +0530, Ani Sinha wrote:
> >>
> >> On Mon, 28 Feb 2022, Liav Albani wrote:
> >>
> >>> After changing the IAPC boot flags register to indicate support of i8042
>
On 3/1/22 13:21, Michael S. Tsirkin wrote:
On Tue, Mar 01, 2022 at 08:29:57AM +0530, Ani Sinha wrote:
On Mon, 28 Feb 2022, Liav Albani wrote:
After changing the IAPC boot flags register to indicate support of i8042
in the machine chipset to help the guest OS to determine its existence
"fast
On Tue, Mar 01, 2022 at 08:29:57AM +0530, Ani Sinha wrote:
>
>
> On Mon, 28 Feb 2022, Liav Albani wrote:
>
> > After changing the IAPC boot flags register to indicate support of i8042
> > in the machine chipset to help the guest OS to determine its existence
> > "faster", we need to have the upd
On Mon, 28 Feb 2022, Liav Albani wrote:
> After changing the IAPC boot flags register to indicate support of i8042
> in the machine chipset to help the guest OS to determine its existence
> "faster", we need to have the updated FACP ACPI binary images in tree.
>
> @@ -1,32 +1,32 @@
> /*
> *
After changing the IAPC boot flags register to indicate support of i8042
in the machine chipset to help the guest OS to determine its existence
"faster", we need to have the updated FACP ACPI binary images in tree.
@@ -1,32 +1,32 @@
/*
* Intel ACPI Component Architecture
* AML/ASL+ Disassembl
