Hello,
how can I use the "-include file" GCC option with waf? In case I use this:
+bld.objects(target = "objs07",
+features = "c",
+cflags = ['-include
freebsd/sys/contrib/ncsw/build/dflags.h'] + cflags,
I get:
Waf: Entering directory
`/scratch/git-rtems-
On 20/10/2015 9:39 am, Joel Sherrill wrote:
> Did I miss all discussion and review of this patch set?
I did not see any discussion on how RTEMS is to use the FDT.
The only patch that appeared was the FDT code itself which I was fine
with as it is a single commit with an import of code. I assumed
Was this patch posted to devel@rtems.org for review?
I do not remember any discussion about how BSPs and FDT will be
supported. I posted an RTEMS API for FDT which seems to have been ignored.
Can you please describe this use of FDT in RTEMS and how this can used
by more than the immediate use you
Hello Sudarshan,
Às 18:53 de 19-10-2015, sudarshan.rajagopalan escreveu:
Hey guys,
I have few questions/comments on the GPIO APIs, maybe to André:
1.) Most of the APIs has a way to call the BSP specific functions: pin
input/output initialize, pin read/write, enable/disable interrupts
etc, bu
On 19/10/2015 5:18 pm, Sebastian Huber wrote:
> On 19/10/15 07:50, Chris Johns wrote:
>> On 19/10/2015 4:47 pm, Sebastian Huber wrote:
>>> Since its not explained what a '-' means in the RTEMS project its
>>> probably subject to interpretation. GCC and other GNU projects clarify
>>> this in READMEs
- Am 19. Okt 2015 um 20:51 schrieb Joel Sherrill joel.sherr...@oarcorp.com:
> Hi
>
> psxcancel and spcontext01 fail on the master.
This is
https://devel.rtems.org/ticket/2402
and (SPARC floating point support on uni-processor configurations is not bullet
proof)
https://devel.rtems.org/
Hi
psxcancel and spcontext01 fail on the master.
I thought all tests were passing on sparc/erc32.
Any thoughts?
--joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hey guys,
I have few questions/comments on the GPIO APIs, maybe to André:
1.) Most of the APIs has a way to call the BSP specific functions: pin
input/output initialize, pin read/write, enable/disable interrupts etc,
but I couldn't find a way to call a BSP specific pin release (or
de-init). T
This patch renames the GPIO specific functions:
from
rtems_bsp_enable_interrupt
rtems_bsp_disable_interrupt
rtems_bsp_select_specific_io
to
rtems_gpio_bsp_enable_interrupt
rtems_gpio_bsp_disable_interrupt
rtems_gpio_bsp_select_specific_io
And also minor changes to the function description in
