Hi Gary, Le jeudi 14 juin 2012 à 10:07 -0700, Gary Hade a écrit : > On Thu, Jun 14, 2012 at 10:35:11AM +0200, Jean Delvare wrote: > > I see it as a firmware bug, nothing else > > That was my strong feeling but since the number of sightings > seems to be on the increase, I thought it might be good to talk > about whether our interpretation is actually correct. It's always good to ensure we got things right, sure. WRT to the number of faulty systems, I wouldn't jump to any conclusion. It is sufficient to have a bug in the reference BIOS code in order to see the same bug spread across boards and vendors all around. > > (although I am still waiting > > for Asus to reply on this.) And if it really isn't a bug, I can only > > read it as "we have a 32-bit register that can only be read 8-bit at a > > time so please issue 4 8-bit reads and build up a 32-bit value out of > > these." And certainly not as "don't touch the upper 24-bits." > > It will definitely be interesting to see what you hear from Asus. If I ever hear something... No news yet :( > Multiple reads or writes to access all the bits in a register > does _not_ sound like a reasonable interpretation of the ACPI > spec to me. Well, I can imagine that some hardware has (or has had) such limitations, and the ACPI spec authors may have wanted to play it safe and make it possible to describe this case. I didn't mean that I expect it to be the case for my Asus board - I still believe it is a simple BIOS bug here. -- Jean Delvare Suse L3 -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
