Re: [PATCH 1/2] nand: imx6: Changed default NAND clock

2016-10-25 Thread Sascha Hauer
On Thu, Oct 20, 2016 at 03:40:06PM +0200, Christian Hemp wrote: > From: Daniel Schultz > > The Barebox recognized false bad erase blocks while booting from a > Spansion NAND (1). This error occurred due a to high clock. The > Kernel sets the default NAND clock to 22Mhz. So,

Re: [PATCH 1/2] nand: imx6: Changed default NAND clock

2016-10-24 Thread Stefan Lengfeld
Hi Sascha, On Fri, Oct 21, 2016 at 09:11:47AM +0200, Sascha Hauer wrote: > On Thu, Oct 20, 2016 at 03:40:06PM +0200, Christian Hemp wrote: > > From: Daniel Schultz > > > > The Barebox recognized false bad erase blocks while booting from a > > Spansion NAND (1). This error

Re: [PATCH 1/2] nand: imx6: Changed default NAND clock

2016-10-21 Thread Sascha Hauer
On Thu, Oct 20, 2016 at 03:40:06PM +0200, Christian Hemp wrote: > From: Daniel Schultz > > The Barebox recognized false bad erase blocks while booting from a > Spansion NAND (1). This error occurred due a to high clock. The > Kernel sets the default NAND clock to 22Mhz. So,

[PATCH 1/2] nand: imx6: Changed default NAND clock

2016-10-20 Thread Christian Hemp
From: Daniel Schultz The Barebox recognized false bad erase blocks while booting from a Spansion NAND (1). This error occurred due a to high clock. The Kernel sets the default NAND clock to 22Mhz. So, to fix this error and to be more identical with the Kernel, the Barebox