On Saturday, October 10, 2015 at 02:21:24 PM, Thomas Chou wrote:
> Hi Marek,
Hi!
> On 10/09/2015 10:39 PM, Marek Vasut wrote:
> >> It might be awful to use the maximum value all the time. See, we flush
> >> cache for every eth packet!
> >
> > You should only flush the part where the packet is lo
Hi Marek,
On 10/09/2015 10:39 PM, Marek Vasut wrote:
It might be awful to use the maximum value all the time. See, we flush
cache for every eth packet!
You should only flush the part where the packet is located ;-) I finally
have the MAX10 kit, so I can check the ethernet at least :)
Sure. W
On Friday, October 09, 2015 at 11:03:36 AM, Thomas Chou wrote:
> Hi Marek,
Hi,
> On 10/09/2015 05:14 AM, Marek Vasut wrote:
> > Did I miss the DT part somewhere or is that not part of this patch ?
>
> As we are just barely starting from reset, there is no luxury of DT.
> After this, DT will be u
Hi Marek,
On 10/09/2015 05:14 AM, Marek Vasut wrote:
Did I miss the DT part somewhere or is that not part of this patch ?
As we are just barely starting from reset, there is no luxury of DT.
After this, DT will be used with the cache flush patch.
Another question I have is -- why don't we
On Tuesday, October 06, 2015 at 10:21:48 AM, Thomas Chou wrote:
> Set default icache and dcache configuration for start.S.
> The values are chosen so that it will work for most configurations.
> During initialization, cpu information will be extracted from
> device tree. Then cache flush operations
Set default icache and dcache configuration for start.S.
The values are chosen so that it will work for most configurations.
During initialization, cpu information will be extracted from
device tree. Then cache flush operations will have correct
cache configurations.
Signed-off-by: Thomas Chou
--
6 matches
Mail list logo
