Hi Jan,
On Wed, Jul 18, 2012 at 02:37:11PM +0200, Jan Weitzel wrote:
> GPMC could be already configured by xloader or rom bootloader
> Use the configured buswidth (width == 0) or set it explicit in the board file.
What happens if it hasn't been configured by the ROM or xloader, for
example when b
Hi Jan,
On Wed, Jul 18, 2012 at 02:37:12PM +0200, Jan Weitzel wrote:
> Add reset to gpmc_generic_init as proposed by TRM.
> This also fixes some strange timing issue while GPMC Initialization for
> NAND OMAP4460
>
> Signed-off-by: Jan Weitzel
> ---
> arch/arm/mach-omap/gpmc.c | 10 +-
On 17:06 Wed 18 Jul , Sascha Hauer wrote:
> Hi Sven,
>
> On Wed, Jul 18, 2012 at 11:44:29AM +0200, Stutz Sven wrote:
> >
> > Hello Sascha,
> >
> > thanks a lot for your help.
> >
> > When I completely switch off the ecc, Barebox is loading the Linux kernel.
> > But I guess that the ecc is n
Hi Sven,
On Wed, Jul 18, 2012 at 11:44:29AM +0200, Stutz Sven wrote:
>
> Hello Sascha,
>
> thanks a lot for your help.
>
> When I completely switch off the ecc, Barebox is loading the Linux kernel.
> But I guess that the ecc is necessary especially for NAND-Flash devices.
Indeed. You shouldn't
On Wed, Jul 18, 2012 at 10:46:46AM +0200, Juergen Beisert wrote:
> Many architectures support a way to detect why the bootloader is running.
> This patch adds a global variable to be able to use the cause in some kind of
> shell code to do special things on demand. For example to do an emergency
>
This configuration can be used to use barebox as
x-loader replacement.
Also the ECC-Mode is changed from SOFT to BCH8.
Signed-off-by: Juergen Kilb
---
arch/arm/boards/phycard-a-l1/pca-a-l1.c | 10 ++
arch/arm/configs/phycard_a_l1_xload_defconfig | 43 +
arch
Most of the time, a SD card was not found during probing.
This hack fixed the problem.
Further investigation needed !!
Signed-off-by: Juergen Kilb
---
drivers/mci/omap_hsmmc.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/mci/omap_hsmmc.c b/drivers/mci/omap_hs
Signed-off-by: Juergen Kilb
---
arch/arm/boards/phycard-a-l1/pca-a-l1.c |2 ++
arch/arm/mach-omap/include/mach/omap3-silicon.h |1 +
2 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boards/phycard-a-l1/pca-a-l1.c
b/arch/arm/boards/phycard-a-l1/pca-a-l1.c
i
Signed-off-by: Juergen Kilb
---
arch/arm/boards/phycard-a-l1/pca-a-l1.c | 169 +++
1 files changed, 125 insertions(+), 44 deletions(-)
diff --git a/arch/arm/boards/phycard-a-l1/pca-a-l1.c
b/arch/arm/boards/phycard-a-l1/pca-a-l1.c
index a388f63..1dc7678 100644
--- a
Add reset to gpmc_generic_init as proposed by TRM.
This also fixes some strange timing issue while GPMC Initialization for
NAND OMAP4460
Signed-off-by: Jan Weitzel
---
arch/arm/mach-omap/gpmc.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap/g
GPMC could be already configured by xloader or rom bootloader
Use the configured buswidth (width == 0) or set it explicit in the board file.
Use autodetect on pcm049
Signed-off-by: Jan Weitzel
---
arch/arm/boards/pcm049/board.c |4 ++--
arch/arm/mach-omap/devices-gpmc-nand.c | 23
If nand_scan_ident fail try to reconfigure buswidth from 8bit to 16bit or
the other way around.
There are still the ugly debug messages like:
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xb3 (Micron NAND 1GiB 1,8V 16-bit)
NAND bus width 8 instead 16 bit
No NAND device found (-22)!
NAND device: Ma
Jan Weitzel (3):
OMAP GPMC NAND: use buswidth from GPMC
gpmc: Add reset to gpmc_generic_init
mtd omap nand: reconfigure buswidth
arch/arm/boards/pcm049/board.c |4 ++--
arch/arm/mach-omap/devices-gpmc-nand.c | 23 ++-
arch/arm/mach-omap/gpmc.c
Hello Sascha,
thanks a lot for your help.
When I completely switch off the ecc, Barebox is loading the Linux kernel.
But I guess that the ecc is necessary especially for NAND-Flash devices.
The AT91SAM9263 controller has a ecc unit implemented. There are three
registers and the error calcula
On Wed, Jul 18, 2012 at 10:53:29AM +0200, Juergen Beisert wrote:
> Hi,
>
> a look into "arch/arm/boards/" offers various boards starting with the
> vendor's name in their directory name (eukrea/freescale).
> I would like to have the same for the FriendlyARM boards. Currently the
> Mini2440 and T
Hi,
a look into "arch/arm/boards/" offers various boards starting with the
vendor's name in their directory name (eukrea/freescale).
I would like to have the same for the FriendlyARM boards. Currently the
Mini2440 and Tiny210 are part of the tree and I'm still working on the
Mini6410 and Tiny64
Signed-off-by: Juergen Beisert
---
arch/arm/mach-samsung/Makefile |1 +
arch/arm/mach-samsung/reset_source.c | 56 ++
2 files changed, 57 insertions(+)
create mode 100644 arch/arm/mach-samsung/reset_source.c
diff --git a/arch/arm/mach-samsung/Makefile
Many architectures support a way to detect why the bootloader is running.
This patch adds a global variable to be able to use the cause in some kind of
shell code to do special things on demand. For example to do an emergency boot,
when the last boot fails and the watchdog reactivate the hanging sy
Signed-off-by: Juergen Beisert
---
arch/arm/mach-imx/Makefile |1 +
arch/arm/mach-imx/reset_source.c | 72 ++
2 files changed, 73 insertions(+)
create mode 100644 arch/arm/mach-imx/reset_source.c
diff --git a/arch/arm/mach-imx/Makefile b/arch/arm/
Signed-off-by: Juergen Beisert
---
drivers/watchdog/im28wd.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/watchdog/im28wd.c b/drivers/watchdog/im28wd.c
index b016910..1f987de 100644
--- a/drivers/watchdog/im28wd.c
+++ b/drivers/watchdog/im28wd.c
@@ -21,
Many architectures support a way to detect why the bootloader is running.
This patch adds a global variable to be able to use the cause in some kind of
shell code to do special things on demand. For example to do an emergency boot,
when the last boot fails and the watchdog reactivates the hanging s
21 matches
Mail list logo
