On Mon, Jul 20, 2015 at 02:21:00AM +0200, Hrvoje Popovski wrote:
> On 20.7.2015. 0:53, Bob Beck wrote:
> >
>
> >>>
> >>> I'm pretty sure that's a different problem. But thanks for pointing this
> >>> out.
> >>>
> >>> -ml
> >>>
> >
> > no, just update your tree please, I just committed th
On 20.7.2015. 0:53, Bob Beck wrote:
>
>>>
>>> I'm pretty sure that's a different problem. But thanks for pointing this
>>> out.
>>>
>>> -ml
>>>
>
> no, just update your tree please, I just committed the fix
>
thank you, everything is working after your fix
On 20.7.2015. 0:06, Mark Kettenis wrote:
> The acpi code that reads and writes pci config space is quite busted.
> It always does byte-sized reads and writes even if the aml specifies
> an access size of four bytes. This made vmware unhappy, because it
> expetcs to see a magic value being written
> >>
> >
> > I'm pretty sure that's a different problem. But thanks for pointing this
> > out.
> >
> > -ml
> >
no, just update your tree please, I just committed the fix
On 20.7.2015. 0:41, Mike Larkin wrote:
> On Mon, Jul 20, 2015 at 12:38:19AM +0200, Hrvoje Popovski wrote:
>> On 20.7.2015. 0:06, Mark Kettenis wrote:
>>> The acpi code that reads and writes pci config space is quite busted.
>>> It always does byte-sized reads and writes even if the aml specifies
>>
On Mon, Jul 20, 2015 at 12:38:19AM +0200, Hrvoje Popovski wrote:
> On 20.7.2015. 0:06, Mark Kettenis wrote:
> > The acpi code that reads and writes pci config space is quite busted.
> > It always does byte-sized reads and writes even if the aml specifies
> > an access size of four bytes. This made
On 20.7.2015. 0:06, Mark Kettenis wrote:
> The acpi code that reads and writes pci config space is quite busted.
> It always does byte-sized reads and writes even if the aml specifies
> an access size of four bytes. This made vmware unhappy, because it
> expetcs to see a magic value being written
The acpi code that reads and writes pci config space is quite busted.
It always does byte-sized reads and writes even if the aml specifies
an access size of four bytes. This made vmware unhappy, because it
expetcs to see a magic value being written into a 32-bit register and
not the individual byt
