On Mon, Jul 14, 2025 at 08:08:45AM +0200, Ard Biesheuvel wrote:
> From: Ard Biesheuvel
>
> The EFI rtc driver is used by non-x86 architectures only, and exposes
> the get/set wakeup time functionality provided by the underlying
> platform. This is usually broken on most platforms, and not widely
On Mon, 14 Jul 2025 at 16:22, Demi Marie Obenour wrote:
>
> On 7/14/25 02:19, Ard Biesheuvel wrote:
> > On Mon, 14 Jul 2025 at 16:13, Demi Marie Obenour
> > wrote:
> >>
> >> On 7/14/25 02:08, Ard Biesheuvel wrote:
> >>> From: Ard Biesheuvel
> >>>
> >>> The EFI rtc driver is used by non-x86 arch
On 7/14/25 02:19, Ard Biesheuvel wrote:
> On Mon, 14 Jul 2025 at 16:13, Demi Marie Obenour
> wrote:
>>
>> On 7/14/25 02:08, Ard Biesheuvel wrote:
>>> From: Ard Biesheuvel
>>>
>>> The EFI rtc driver is used by non-x86 architectures only, and exposes
>>> the get/set wakeup time functionality provi
On Mon, 14 Jul 2025 at 16:13, Demi Marie Obenour wrote:
>
> On 7/14/25 02:08, Ard Biesheuvel wrote:
> > From: Ard Biesheuvel
> >
> > The EFI rtc driver is used by non-x86 architectures only, and exposes
> > the get/set wakeup time functionality provided by the underlying
> > platform. This is usu
On 7/14/25 02:08, Ard Biesheuvel wrote:
> From: Ard Biesheuvel
>
> The EFI rtc driver is used by non-x86 architectures only, and exposes
> the get/set wakeup time functionality provided by the underlying
> platform. This is usually broken on most platforms, and not widely used
> to begin with [if
