I'm interested to update my bsp to use the new environment. I am not finding
any info that describe the structure or how it is intended to be configured
and used. Can someone provide a pointer to something, or write a few
sentences on the subject ?
Geo.
_
Having some trouble booting Linux from recent versions of barebox, and need
some pointers about where to look.
I'm working with custom hardware based on the i.MX53. It is roughly
comparable to the i.MX53 LOCO board, and I started with that board support
as a base for my own port. Up through barebo
Subject: i.MX53: Add WEIM register defines ( same as i.MX51 )
Signed-off-by: George Pontis
diff -Naur bb.a/arch/arm/mach-imx/include/mach/imx53-regs.h
bb.b/arch/arm/mach-imx/include/mach/imx53-regs.h
--- bb.a/arch/arm/mach-imx/include/mach/imx53-regs.h2013-02-04
06:24:51.0 -0800
Subject: i.MX53 i2c, add support for third i2c interface
Signed-off-by: George Pontis
---
diff -Naur bb.a/arch/arm/mach-imx/include/mach/devices-imx53.h
bb.b/arch/arm/mach-imx/include/mach/devic
es-imx53.h
--- bb.a/arch/arm/mach-imx/include/mach/devices-imx53.h 2013-02-04
06:24:51.0
> -Original Message-
> From: Alexander Shiyan [mailto:shc_w...@mail.ru]
> Sent: Monday, February 04, 2013 11:09 AM
> To: George Pontis
> Cc: barebox@lists.infradead.org
> Subject: Re: i.MX53, add access to third I2C peripheral
>
> > All versions of the i.MX53
> -Original Message-
> From: Antony Pavlov [mailto:antonynpav...@gmail.com]
> Sent: Saturday, February 02, 2013 9:56 AM
> To: George Pontis
> Cc: barebox@lists.infradead.org
> Subject: Re: Lost access to M25Pxx in move to 2013.01
>
...
>
> Here is part of
All versions of the i.MX53 have three I2C peripherals. This patch provides
access to it.
diff -Naur a/arch/arm/mach-imx/include/mach/devices-imx53.h
b/arch/arm/mach-imx/include/mach/devices-imx
53.h
--- bb.a/arch/arm/mach-imx/include/mach/devices-imx53.h 2013-02-04
06:24:51.0 -0800
+++
Under 2012.11 I created a new board support package for custom hardware,
which included a M25P32. I store barebox and its environment there, and boot
from it. The board file also defines partitions for it. The first three look
like this:
devfs_add_partition("m25p0",0, 0x05,
DEV
> -Original Message-
> From: Sascha Hauer [mailto:s.ha...@pengutronix.de]
> Sent: Monday, July 16, 2012 1:33 AM
> To: George Pontis
> Cc: barebox@lists.infradead.org
> Subject: Re: Atmel AT91 SD/MMC clock too fast
>
> Hi George,
>
> On Mon, Jul 16, 20
Due to integer truncation, the calculated divisor for the SD/MMC clock may
be too low, resulting in a clock that is too fast. For example, the
at91sam9g45 is typically run with a master clock at 133 MHz. There is no
divisor possible that will result in a 25 or 50 MHz clock as is typically
used for
Is it possible to get barebox to load an initramfs image ?
George
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
Machine is a custom at91sam9g45 board with NOR and NAND flash. The bootstrap
loader and barebox, and barebox environment are in the NOR flash. All seems
to be working well there. The NAND is partitioned into 2 chunks:
2560K(kernel),-(root)
I used ubimkvol to create a volume on root and the nfs
Hi fellow barebox users. What a great loader, thanks to all of you for
sharing your work on this.
I've brought barebox up on a custom at91sam9g45 board that has both NOR and
NAND flash, and one SD card connected to the MMC interface. I was previously
using all these with an older version of u-b
13 matches
Mail list logo
