lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251216142708.14727-1-vgrinber@redhat.com>
Date: Tue, 16 Dec 2025 16:27:08 +0200
From: Vitaly Grinberg <vgrinber@...hat.com>
To: grzegorz.nitka@...el.com
Cc: aleksandr.loktionov@...el.com,
	anthony.l.nguyen@...el.com,
	arkadiusz.kubalewski@...el.com,
	horms@...nel.org,
	intel-wired-lan@...ts.osuosl.org,
	linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org,
	pmenzel@...gen.mpg.de,
	przemyslaw.kitszel@...el.com
Subject: Re:[Intel-wired-lan] [PATCH v5 iwl-next] ice: add support for unmanaged DPLL on E830 NIC

Will a notification be provided when the lock is re-acquired?

Another concern is the absence of periodical pin notifications. With the E810, users received the active pin notifications every 1 second. However, the unmanaged DPLL appears to lack this functionality. User implementations currently rely on these periodical notifications to derive the overall clock state, metrics and events from the phase offset. It seems that unmanaged DPLL users will be forced to support two distinct types of DPLLs: one that sends periodical pin notifications and one that does not. Crucially, this difference does not appear to be reflected in the device capabilities, meaning users cannot know in advance whether to expect these notifications.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ