On 2019-11-12 12:00 p.m., Sascha Hauer wrote:
Sorry for the delay, I probably knew this issue will be something
unfortunate to look at...
No Problem, thanks for your hard work. :)
The second solution is to add -fPIE to CPPFLAGS which is a more general
approach. I'd like to give this a try
Good day, everyone.
*bump*
On 2019-10-25 10:48 a.m., Andreas Geisenhainer wrote:
Hello Sascha, hello barebox-ml.
> On 2019-07-10 9:58 a.m., Sascha Hauer wrote:
>> On Mon, Jul 08, 2019 at 04:15:00PM +0200, Andreas Geisenhainer wrote:
>>> We're running barebox an a Phy
Hello Sascha, hello barebox-ml.
> On 2019-07-10 9:58 a.m., Sascha Hauer wrote:
>> On Mon, Jul 08, 2019 at 04:15:00PM +0200, Andreas Geisenhainer wrote:
>>> We're running barebox an a Phytec PhyCORE AM335x platform, and the
>>> behaviour does emerge for the default
Hello Sascha, hello ML.
On 2019-07-10 9:58 a.m., Sascha Hauer wrote:
Hi Andreas,
On Mon, Jul 08, 2019 at 04:15:00PM +0200, Andreas Geisenhainer wrote:
We're running barebox an a Phytec PhyCORE AM335x platform, and the
behaviour does emerge for the default "barebox-am335x-phytec-phycor
config into the extracted archive.
But it does not really explain why this breaks.
kind regards
Andreas Geisenhainer
--
_
__ _| |_ ___
/ _` | __/ __|
| (_| | |_\__ \
\__,_|\__|___/
Elektronik GmbH
___
barebox mailing list
barebox@lists.infrad
Remove information about DATA from help text.
Signed-off-by: Andreas Geisenhainer <andreas.geisenhai...@atsonline.de>
---
commands/i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/commands/i2c.c b/commands/i2c.c
index e6750e3..ae7f7fc 100644
--- a/commands/i2c.c
On 27/05/15 08:41 AM, Sascha Hauer wrote:
Hi Alexander,
On Tue, May 26, 2015 at 11:50:39AM +0200, Alexander Richter wrote:
Hallo,
I just used bareboxenv tool in linux userspace after a long
troublesome trip through ptxdist.
That would not have to be, if the description of build bareboxenv
