On Thursday, June 27, 2019 at 1:04:52 AM UTC-4, דור לאור wrote:
>
> Just out of curiosity, why Hpet? it's a rarely used clock source.
>
It is rarely used in production. And it sucks especially with 32-bit
counter. But unfortunately, it is the only clock provided by hyperkit which
in turn uses A
On Thu, Jun 27, 2019 at 7:30 AM Waldemar Kozaczuk
wrote:
> This patch adds very limited support of hpets
> with 32-bit main counter. It also refactors
> the hpet code to allow for future refinements
> of both 32-bit and 64-bit implementations
> independently.
>
Can you please give here, and/or i
Just out of curiosity, why Hpet? it's a rarely used clock source.
On Wed, Jun 26, 2019 at 9:30 PM Waldemar Kozaczuk
wrote:
> This patch adds very limited support of hpets
> with 32-bit main counter. It also refactors
> the hpet code to allow for future refinements
> of both 32-bit and 64-bit imp
This patch adds very limited support of hpets
with 32-bit main counter. It also refactors
the hpet code to allow for future refinements
of both 32-bit and 64-bit implementations
independently.
Signed-off-by: Waldemar Kozaczuk
---
drivers/hpet.cc | 54 +
