On 03/07/2017 05:45 PM, york sun wrote:
> On 03/06/2017 10:36 PM, Marek Vasut wrote:
>> On 03/07/2017 05:31 AM, york sun wrote:
>>> On 03/06/2017 07:59 PM, Marek Vasut wrote:
On 03/06/2017 06:02 PM, York Sun wrote:
> Early MMU improves performance especially on emulators. However, the
On 03/06/2017 10:36 PM, Marek Vasut wrote:
> On 03/07/2017 05:31 AM, york sun wrote:
>> On 03/06/2017 07:59 PM, Marek Vasut wrote:
>>> On 03/06/2017 06:02 PM, York Sun wrote:
Early MMU improves performance especially on emulators. However, the
early MMU is left enabled after the first
On 03/07/2017 05:31 AM, york sun wrote:
On 03/06/2017 07:59 PM, Marek Vasut wrote:
On 03/06/2017 06:02 PM, York Sun wrote:
Early MMU improves performance especially on emulators. However, the
early MMU is left enabled after the first stage of SPL boot. Instead
of flushing D-cache and dealing
On 03/06/2017 07:59 PM, Marek Vasut wrote:
> On 03/06/2017 06:02 PM, York Sun wrote:
>> Early MMU improves performance especially on emulators. However, the
>> early MMU is left enabled after the first stage of SPL boot. Instead
>> of flushing D-cache and dealing with re-enabling MMU for the
On 03/06/2017 06:02 PM, York Sun wrote:
Early MMU improves performance especially on emulators. However, the
early MMU is left enabled after the first stage of SPL boot. Instead
of flushing D-cache and dealing with re-enabling MMU for the second
stage U-Boot, disabling it for SPL build
Early MMU improves performance especially on emulators. However, the
early MMU is left enabled after the first stage of SPL boot. Instead
of flushing D-cache and dealing with re-enabling MMU for the second
stage U-Boot, disabling it for SPL build simplifies the process. The
performance penalty is
6 matches
Mail list logo
