On Fri, May 18, 2018 at 1:41 PM, Sam Ravnborg wrote:
> Hi Andrey.
>
> On Thu, May 17, 2018 at 01:58:33PM -0700, Andrey Smirnov wrote:
>> There's already a function that implement necessary arithemtic to find
>> offset within page table for a given address, so make use of it
>> instead of re-implem
On Fri, May 18, 2018 at 04:41:29PM -0400, Vivien Didelot wrote:
> When a SoC such as VF610 has no addresses programmed for both its
> interfaces, the "No MAC address set" warning can be confusing:
>
> booting 'net'
> WARNING: net: warning: No MAC address set. Using random address
> a2:e8:
When a SoC such as VF610 has no addresses programmed for both its
interfaces, the "No MAC address set" warning can be confusing:
booting 'net'
WARNING: net: warning: No MAC address set. Using random address
a2:e8:be:79:72:01
WARNING: net: warning: No MAC address set. Using random addr
Hi Andrey.
On Thu, May 17, 2018 at 01:58:33PM -0700, Andrey Smirnov wrote:
> There's already a function that implement necessary arithemtic to find
> offset within page table for a given address, so make use of it
> instead of re-implementing it again.
>
> Signed-off-by: Andrey Smirnov
> ---
>
Hi Sam,
Sam Ravnborg writes:
> On Fri, May 18, 2018 at 02:06:36PM -0400, Vivien Didelot wrote:
>> When a SoC such as VF610 has no addresses programmed for both its
>> interfaces, the "No MAC address set" warning can be confusing:
>>
>> booting 'net'
>> WARNING: net: warning: No MAC addr
On Thu, May 17, 2018 at 01:58:32PM -0700, Andrey Smirnov wrote:
> If address passed arm_create_pte() is not 1M (PGDIR_SIZE) aligned,
> page table that is created will end up having unexpected mapping
> offset, breaking "1:1 mapping" assumption and leading to bugs that are
> not immediately obvious
Hi Vivien
On Fri, May 18, 2018 at 02:06:36PM -0400, Vivien Didelot wrote:
> When a SoC such as VF610 has no addresses programmed for both its
> interfaces, the "No MAC address set" warning can be confusing:
>
> booting 'net'
> WARNING: net: warning: No MAC address set. Using random addres
When a SoC such as VF610 has no addresses programmed for both its
interfaces, the "No MAC address set" warning can be confusing:
booting 'net'
WARNING: net: warning: No MAC address set. Using random address
a2:e8:be:79:72:01
WARNING: net: warning: No MAC address set. Using random addr
Hi, Sascha,
On Fri, May 18, 2018 at 07:57:34AM +0200, Sascha Hauer wrote:
> On Thu, May 17, 2018 at 04:58:48PM +0300, Peter Mamonov wrote:
> > Signed-off-by: Peter Mamonov
> > ---
> > arch/mips/include/asm/dma-mapping.h | 2 +-
> > arch/mips/include/asm/io.h | 4 ++--
> > arch/mips/li
Hi Sascha,
On Tue, 2018-04-03 at 09:48 +0200, Sascha Hauer wrote:
[...]
> -static int tftp_stat(struct device_d *dev, const char *filename, struct stat
> *s)
> +static struct dentry *tftp_lookup(struct inode *dir, struct dentry *dentry,
> + unsigned int flags)
> {
> -
Hi, Andrey,
On Thu, May 17, 2018 at 02:50:58PM -0700, Andrey Smirnov wrote:
> On Thu, May 17, 2018 at 6:58 AM, Peter Mamonov wrote:
> > Signed-off-by: Peter Mamonov
> > ---
> > common/resource.c | 4
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/common/resource.c b/common/resour
The eccsteps where set wrong for OMAP_ECC_BCH8_CODE_HW_ROMCODE.
So the ECC was only corrected for the first 512 bytes chunk of a 2k page.
Moved out the ecc step iteration out of the correcting loop to make
it more alike the generic nand functions. And made sure that
the ECC is caclulated for all c
12 matches
Mail list logo
