Hello Federico,
since this just adds a linker command file variant, I would prefer to just add
the linker command file without the BSP name. You can then use -qnolinkcmds
-T linkcmds.lpc1768_mbed_ahb_ram_eth to select this memory map.
On 01/09/14 15:21, Federico Casares wrote:
Attached the
On Tue, Sep 2, 2014 at 11:51 AM, Joel Sherrill
joel.sherr...@oarcorp.com wrote:
This is the license.
The big problem I see first is the typical use only on our hardware
and that in order to redistribute, we must ensure that it is only
used on ARM hardware.
This is a common restriction on
On 9/2/2014 9:52 AM, Daniel Gutson wrote:
On Tue, Sep 2, 2014 at 11:51 AM, Joel Sherrill
joel.sherr...@oarcorp.com wrote:
This is the license.
The big problem I see first is the typical use only on our hardware
and that in order to redistribute, we must ensure that it is only
used on ARM
Hi
Doing some greps and mangling on the build logs from every BSP, I
discovered we have ~2350 unique warnings output by gcc.
- ~1250 of these only occur once.
- ~1900 occur less than 5 times.
- ~2270 occur less than 10 times.
These are almost certainly in BSP specific code built for variants.
Hi
The tms570 has what appears to be a partial set of Makefile.am
entries for a network driver but none is present so the BSP fails
to build when networking is enabled. It appears to be missing
the line which would specify a source file anyway.
I have commented out the section locally. Should I
On 3/09/2014 12:05 pm, 贾超 wrote:
tools: sparc-rtems4.11.
host: x86_64ubuntu.
When I compile the source code in the sparc-rtems4.11 target, always
appear the following error.
../../../sis/lib/include/rtems/rtems_bsdnet_internal.h:54:7: note:
expected 'void *' but argument is of type 'volatile
On 3/09/2014 12:21 am, Joel Sherrill wrote:
cpukit/score/cpu/or1k/preinstall.am|6 +-
Did this patch happen before my fix to the preinstall went in ?
I am seeing an issue with this one.
Chris
___
devel mailing list
