On Fri, 2018-11-16 at 14:25:49 UTC, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> The current Cadence QSPI driver caused a kernel panic sporadically
> when writing to QSPI. The problem was caused by writing more bytes
> than needed because the QSPI operated on 4 bytes at a time.
>
On Fri, 2018-11-16 at 14:25:49 UTC, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> The current Cadence QSPI driver caused a kernel panic sporadically
> when writing to QSPI. The problem was caused by writing more bytes
> than needed because the QSPI operated on 4 bytes at a time.
>
From: Thor Thayer
The current Cadence QSPI driver caused a kernel panic sporadically
when writing to QSPI. The problem was caused by writing more bytes
than needed because the QSPI operated on 4 bytes at a time.
[ 11.202044] Unable to handle kernel paging request at virtual address
bffd3000
From: Thor Thayer
The current Cadence QSPI driver caused a kernel panic sporadically
when writing to QSPI. The problem was caused by writing more bytes
than needed because the QSPI operated on 4 bytes at a time.
[ 11.202044] Unable to handle kernel paging request at virtual address
bffd3000
On Mon, 26 Mar 2018 09:12:17 -0500
thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> The current Cadence QSPI driver caused a kernel panic when loading
> a Root Filesystem from QSPI. The problem was caused by reading more
> bytes than needed because the
On Mon, 26 Mar 2018 09:12:17 -0500
thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> The current Cadence QSPI driver caused a kernel panic when loading
> a Root Filesystem from QSPI. The problem was caused by reading more
> bytes than needed because the QSPI operated on 4 bytes at a
On 04/11/2018 05:17 PM, Thor Thayer wrote:
> Hi. Any comments on this patch?
None other than
Reviewed-by: Marek Vasut
sorry for the delay.
btw stop top-posting please.
> On 03/26/2018 09:12 AM, thor.tha...@linux.intel.com wrote:
>> From: Thor Thayer
On 04/11/2018 05:17 PM, Thor Thayer wrote:
> Hi. Any comments on this patch?
None other than
Reviewed-by: Marek Vasut
sorry for the delay.
btw stop top-posting please.
> On 03/26/2018 09:12 AM, thor.tha...@linux.intel.com wrote:
>> From: Thor Thayer
>>
>> The current Cadence QSPI driver
Hi. Any comments on this patch?
On 03/26/2018 09:12 AM, thor.tha...@linux.intel.com wrote:
From: Thor Thayer
The current Cadence QSPI driver caused a kernel panic when loading
a Root Filesystem from QSPI. The problem was caused by reading more
bytes than needed
Hi. Any comments on this patch?
On 03/26/2018 09:12 AM, thor.tha...@linux.intel.com wrote:
From: Thor Thayer
The current Cadence QSPI driver caused a kernel panic when loading
a Root Filesystem from QSPI. The problem was caused by reading more
bytes than needed because the QSPI operated on 4
From: Thor Thayer
The current Cadence QSPI driver caused a kernel panic when loading
a Root Filesystem from QSPI. The problem was caused by reading more
bytes than needed because the QSPI operated on 4 bytes at a time.
[7.947754] spi_nor_read[1048]:from
From: Thor Thayer
The current Cadence QSPI driver caused a kernel panic when loading
a Root Filesystem from QSPI. The problem was caused by reading more
bytes than needed because the QSPI operated on 4 bytes at a time.
[7.947754] spi_nor_read[1048]:from 0x037cad74, len 1 [bfe07fff]
[
12 matches
Mail list logo