<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic BIOS R0200J3 BUG in ACPI DSDT TO(L)UD definition in PCs &amp; Accessories</title>
    <link>https://community.sony.ie/t5/pcs-accessories/bios-r0200j3-bug-in-acpi-dsdt-to-l-ud-definition/m-p/45695#M59428</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a bug in the R0200J3 ACPI DSDT. It erroneously defines the PCI Configuration Space register TOLUD for the PCI root bridge (\_SB.PCI0.(HBUS.)TOUD) as 6 bits wide instead of 5. This register reports the address of the top of usable RAM which is used in \_SB.PCI0._CRS() to return a package to the host that includes the calculated size of RAM in the DWordRange ResourceProducer AddressRangeMemory \_SB.PCI0.BUF0._X0D.&lt;BR /&gt;&lt;BR /&gt;&lt;PRE&gt;OperationRegion (HBUS, PCI_Config, 0x40, 0xC0)&lt;BR /&gt;Field (HBUS, DWordAcc, NoLock, Preserve)&lt;BR /&gt;{&lt;BR /&gt;  // ...             &lt;BR /&gt;  Offset (0x5C),  // 0x5C + base 0x40 = offset 0x9C in PCI Config&lt;BR /&gt;            ,   3, &lt;BR /&gt;  TOUD,   6 // Intel Mobile 945 Express TOLUD register&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;// ...&lt;BR /&gt;&lt;BR /&gt;Method (_CRS, 0, Serialized)&lt;BR /&gt;{&lt;BR /&gt;  // ...&lt;BR /&gt;  CreateDWordField (BUF0, \_SB.PCI0._X0D._MIN, M1MN)&lt;BR /&gt;  CreateDWordField (BUF0, \_SB.PCI0._X0D._MAX, M1MX)&lt;BR /&gt;  CreateDWordField (BUF0, \_SB.PCI0._X0D._LEN, M1LN)&lt;BR /&gt;  ShiftLeft (TOUD, 0x1B, M1MN)&lt;BR /&gt;  Add (Subtract (M1MX, M1MN), One, M1LN)&lt;BR /&gt;  Return (BUF0)&lt;BR /&gt;}&lt;BR /&gt;&lt;/PRE&gt;&lt;BR /&gt;PCIO is the root bridge in the Mobile Intel® 945 Express Chip-set. According to the data-sheet at 5.1.26:&lt;BR /&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;TOLUD - Top of Low Used DRAM Register - bits 7:3&lt;BR /&gt;&lt;BR /&gt;B/D/F/Type:     0/0/0/PCI&lt;BR /&gt;Address Offset: 9Ch&lt;BR /&gt;Default Value:  08h&lt;BR /&gt;Access:         R/W/L; RO&lt;BR /&gt;Size:           8 bits&lt;BR /&gt;&lt;BR /&gt;This 8-bit register defines the Top of Usable Dram. Graphics Stolen Memory and TSEG&lt;BR /&gt;are within dram space defined under TOLUD. From the top of low used dram, (G)MCH&lt;BR /&gt;claims 1 to 64 MBs of DRAM for internal graphics if enabled and 1, 2 or 8 MBs of DRAM&lt;BR /&gt;for TSEG if enabled.&lt;BR /&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;Depending on how the host OS ACPI core interprets the Field FieldUnit declarations, this could result in a bit from the following register, SMRAM, being interpreted as part of the TOLUD value. If the interpreter discards illegal bit-widths the entire register (value) could be ignored.&lt;BR /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Jul 2008 18:30:47 GMT</pubDate>
    <dc:creator>IntuitiveNipple</dc:creator>
    <dc:date>2008-07-18T18:30:47Z</dc:date>
    <item>
      <title>BIOS R0200J3 BUG in ACPI DSDT TO(L)UD definition</title>
      <link>https://community.sony.ie/t5/pcs-accessories/bios-r0200j3-bug-in-acpi-dsdt-to-l-ud-definition/m-p/45695#M59428</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is a bug in the R0200J3 ACPI DSDT. It erroneously defines the PCI Configuration Space register TOLUD for the PCI root bridge (\_SB.PCI0.(HBUS.)TOUD) as 6 bits wide instead of 5. This register reports the address of the top of usable RAM which is used in \_SB.PCI0._CRS() to return a package to the host that includes the calculated size of RAM in the DWordRange ResourceProducer AddressRangeMemory \_SB.PCI0.BUF0._X0D.&lt;BR /&gt;&lt;BR /&gt;&lt;PRE&gt;OperationRegion (HBUS, PCI_Config, 0x40, 0xC0)&lt;BR /&gt;Field (HBUS, DWordAcc, NoLock, Preserve)&lt;BR /&gt;{&lt;BR /&gt;  // ...             &lt;BR /&gt;  Offset (0x5C),  // 0x5C + base 0x40 = offset 0x9C in PCI Config&lt;BR /&gt;            ,   3, &lt;BR /&gt;  TOUD,   6 // Intel Mobile 945 Express TOLUD register&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;// ...&lt;BR /&gt;&lt;BR /&gt;Method (_CRS, 0, Serialized)&lt;BR /&gt;{&lt;BR /&gt;  // ...&lt;BR /&gt;  CreateDWordField (BUF0, \_SB.PCI0._X0D._MIN, M1MN)&lt;BR /&gt;  CreateDWordField (BUF0, \_SB.PCI0._X0D._MAX, M1MX)&lt;BR /&gt;  CreateDWordField (BUF0, \_SB.PCI0._X0D._LEN, M1LN)&lt;BR /&gt;  ShiftLeft (TOUD, 0x1B, M1MN)&lt;BR /&gt;  Add (Subtract (M1MX, M1MN), One, M1LN)&lt;BR /&gt;  Return (BUF0)&lt;BR /&gt;}&lt;BR /&gt;&lt;/PRE&gt;&lt;BR /&gt;PCIO is the root bridge in the Mobile Intel® 945 Express Chip-set. According to the data-sheet at 5.1.26:&lt;BR /&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;TOLUD - Top of Low Used DRAM Register - bits 7:3&lt;BR /&gt;&lt;BR /&gt;B/D/F/Type:     0/0/0/PCI&lt;BR /&gt;Address Offset: 9Ch&lt;BR /&gt;Default Value:  08h&lt;BR /&gt;Access:         R/W/L; RO&lt;BR /&gt;Size:           8 bits&lt;BR /&gt;&lt;BR /&gt;This 8-bit register defines the Top of Usable Dram. Graphics Stolen Memory and TSEG&lt;BR /&gt;are within dram space defined under TOLUD. From the top of low used dram, (G)MCH&lt;BR /&gt;claims 1 to 64 MBs of DRAM for internal graphics if enabled and 1, 2 or 8 MBs of DRAM&lt;BR /&gt;for TSEG if enabled.&lt;BR /&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;Depending on how the host OS ACPI core interprets the Field FieldUnit declarations, this could result in a bit from the following register, SMRAM, being interpreted as part of the TOLUD value. If the interpreter discards illegal bit-widths the entire register (value) could be ignored.&lt;BR /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2008 18:30:47 GMT</pubDate>
      <guid>https://community.sony.ie/t5/pcs-accessories/bios-r0200j3-bug-in-acpi-dsdt-to-l-ud-definition/m-p/45695#M59428</guid>
      <dc:creator>IntuitiveNipple</dc:creator>
      <dc:date>2008-07-18T18:30:47Z</dc:date>
    </item>
  </channel>
</rss>

