<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Firmware on Blogue de Damien Dye</title>
    <link>https://blogs.damiendye.uk/pt/tags/firmware/</link>
    <description>Recent content in Firmware on Blogue de Damien Dye</description>
    <generator>Hugo</generator>
    <language>pt-PT</language>
    <lastBuildDate>Sun, 11 Oct 2026 17:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/pt/tags/firmware/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resolver o TSC quando o firmware está avariado</title>
      <link>https://blogs.damiendye.uk/pt/hardware/sorting-tsc-when-your-firmware-is-broken/</link>
      <pubDate>Sun, 11 Oct 2026 13:30:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/pt/hardware/sorting-tsc-when-your-firmware-is-broken/</guid>
      <description>Quatro meses a fio, cada arranque do meu ThinkPad E595 deu ao Linux um núcleo três segundos atrás dos outros sete, e o kernel trocou o TSC pelo HPET. Porque é que o Linux não o resolve em portáteis AMD, o que dizem 40 arranques de registos, como o tscsync sincroniza os contadores em UEFI, a BIOS 1.30, tsc=nowatchdog e o custo em cada convidado KVM.</description>
    </item>
  </channel>
</rss>
