On Fri, 24 Mar 2017, Enric Balletbo i Serra wrote:
> From: Vic Yang
>
> For SPI, we can get up to 32 additional bytes for response preamble.
> The current overhead (2 bytes) may cause problems when we try to receive
> a big response. Update it to 32 bytes.
>
> Without this fix we could see a ke
On Mon, 03 Apr 2017, Enric Balletbo i Serra wrote:
>
>
> On 03/04/17 16:30, Lee Jones wrote:
> > On Mon, 03 Apr 2017, Lee Jones wrote:
> >
> >> On Fri, 24 Mar 2017, Enric Balletbo i Serra wrote:
> >>
> >>> From: Vic Yang
> >>>
> >>> For SPI, we can get up to 32 additional bytes for response pr
On 03/04/17 16:30, Lee Jones wrote:
> On Mon, 03 Apr 2017, Lee Jones wrote:
>
>> On Fri, 24 Mar 2017, Enric Balletbo i Serra wrote:
>>
>>> From: Vic Yang
>>>
>>> For SPI, we can get up to 32 additional bytes for response preamble.
>>> The current overhead (2 bytes) may cause problems when we tr
On Mon, 03 Apr 2017, Lee Jones wrote:
> On Fri, 24 Mar 2017, Enric Balletbo i Serra wrote:
>
> > From: Vic Yang
> >
> > For SPI, we can get up to 32 additional bytes for response preamble.
> > The current overhead (2 bytes) may cause problems when we try to receive
> > a big response. Update it
On Fri, 24 Mar 2017, Enric Balletbo i Serra wrote:
> From: Vic Yang
>
> For SPI, we can get up to 32 additional bytes for response preamble.
> The current overhead (2 bytes) may cause problems when we try to receive
> a big response. Update it to 32 bytes.
>
> Without this fix we could see a ke
From: Vic Yang
For SPI, we can get up to 32 additional bytes for response preamble.
The current overhead (2 bytes) may cause problems when we try to receive
a big response. Update it to 32 bytes.
Without this fix we could see a kernel BUG when we receive a big response
from the Chrome EC when is
6 matches
Mail list logo
