On Mon, 26 Mar 2018 17:35:00 +0200, Jani Nikula
wrote:
On Mon, 26 Mar 2018, Michał Winiarski wrote:
On Fri, Mar 23, 2018 at 02:47:23PM +, Michal Wajdeczko wrote:
Instead of returning small data in response status dword,
GuC may
On Mon, 26 Mar 2018 17:29:32 +0200, Michał Winiarski
wrote:
On Fri, Mar 23, 2018 at 02:47:23PM +, Michal Wajdeczko wrote:
Instead of returning small data in response status dword,
GuC may append longer data as response message payload.
If caller provides
On Mon, 26 Mar 2018, Michał Winiarski wrote:
> On Fri, Mar 23, 2018 at 02:47:23PM +, Michal Wajdeczko wrote:
>> Instead of returning small data in response status dword,
>> GuC may append longer data as response message payload.
>> If caller provides response
On Fri, Mar 23, 2018 at 02:47:23PM +, Michal Wajdeczko wrote:
> Instead of returning small data in response status dword,
> GuC may append longer data as response message payload.
> If caller provides response buffer, we will copy received
> data and use number of received data dwords as new
On 3/23/2018 7:47 AM, Michal Wajdeczko wrote:
Instead of returning small data in response status dword,
GuC may append longer data as response message payload.
If caller provides response buffer, we will copy received
data and use number of received data dwords as new success
return value. We
Instead of returning small data in response status dword,
GuC may append longer data as response message payload.
If caller provides response buffer, we will copy received
data and use number of received data dwords as new success
return value. We will WARN if response from GuC does not
match