On 12 Aug 2015 11:38, "Chris Johns" wrote:
>
> On 12/08/2015 6:02 am, Rohini Kulkarni wrote:
> > Yes I have tried this. Didn't work out :(
>
> What was the reason ?
>
> I do not remembering seeing it.
I didn't understand what "it" refers to.
>
> Chris
__
On 12/08/2015 3:18 pm, punit vara wrote:
> I am facing problem with python .I installed python but don't know why
> still same problem .Can anybody tell me how to solve python
> dependencies in Ubuntu 15.04 64 bit.
> please find the attachment of error report.
https://lists.rtems.org/pipermail/use
On 12/08/2015 6:02 am, Rohini Kulkarni wrote:
> Yes I have tried this. Didn't work out :(
What was the reason ?
I do not remembering seeing it.
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
I am facing problem with python .I installed python but don't know why
still same problem .Can anybody tell me how to solve python
dependencies in Ubuntu 15.04 64 bit.
please find the attachment of error report.
RTEMS Tools Project - Source Builder Error Report
Build: error: building i386-rtems4.1
Hi,
how should I make sure that testcases I am implementing are running under
uniprocessor configuration?
What do we have to do to run rtems for uniprocessor architecture?
Thanks,
Saurabh Gadia
___
devel mailing list
devel@rtems.org
http://lists.rtems.
Yes I have tried this. Didn't work out :(
On 11 Aug 2015 19:56, "Joel Sherrill" wrote:
> Hi
>
> Has this been tried?
>
>
> Forwarded Message
> Subject: Re: [PATCH] GSoC: Cache configurations Raspberry Pi 2 support
> Date: Tue, 28 Jul 2015 01:57:44 -0500
> From: Sebastian Huber
On 8/11/2015 2:06 PM, Rohini Kulkarni wrote:
Hi,
I would have to register the related mailbox interrupt and associate it with a
handler that should be same as _SMP_Inter_processor_interrupt_handler(). Am I
right?
That sounds correct.
From where can I get a reference of how to do this?
Hi,
I would have to register the related mailbox interrupt and associate it
with a handler that should be same as
_SMP_Inter_processor_interrupt_handler(). Am I right?
>From where can I get a reference of how to do this?
On 11 Aug 2015 00:41, "Joel Sherrill" wrote:
> The source for the CPU su
Ok
> 在 2015年8月11日，17:02，Joel Sherrill 写道：
>
> Can you rebase these and send again?
>
> Previous patches have changed at least bsp.h, Makefile.am
> and preinstall.am.
>
> --joel
>
>> On 8/10/2015 7:47 AM, YANG QIAO wrote:
>> From: YANG Qiao
>>
>> ---
>> c/src/lib/libbsp/arm/raspberrypi/Mak
Can you rebase these and send again?
Previous patches have changed at least bsp.h, Makefile.am
and preinstall.am.
--joel
On 8/10/2015 7:47 AM, YANG QIAO wrote:
From: YANG Qiao
---
c/src/lib/libbsp/arm/raspberrypi/Makefile.am | 4 ++
c/src/lib/libbsp/arm/raspberrypi/include/mailbox.
Hi
Has this been tried?
Forwarded Message
Subject: Re: [PATCH] GSoC: Cache configurations Raspberry Pi 2 support
Date: Tue, 28 Jul 2015 01:57:44 -0500
From: Sebastian Huber
To: Rohini Kulkarni , Gedare Bloom
CC: rtems-de...@rtems.org
On 24/07/15 21:55, Rohini Kulkarni wr
Well, the unwind code is being pulled in for:
Unwind table index '.ARM.exidx' at offset 0xa3fb8 contains 1 entries:
0x9b300 <__divdi3>: 0x1 [cantunwind]
So back-tracking that may also help.
Gedare
On Tue, Aug 11, 2015 at 10:09 AM, Joel Sherrill
wrote:
>
>
> On 8/11/2015 9:00 AM, Gedare Bloom wr
On 8/11/2015 9:00 AM, Gedare Bloom wrote:
On Tue, Aug 11, 2015 at 9:59 AM, Gedare Bloom wrote:
Yeah until you or someone can figure out how to get the .ARM.exidx
section from being placed in the .bss, a quick work-around would be to
provide an alternate code to clear the bss that does somethi
On Tue, Aug 11, 2015 at 9:59 AM, Gedare Bloom wrote:
> Yeah until you or someone can figure out how to get the .ARM.exidx
> section from being placed in the .bss, a quick work-around would be to
> provide an alternate code to clear the bss that does something like...
>
> memset(bsp_section_bss_beg
Yeah until you or someone can figure out how to get the .ARM.exidx
section from being placed in the .bss, a quick work-around would be to
provide an alternate code to clear the bss that does something like...
memset(bsp_section_bss_begin, 0, __exidx_start - bsp_section_bss_begin);
memset(__exidx_s
OK! So is there any immediate solution which can be tried?
On Tue, Aug 11, 2015 at 6:32 PM, Gedare Bloom wrote:
> I can see the following pertinent information:
> [15] .bss NOBITS 001156e0 0a8fd8 00fab0 00 WA 0
> 0 32
> The bss section starts at 0x1156e0, has size 0xfab0
I can see the following pertinent information:
[15] .bss NOBITS 001156e0 0a8fd8 00fab0 00 WA 0 0 32
The bss section starts at 0x1156e0, has size 0xfab0, and is writeable.
In the symbol table we can see:
7825: 001156e0 0 NOTYPE GLOBAL DEFAULT 15 bsp_section_bss_b
---
diff --git a/c/src/lib/libbsp/arm/beagle/gpio/bbb-gpio.c
b/c/src/lib/libbsp/arm/beagle/gpio/bbb-gpio.c
new file mode 100644
index 000..6426d21
--- /dev/null
+++ b/c/src/lib/libbsp/arm/beagle/gpio/bbb-gpio.c
@@ -0,0 +1,468 @@
+/**
+ * @file
+ *
+ * @ingroup arm_beagle
+ *
+ * @brief Support
---
c/src/lib/libbsp/arm/beagle/Makefile.am| 6 +
c/src/lib/libbsp/arm/beagle/gpio/bbb-gpio.c| 468 +
c/src/lib/libbsp/arm/beagle/include/bbb-gpio.h | 43 ++
.../libbsp/arm/beagle/include/beagleboneblack.h| 72
c/src/lib/libbsp/arm/beagle/in
19 matches
Mail list logo
