As far as I can tell it's the plain BSP. I haven't added anything that I
know of.
Perhaps I should say that my main interest here is in Barebox with the
intention of porting your Mini2440 version to the new Mini2451 to
replace FriendlyARM's incredibly lame Superboot. I was surprised to find
Hi Doug,
On Sunday 01 March 2015 01:31:03 Doug Abbott wrote:
OK, so I solved the problem of the undefined symbols. Had to do a
distclean to remove all references to the older toolchain I had been
using. Now it gets to:
target: glibc.targetinstall
And emits the subject error message. Of
On 03/02/2015 10:30 AM, Juergen Borleis wrote:
Maybe you should do more validating tests.
PROC_TO_KILL=`pidof data.hhp`
if [ -n ${PROC_TO_KILL} ]; then
ps ${PROC_TO_KILL} /dev/null
if [ $? -eq 0 ]; then
kill ${PROC_TO_KILL}
fi
fi
This is all racy, what about
Juergen,
Good suggestion:
pidof crond returns the PID, but
pidof data.php returns nothing
whereas on the previous version
pidof data.php returns the PID.
I'll look on the Busybox mailing list to try and determine if there has been a
change.
Thank you,
Dave
From: j...@pengutronix.de
To:
On Saturday 28 February 2015 08:11:20 Dave Festing wrote:
Upgraded a system that has been working nicely with the previous BSP and
3.7 and having a few problems.
My main PHP script starts with:
#!/usr/bin/php5
?php
...
and the error I get when I invoke:
./data.php (from the
On 03/02/2015 10:54 AM, Juergen Borleis wrote:
On Monday 02 March 2015 10:38:42 Marc Kleine-Budde wrote:
On 03/02/2015 10:30 AM, Juergen Borleis wrote:
Maybe you should do more validating tests.
PROC_TO_KILL=`pidof data.hhp`
if [ -n ${PROC_TO_KILL} ]; then
ps ${PROC_TO_KILL}
The penny just dropped, if I do:
pidof php5 data.php
the PID is returned.
Looks like the initial problem ... ie from the directory that data.php is in,
that it couldn't be invoked by ./data.php but worked with php5 data.php seems
to influence how pidof now works.
Well, looks like I have a
Hi Rudi,
On Saturday 28 February 2015 11:16:14 Lappies wrote:
[...]
Hm, hardware issue?
SDCard or the mini itself?
I dont have a nother SDCard to hand to test.
[...]
mmc: Probing for SDHC ...
mmc: SD 2.0 or later card found
trying to detect SD Card...
Manufacturer: 0x03, OEM SD
Hi Dave,
On Saturday 28 February 2015 08:11:20 Dave Festing wrote:
Upgraded a system that has been working nicely with the previous BSP and
3.7 and having a few problems.
My main PHP script starts with:
#!/usr/bin/php5
?php
...
and the error I get when I invoke:
./data.php (from
Hi Gautam,
On Saturday 28 February 2015 06:48:48 mind entropy wrote:
On Sat, Feb 21, 2015 at 12:21 PM, mind entropy mindentr...@gmail.com wrote:
I am trying to understand the flash access timing calculations in
the barebox code and I have some doubts. ( I am a newbie in NAND flash
).
Yes, it does.
From: j...@pengutronix.de
To: oselas@community.pengutronix.de
Date: Mon, 2 Mar 2015 11:19:55 +0100
CC: dave_fest...@hotmail.com
Subject: Re: [oselas] Latest mini2440BSP bash pidof problems
On Saturday 28 February 2015 08:11:20 Dave Festing wrote:
Upgraded a system that has
On Mon, Mar 2, 2015 at 3:01 PM, Juergen Borleis j...@pengutronix.de wrote:
Hi Gautam,
On Saturday 28 February 2015 06:48:48 mind entropy wrote:
On Sat, Feb 21, 2015 at 12:21 PM, mind entropy mindentr...@gmail.com wrote:
I am trying to understand the flash access timing calculations in
Hi Gautam,
mind entropy wrote:
On Mon, Mar 2, 2015 at 3:01 PM, Juergen Borleis j...@pengutronix.de wrote:
On Saturday 28 February 2015 06:48:48 mind entropy wrote:
On Sat, Feb 21, 2015 at 12:21 PM, mind entropy mindentr...@gmail.com
wrote:
I am trying to understand the flash access
13 matches
Mail list logo
