On Wed, 10 Apr 2013 11:14:53 +0200
Lucas Stach wrote:
> ODMdata tells us which UART to use for debugging purposes. This is
> agreed upon in both the upstream Linux kernel and U-Boot, so do it the
> same way in barebox.
>
> Signed-off-by: Lucas Stach
> ---
> v4:
> - fix rebase error
> - provide
On Wed, 10 Apr 2013 11:14:55 +0200
Lucas Stach wrote:
> Taken from the Linux kernel, simplified and reworked to match barebox.
>
> Signed-off-by: Lucas Stach
> ---
> v4: remove Tegra 30 parts for now
> ---
> arch/arm/Kconfig| 2 +
> arch/arm/dts/tegra20.dtsi
On Wed, 10 Apr 2013 11:18:01 +0200
Lucas Stach wrote:
> Am Montag, den 08.04.2013, 17:03 +0400 schrieb antonynpav...@gmail.com:
> > On Mon, 08 Apr 2013 14:24:06 +0200
> > Lucas Stach wrote:
> >
> > > Am Montag, den 08.04.2013, 15:46 +0400 schrieb antonynpav...@gmail.com:
> > > > On Mon, 08 Apr
Hi Sacha,
Le Wed, 3 Apr 2013 09:09:40 +0200,
Sascha Hauer a écrit :
> With CONFIG_MMU_EARLY enabled the board does not survive the call
> to imx53_init_lowlevel(). This should not happen, but the reasons
> are currently unknown. This works on other boards like the i.MX53
> QSB.
> This patch mov
On 16:10 Wed 10 Apr , Eric Bénard wrote:
> this patch allows barebox to run when loaded on the iMX53QSB
> using the serial downloader.
>
> Signed-off-by: Eric Bénard
> ---
> arch/arm/boards/freescale-mx53-loco/flash_header.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/ar
if the flash has a known type, the ONFI detection won't occur
and thus we may not detect the right parameters.
By testing both namd and pagesize, as done in the kernel, we
can detect ONFI flash with know IDs.
As an example on an i.MX53 board :
- without the patch :
NAND device: Manufacturer ID: 0x
Signed-off-by: Jan Luebbe
---
drivers/mtd/nand/nand_ids.c | 4 +++-
include/linux/mtd/nand.h| 20 +++-
2 files changed, 14 insertions(+), 10 deletions(-)
diff --git a/drivers/mtd/nand/nand_ids.c b/drivers/mtd/nand/nand_ids.c
index 72593d4..4f8fb02 100644
--- a/drivers/mtd/na
Hi Sascha,
Le Wed, 10 Apr 2013 11:29:18 +0200,
Eric Bénard a écrit :
> if the flash has a known type, the ONFI detection won't occur
> and thus we may not detect the right parameters.
> By testing both namd and pagesize, as done in the kernel, we
> can detect ONFI flash with know IDs.
>
> As an
Signed-off-by: Eric Bénard
---
arch/arm/mach-imx/boot.c | 70 +---
1 file changed, 37 insertions(+), 33 deletions(-)
diff --git a/arch/arm/mach-imx/boot.c b/arch/arm/mach-imx/boot.c
index bd0cb84..2e3f7ca 100644
--- a/arch/arm/mach-imx/boot.c
+++ b/arc
this patch allows barebox to run when loaded on the iMX53QSB
using the serial downloader.
Signed-off-by: Eric Bénard
---
arch/arm/boards/freescale-mx53-loco/flash_header.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boards/freescale-mx53-loco/flash_header.c
b/arch/arm/bo
if the flash has a known type, the ONFI detection won't occur
and thus we may not detect the right parameters.
By testing both namd and pagesize, as done in the kernel, we
can detect ONFI flash with know IDs.
As an example on an i.MX53 board :
- without the patch :
NAND device: Manufacturer ID: 0x
Am Montag, den 08.04.2013, 17:03 +0400 schrieb antonynpav...@gmail.com:
> On Mon, 08 Apr 2013 14:24:06 +0200
> Lucas Stach wrote:
>
> > Am Montag, den 08.04.2013, 15:46 +0400 schrieb antonynpav...@gmail.com:
> > > On Mon, 08 Apr 2013 12:57:26 +0200
> > > Lucas Stach wrote:
> > >
> > > > Hi Anto
All Tegra20 boards have a common startup sequence. Also there is an
agreement on how to find out about the installed amount of RAM and other
information needed by early startup. So as there is really no need to do
any lowlevel stuff per board, we can just do it at the ARCH level.
This also enables
Taken from the Linux kernel, simplified and reworked to match barebox.
Signed-off-by: Lucas Stach
---
v4: remove Tegra 30 parts for now
---
arch/arm/Kconfig| 2 +
arch/arm/dts/tegra20.dtsi | 16 +++
arch/arm/mach-tegra/include/mach/gpio.h | 1 +
drivers
ODMdata tells us which UART to use for debugging purposes. This is
agreed upon in both the upstream Linux kernel and U-Boot, so do it the
same way in barebox.
Signed-off-by: Lucas Stach
---
v4:
- fix rebase error
- provide Kconfig option to ovveride ODMdata
---
arch/arm/boards/toshiba-ac100/Make
Only a basic set of clocks is supported. This is a temporary solution
and will go away as soon as the port of the Tegra common clock code from
the Linux kernel is ready to go.
Signed-off-by: Lucas Stach
---
arch/arm/Kconfig | 2 +
arch/arm/dts/tegra20.dtsi
Currently only implements system wide reset functionality.
Signed-off-by: Lucas Stach
---
arch/arm/dts/tegra20.dtsi | 5 ++
arch/arm/mach-tegra/Makefile | 2 +-
arch/arm/mach-tegra/include/mach/tegra20-pmc.h | 37 ++
arch/arm/mach-tegra/reset.
Replace the ad-hoc clocksource implementation with a proper driver for
the Tegra 20 timer. This driver is able to do the required hardware
initialisation itself.
Signed-off-by: Lucas Stach
---
arch/arm/dts/tegra20.dtsi | 9 +++
arch/arm/mach-tegra/Makefile| 2 +-
arch/arm/m
ODMdata tells us how much RAM is installed, so no need to define this at
the board level.
Signed-off-by: Lucas Stach
---
arch/arm/boards/toshiba-ac100/board.c | 8
arch/arm/mach-tegra/tegra20.c | 9 +
2 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/arch/ar
We will follow the Linux kernel and go devicetree only for Tegra. This
doesn't prevent specific code for certain boards, but always requires a
valid DTB for all boards.
Also regenerate the AC100 defconfig to reflect this change.
Signed-off-by: Lucas Stach
---
v4: unbrick ac100 defconfig
---
arc
This synchronizes the Tegra iomap.h with the latest Linux kernel code.
Signed-off-by: Lucas Stach
---
arch/arm/mach-tegra/include/mach/iomap.h | 64 ++--
1 file changed, 19 insertions(+), 45 deletions(-)
diff --git a/arch/arm/mach-tegra/include/mach/iomap.h
b/arch/a
All available opensource tools and published BCT configurations use
0x10800 as the default textbase on Tegra 20.
Signed-off-by: Lucas Stach
---
arch/arm/mach-tegra/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-tegra/Kconfig b/arch/arm/mach-tegra/Kconfi
Tegra isn't a single architecture, but a collection of more or less
similar chip families. Introduce the same conf define as used in the
Linux kernel to differentiate between those families.
Currently we are only supporting the Tegra20 chip type.
Signed-off-by: Lucas Stach
---
arch/arm/mach-teg
Tegras main CPUs are all ARMv7.
Signed-off-by: Lucas Stach
---
arch/arm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index bb9b47b..dfb7e24 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -137,7 +137,7 @@ config ARCH_VEXP
Signed-off-by: Lucas Stach
---
arch/arm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index dfb7e24..befed5d 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -136,7 +136,7 @@ config ARCH_VEXPRESS
select COMMON_CLK
25 matches
Mail list logo