{"push_id":1811663368,"size":1,"distinct_size":1,"ref":"refs/heads/attribRawProcessBytes","head":"d28f6c2927053d85f33780b66c0d9050f0e30d3a","before":"8819a31c85bded0ebbdf130e18acb20706a9e4cf","commits":[{"sha":"d28f6c2927053d85f33780b66c0d9050f0e30d3a","author":{"name":"Benjamin Tissoires","email":"ace37d3dd488d1f8efb492bba0263a7c3c3d861c@redhat.com"},"message":"Executer: adapt buffer length for Field Attrib Raw Process in Ops Region\n\nDetected on the Surface 3:\nThe MSHW0011 driver uses Field Attrib Raw Process to return information\nfor the ACPI Battery. The DSDT declares a parameter of 2 though\nfunctions like _BST or _BIX require a much bigger out buffer.\n\nIt looks like the incoming buffer has the requested size and we can\nwork around the issue by using this input size as the output and\nparameters size.\n\nAs mentioned by Stephen Just on the kernel bugzilla (comment 44):\n\"Lv, after reading through 5.5.2.4.5.3 of the ACPI spec several times,\nit appears that AccessLength is ignored for AttribRawProcessBytes\naccesses - the access length is always specified by the user - and\nin fact, the example omits the AccessLength argument entirely.\n\nMore specifically, comparing 5.5.2.4.5.3.9 and 5.5.2.4.5.3.10, it\nappears that the only difference between AttribRawProcessBytes and\nAttribRawBytes is that AttribRawProcessBytes does not seem to pay\nattention to AccessLength, and lets the driver deal with it.\"\n\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=106231\n\nSigned-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>","distinct":true,"url":"https://api.github.com/repos/bentiss/acpica/commits/d28f6c2927053d85f33780b66c0d9050f0e30d3a"}]}
{"actor":{"display_login":"bentiss"}}