Uwe Kleine-König writes:
>
> Hello,
>
> On Tue, Apr 05, 2016 at 10:40:48AM +0200, Guillermo Rodriguez Garcia
wrote:
> > I am wondering: If I am correct, serial in/out in barebox is not
> > interrupt-driven. Plus, the default UART in the sama5d3_xplained board
>
> right
>
> > that I am using
Guillermo Rodriguez Garcia writes:
>
> That's a very good question. I just tried to paste this text in
> barebox's command line:
>
> Lorem Ipsum is simply dummy text of the printing and typesetting industry.
>
> It works perfectly. However I then tried to paste the very same text
> in a "edit"
> I have a cortex-A9 based platform featuring a spi-nor (n25q256a).
> Copying a bigger file (512KB) leads to a read failure
> Has anybody used UBI/UBIFS on spi-nor successfully or seen a similar
issue?
>
Hello,
I've recently used UBI/UBIFS with a cortex-A7 based platform featuring a
spi-nor fr
Dear Andy,
we have another custom hardware platform that uses a 800MHz TI AM3359. Currently
we store only barebox-MLO and the barebox itself in SPI NOR. The kernel is
loaded over USB.
When I checked the SPI bus during boot, I found that the ROM Code loads the
first part of the barebox in chunks of
Long time ago all ".ip" parameters have been replaced with ".ipaddr".
Signed-off-by: Rolf Evers-Fischer
---
lib/parameter.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/parameter.c b/lib/parameter.c
index 84a632c..c4c30ca 100644
--- a/lib/p
[ Rolf: ported from kernel to barebox 2014.09.0 ]
Signed-off-by: Rolf Evers-Fischer
---
drivers/net/usb/asix.c | 123 -
1 file changed, 91 insertions(+), 32 deletions(-)
diff --git a/drivers/net/usb/asix.c b/drivers/net/usb/asix.c
index d6ac322..14a8c76
Hello Sascha,
Sascha Hauer writes:
> Looks like a side effect of:
>
> | commit d1ec6fb0c9bb66939e85964c2f5214b117c78ecf
> | Author: Sascha Hauer
> | Date: Mon Jul 7 14:13:14 2014 +0200
> |
> | ARM: OMAP: Do not show MLO/SPI image options with OMAP_MULTI_BOARDS
> |
> | The MLO/S
Hello Florian,
On Tue, 8 Jul 2014, Teresa Gamez wrote:
> Hello Florian,
>
> I guess you having the default kit WEGA, which does have 256MB RAM. The
> mainline supported
> phyCORE Kit does have 512MB. Thats probably why it does not start up.
>
> I'll have a look at it.
>
> Teresa
>
I'm not 10
Hello Florian,
> Sascha Hauer hat am 7. Juli 2014 um 14:00
> geschrieben:
>
>
> On Mon, Jul 07, 2014 at 01:14:35PM +0200, Frede Florian wrote:
> > Hello Rolf,
> >
> > thank you very much...
> > after I selected the mentioned entry in the menu the problem was solved...
> > but the board do not pro
Hello Florian,
On Mon, 7 Jul 2014, Florian Frede wrote:
> Hello Rolf,
>
> I used this Option already, but to be sure that there is no mistake I
> reconfigured the Barebox and Barebox_MLO again and use the new Version
> 2014.07.0. The result is the same.
>
>
> I also attached the config files m
Hi Florian,
On Fri, Jul 04, 2014 at 12:12, Florian Wrede wrote:
> I like to update from barebox 2013.11 to barebox 2014.06.0 with the
> phyBoard-Wega-AM335x. After reconfigure the barebox I get the error:
>
> LD images/start_am33xx_phytec_phycore_sram.pbl
> arch/arm/boards/built-in-pbl
Dear Uwe and Alessandro,
thank you for your quick replies and the interesting informations that you
shared. I didn't know these details until now.
Best regards,
Rolf
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailm
Hi Sascha,
Sascha Hauer wrote:
> + static int in_automount;
> +
> + if (in_automount)
> + return;
It seems that we are using the 'in_automount' without initialization.
Shouldn't we initialize the static 'in_automount' with 0? Or can we rely
on the compiler, that all statics
On Wed, 2 Jul 2014, Sascha Hauer wrote:
> I mean the intention is that
>
> boot -l
>
> lists all sources specified, whereas
>
> boot -l
>
> lists everything from $global.boot.default
>
Thank you for this clarification. Now I know, how I can list more than one
bootsource in bootmenu: I s
On Tue, 1 Jul 2014, Sascha Hauer wrote:
On Mon, Jun 30, 2014 at 02:21:39PM +0200, Rolf Evers-Fischer wrote:
This patch fixes the presentation of all bootsources with 'boot -m' and
'boot -l' command.
Signed-off-by: Rolf Evers-Fischer
---
commands/boot.c | 4 ++--
Hi Sascha,
> Sascha Hauer hat am 1. Juli 2014 um 08:46
> geschrieben:
>
>
> Hi Rolf,
>
> On Mon, Jun 30, 2014 at 02:27:30PM +0200, Rolf Evers-Fischer wrote:
> > Signed-off-by: Rolf Evers-Fischer
> > ---
> > commands/boot.c | 2 +-
> >
Signed-off-by: Rolf Evers-Fischer
---
commands/boot.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/commands/boot.c b/commands/boot.c
index a23ffb1..c8eae10 100644
--- a/commands/boot.c
+++ b/commands/boot.c
@@ -151,7 +151,7 @@ static int bootscript_scan_path(struct
This patch fixes the presentation of all bootsources with 'boot -m' and
'boot -l' command.
Signed-off-by: Rolf Evers-Fischer
---
commands/boot.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/commands/boot.c b/commands/boot.c
index c8eae10..
Dear Sascha and Jan,
Sascha Hauer writes:
>
> From: Jan Luebbe
>
> mk-am35xx-spi-image can only build AM35xx images. Rename
> the tool to mk-am3xxx-spi-image and add support for the AM33xx.
>
> Signed-off-by: Sascha Hauer
> ---
> arch/arm/Makefile | 7 ++-
Dear Christoph and Alex,
> Christoph Fritz hat am 13. Mai 2014 um 14:49
> geschrieben:
>
>
> Hey Alex
>
> On Tue, 2014-05-13 at 13:03 +0200, Alexander Aring wrote:
> > This was one year ago...
>
> The port (with only host support) is that old, but simply due to lack of
> time I haven't fixed the
Dear Christoph,
just a shy question: Were you already able to prepare a first patchset?
Kind regards,
Rolf
> Rolf Evers-Fischer hat am 5. Mai 2014 um 14:13
> geschrieben:
>
>
> Hi Christoph,
>
> > Christoph Fritz hat am 2. Mai 2014 um 00:50
> > geschrieben:
Hi Christoph,
> Christoph Fritz hat am 2. Mai 2014 um 00:50
> geschrieben:
>
>
> Hi Rolf,
>
> I have ported musb (host-support) from u-boot to barebox. I'll send a
> patchset in the next days.
>
that sounds very good. Thank you very much in advance!
_
I have resolved the problem by enabling the USB clocks:
Write "2" to register "CM_PER_USB0_CLKCTRL" (address 0x44e0001c).
Kind regards,
Rolf
> Rolf Evers-Fischer hat am 24. April 2014 um
> 10:52 geschrieben:
>
>
>
> Hi Sascha,
>
> > Sascha Hauer
Hi Sascha,
> Sascha Hauer hat am 24. April 2014 um 08:58
> geschrieben:
>
>
> Hi Rolf,
>
> On Wed, Apr 23, 2014 at 06:09:40PM +0200, Rolf Evers-Fischer wrote:
> > I'm just trying to port the USB driver "musb" (for the AM335x platform) from
> > lin
I'm just trying to port the USB driver "musb" (for the AM335x platform) from
linux kernel to barebox.
But whenever I want to read any address in the range 0x47401400-0x474017ff, the
barebox crashes with "unable to handle paging request".
I have already tried to invoke a "map_io_sections(0x0, 0x4740
> Lucas Stach hat am 22. April 2014 um 10:26
> geschrieben:
>
>
> Am Dienstag, den 22.04.2014, 09:08 +0200 schrieb Rolf Evers-Fischer:
> > Hi Lukasz and Uwe,
> >
> > > Lucas Stach hat am 21. April 2014 um 17:24 geschrieben:
> > >
> > >
>
tag, den 15.04.2014, 13:28 +0200 schrieb Rolf Evers-Fischer:
> > > > Dear all,
> > > > after update to barebox-2014.03.0, the kernel on my beaglebone-white
> > > > doesn't
> > > > start anymore.
> > > > The last line, which appears,
Dear all,
after update to barebox-2014.03.0, the kernel on my beaglebone-white doesn't
start anymore.
The last line, which appears, is "booting kernel with devicetree".
I discovered that the problem is caused by the commit [1]. When I revert this
commit, everything works fine.
Here is some more in
28 matches
Mail list logo
