Sure.
On Wed, Aug 20, 2014 at 7:48 PM, Joel Sherrill
wrote:
> With the recent addition of a prototype for sigaltstack() and
> associated data structures to newlib, the declaration in
> rtems_bsdnet_internal.h is no longer needed. But to ease the
> transition, I added an autoconf probe to determin
With the recent addition of a prototype for sigaltstack() and
associated data structures to newlib, the declaration in
rtems_bsdnet_internal.h is no longer needed. But to ease the
transition, I added an autoconf probe to determine if it
was needed or not.
After 4.11, I would like to rip this and a
I didn't regenerate the patch, I just resent an old email. That could be an
issue.
On Aug 20, 2014, at 16:59 , Joel Sherrill wrote:
> Applying: Properly flush cache when writing to MPC55XX flash.
> fatal: corrupt patch at line 11
> Patch failed at 0001 Properly flush cache when writing to MPC55
Thanks for the update and input, all. I'll make sure it's included in our
current issue tracking.
FYI, work on this has briefly stalled, as Ben is on holiday and I'm working
on wrapping up my current employment in favor of something new. I intend to
begin working again when I have some free time n
Something went wrong. :(
Applying: Properly flush cache when writing to MPC55XX flash.
fatal: corrupt patch at line 11
Patch failed at 0001 Properly flush cache when writing to MPC55XX flash.
How about you compress it and sent it to me privately as an attachment
in case the mail client is doing s
On Wed, Aug 20, 2014 at 10:51 PM, Joel Sherrill
wrote:
> I pushed this. You had the right idea to prod us. There is a lot
> of code flying right now and we want to not forget any of it.
>
> Some comments.
>
> + Turn list of implementations into a bullet list with URLs.
> + I turned on spell check
I pushed this. You had the right idea to prod us. There is a lot
of code flying right now and we want to not forget any of it.
Some comments.
+ Turn list of implementations into a bullet list with URLs.
+ I turned on spell check in gvim and fixed some.
If someone thinks there are other topics t
Hmmm... I also don't see it searching archives but I still have it in my "sent
mail" folder, and it says it went to "rtems-de...@rtems.org". I just sent it
again and cc'd Sebastian.
It was my first attempt to submit a "git patch", maybe I screwed something up.
On Aug 20, 2014, at 14:33 , Gedar
Also cleanup:
* Remove un-needed interrupt disables.
* Address errata "e989: FLASH: Disable Prefetch during programming and erase"
* Use RTEMS_ARRAY_SIZE() macro instead of own macro.
---
.../libcpu/powerpc/mpc55xx/misc/flash_support.c| 85 +---
1 files changed, 39 insertions(+
On 8/20/2014 3:29 PM, Gedare Bloom wrote:
> On Wed, Aug 20, 2014 at 4:06 PM, Hesham Moustafa
> wrote:
>> Hi,
>>
>> On Wed, Aug 20, 2014 at 9:54 PM, Joel Sherrill
>> wrote:
>>> Hi
>>>
>>> Thanks.
>>>
>>> I just pushed this. I did not compile it. Make sure it builds all tests
>> What about the no
On 8/20/2014 3:06 PM, Hesham Moustafa wrote:
> Hi,
>
> On Wed, Aug 20, 2014 at 9:54 PM, Joel Sherrill
> wrote:
>> Hi
>>
>> Thanks.
>>
>> I just pushed this. I did not compile it. Make sure it builds all tests
> What about the nop instruction? Should I add a conditional macros in
> the init.c fil
On Wed, Aug 20, 2014 at 10:29 PM, Gedare Bloom wrote:
> On Wed, Aug 20, 2014 at 4:06 PM, Hesham Moustafa
> wrote:
>> Hi,
>>
>> On Wed, Aug 20, 2014 at 9:54 PM, Joel Sherrill
>> wrote:
>>> Hi
>>>
>>> Thanks.
>>>
>>> I just pushed this. I did not compile it. Make sure it builds all tests
>> What
Hi Ritesh,
On Wed, Aug 20, 2014 at 5:37 PM, Ritesh Harjani
wrote:
> Hi Hesham,
>
> Thanks for the info.
>
> On Wed, Aug 20, 2014 at 3:10 PM, Hesham Moustafa
> wrote:
>>
>> Hi Ritesh,
>>
>> On Wed, Aug 20, 2014 at 11:28 AM, Ritesh Harjani
>> wrote:
>> > Hi All,
>> >
>> > I have been following RT
On Wed, Aug 20, 2014 at 4:06 PM, Hesham Moustafa
wrote:
> Hi,
>
> On Wed, Aug 20, 2014 at 9:54 PM, Joel Sherrill
> wrote:
>> Hi
>>
>> Thanks.
>>
>> I just pushed this. I did not compile it. Make sure it builds all tests
> What about the nop instruction? Should I add a conditional macros in
> the
Hi,
Just wanted to get some eyes on this patch in case it was lost/forgotten.
Thanks,
Hesham
On Sat, Aug 16, 2014 at 6:30 PM, Hesham ALMatary
wrote:
> ---
> doc/cpu_supplement/Makefile.am | 6 +++
> doc/cpu_supplement/cpu_supplement.texi | 2 +
> doc/cpu_supplement/or1k.t
Hi,
On Wed, Aug 20, 2014 at 9:54 PM, Joel Sherrill
wrote:
> Hi
>
> Thanks.
>
> I just pushed this. I did not compile it. Make sure it builds all tests
What about the nop instruction? Should I add a conditional macros in
the init.c file, or create a new macro to mirror l.nop to nop for or1k
targe
Hi
Thanks.
I just pushed this. I did not compile it. Make sure it builds all tests
for
you just like it did before.
How is the test pass/fail rate?
Did you get ticker running?
On 8/20/2014 12:23 PM, Hesham ALMatary wrote:
> This BSP is intended to run on or1ksim (the main OpenRISC emulator).
On Aug 20, 2014 9:29 PM, "Joel Sherrill" wrote:
>
>
> On 8/20/2014 1:23 PM, Hesham Moustafa wrote:
> > Hi,
> >
> > When I was building the new or1ksim/OpenRISC BSP with --enable-tests
> > option. I got some errors from the spcache01/init.c compilation. The
> > error is related to assembler
> > "sp
On 8/20/2014 1:23 PM, Hesham Moustafa wrote:
> Hi,
>
> When I was building the new or1ksim/OpenRISC BSP with --enable-tests
> option. I got some errors from the spcache01/init.c compilation. The
> error is related to assembler
> "spcache01/init.c:117: Error: unrecognized instruction `nop'"
>
> Whi
On 8/20/2014 1:45 PM, Pavel Pisa wrote:
> On Wednesday 20 of August 2014 20:17:47 Joel Sherrill wrote:
>> Hi
>>
>> Initial quick feedback. I build normally with --enable-rtems-debug
>> and the tms570ls3137_hdk variant failed to build with this
>> failure:
>>
>> arm-rtems4.11-gcc --pipe -DHAVE_CON
Hi
I wanted to say thank you to all the GSOC mentors and students who
went diligent enough to turn in their evaluations two days before the
deadline. It sure saves Gedare and I some worry. :)
The next activities are for students to submit their proof of work
to Google. Normally that can be patch
On Wednesday 20 of August 2014 20:17:47 Joel Sherrill wrote:
> Hi
>
> Initial quick feedback. I build normally with --enable-rtems-debug
> and the tms570ls3137_hdk variant failed to build with this
> failure:
>
> arm-rtems4.11-gcc --pipe -DHAVE_CONFIG_H -I../../..
> -I../../../../cpukit/../../..
On 8/20/2014 1:34 PM, Gedare Bloom wrote:
> On Tue, Aug 19, 2014 at 5:34 PM, Chris Johns wrote:
>> On 20/08/2014 2:38 am, Gedare Bloom wrote:
>>> Anything holding it up at the moment?
>>
>> It would be good to get a formal tool set definition into rtems-tools.git.
>>
> I think this can be dealt w
On Tue, Aug 19, 2014 at 5:34 PM, Chris Johns wrote:
> On 20/08/2014 2:38 am, Gedare Bloom wrote:
>>
>> Anything holding it up at the moment?
>
>
> It would be good to get a formal tool set definition into rtems-tools.git.
>
I think this can be dealt with post-release. There may be some time
gap be
On Wed, Aug 20, 2014 at 7:19 AM, Sebastian Huber
wrote:
> On 20/08/14 12:51, Peter Dufault wrote:
>>
>>
>> On Aug 19, 2014, at 12:38 , Gedare Bloom wrote:
>>
>>> Anything holding it up at the moment?
>>
>>
>> I'd like the PATCH for the MPC5554 flash put in, that's the only local
>> change I'm mai
Hi,
When I was building the new or1ksim/OpenRISC BSP with --enable-tests
option. I got some errors from the spcache01/init.c compilation. The
error is related to assembler
"spcache01/init.c:117: Error: unrecognized instruction `nop'"
Which is generated from the following line:
"#define I() __asm
Hi
Initial quick feedback. I build normally with --enable-rtems-debug
and the tms570ls3137_hdk variant failed to build with this
failure:
arm-rtems4.11-gcc --pipe -DHAVE_CONFIG_H -I../../..
-I../../../../cpukit/../../../tms570ls3137_hdk/lib/include -DASM
-march=armv7-r -mthumb -mbig-endian -O
Committed.
-Gedare
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
I replied to a private message without everyone on it.
Premysl. Can you submit the final patch so I am sure I am
merging the right thing?
Thanks.
--joel
On 8/20/2014 12:28 PM, Gedare Bloom wrote:
> All,
> Pavel has indicated no warnings and no serious problems flagged by
> check_submission.
>
>
Looks good to me. Joel, commit if you approve.
On Wed, Aug 20, 2014 at 1:23 PM, Hesham ALMatary
wrote:
> This BSP is intended to run on or1ksim (the main OpenRISC emulator).
> Fixed version according to Joel comments from the mailing list.
> ---
> c/src/aclocal/rtems-cpu-subdirs.m4
All,
Pavel has indicated no warnings and no serious problems flagged by
check_submission.
I'm OK with this patch, Joel commit if you also approve.
-Gedare
On Wed, Aug 20, 2014 at 11:47 AM, Joel Sherrill
wrote:
>
>
> On August 20, 2014 10:39:06 AM CDT, Gedare Bloom wrote:
>>Premysl,
>>
>>It loo
This BSP is intended to run on or1ksim (the main OpenRISC emulator).
Fixed version according to Joel comments from the mailing list.
---
c/src/aclocal/rtems-cpu-subdirs.m4 | 1 +
c/src/lib/libbsp/or1k/Makefile.am | 10 +
c/src/lib/libbsp/or1k/acinclude.m4
Hi Ben/Joel,
On Wed, Aug 20, 2014 at 10:16 PM, Joel Sherrill
wrote:
>
> On 8/20/2014 11:23 AM, Ritesh Harjani wrote:
>
> Hi Ben,
>
> Great work I must admit.
>
> I just have few question/suggestion. I am new to the community so high
> chances that I might be wrong here, but I noticed something
On 8/20/2014 11:23 AM, Ritesh Harjani wrote:
> Hi Ben,
>
> Great work I must admit.
>
> I just have few question/suggestion. I am new to the community so high
> chances that I might be wrong here, but I noticed something so I
> thought I should tell/ask.
>
>
> diff --git a/c/src/lib/libbsp/arm/b
Hi Ben,
Great work I must admit.
I just have few question/suggestion. I am new to the community so high
chances that I might be wrong here, but I noticed something so I thought I
should tell/ask.
diff --git a/c/src/lib/libbsp/arm/beagle/include/bsp.h
b/c/src/lib/libbsp/arm/beagle/include/bsp.h
On August 20, 2014 10:39:06 AM CDT, Gedare Bloom wrote:
>Premysl,
>
>It looks good. I just have two requests for you to do:
>1) Post the warnings you get when you compile.
Fixing them without papering over them is preferred but we can help if you get
stumped.
>2) Run the script
>http://git.rt
Hi Alan,
Thanks for the information. Besides my below queries, could you please also
let me know from where I should begin with ?
Like first I was thinking of understanding at least the initialization
routine from the starting point of raspberry pi. Starting with the
stack/vector initialization a
Premysl,
It looks good. I just have two requests for you to do:
1) Post the warnings you get when you compile.
2) Run the script
http://git.rtems.org/rtems-testing/tree/merge-helpers/check_submission
from within libbsp/arm/tms570 and post the results.
Thanks,
Gedare
_
Hi Hesham,
Thanks for the info.
On Wed, Aug 20, 2014 at 3:10 PM, Hesham Moustafa
wrote:
> Hi Ritesh,
>
> On Wed, Aug 20, 2014 at 11:28 AM, Ritesh Harjani
> wrote:
> > Hi All,
> >
> > I have been following RTEMS from quite some time rather I would say my
> > questions have been on & off from th
Included variants:
tms570ls3137_hdk_intram - place code and data into internal SRAM
tms570ls3137_hdk_sdram - place code into external SDRAM and data to SRAM
tms570ls3137_hdk - variant prepared for stand-alone RTEMS aplication
stored and running directly from flash. Not w
Ben, As far as getting this merged, all of my comments can be done as
a follow-on commit. -Gedare
On Thu, Jul 24, 2014 at 4:28 PM, Ben Gras wrote:
> Thanks for the fast & detailed review. Let me get back to it/you.
>
> In the meantime, any other feedback? From anyone I mean.
>
>
>
> On Thu, Jul 2
I already fixed that in my current version of virtualpok, but Janek's
patches were created against his version from April.
He already has the new version.
I maintain an own linkcmds in virtualpok, as I added a 0x1000 offset to
the start of the binary. It confused me to see some strange code in GD
On 20/08/14 15:53, Joel Sherrill wrote:
On 8/20/2014 8:12 AM, Daniel Cederman wrote:
>Hi,
>
>We are currently experiencing this bug reported by Sebastian Huber and I
>could not find any discussion on it on the list. I'm guessing that the
>simple solution of moving the call to Clock_driver_suppor
On 8/20/2014 8:59 AM, Sebastian Huber wrote:
> On 20/08/14 15:53, Joel Sherrill wrote:
>> On 8/20/2014 8:12 AM, Daniel Cederman wrote:
Hi,
We are currently experiencing this bug reported by Sebastian Huber and I
could not find any discussion on it on the list. I'm guessing that
>>> * Is the linkcmds change required for running pok-rtems?
>> For me, it was required. The old linkcmd script was causing undefined
>> TLS errors while building RTEMS.
> Please report this. This sounds like an independent issue which needs to
> be run down.
I believe this is a known issue. I thin
On 8/20/2014 8:12 AM, Daniel Cederman wrote:
> Hi,
>
> We are currently experiencing this bug reported by Sebastian Huber and I
> could not find any discussion on it on the list. I'm guessing that the
> simple solution of moving the call to Clock_driver_support_at_tick() to
> the critical secti
Hi Ritesh,
For the Raspberry Pi, Andre Marques added GPIO, SPI, and I2C support for
his Google Summer of Code project. When this code is merged, it will allow
many other devices to work on the Pi. There is still plenty of other work
to do on the Raspberry Pi BSP including:
- JTAG debugging - I have
Hi,
We are currently experiencing this bug reported by Sebastian Huber and I
could not find any discussion on it on the list. I'm guessing that the
simple solution of moving the call to Clock_driver_support_at_tick() to
the critical section of _TOD_Tickle_ticks() is not an acceptable
solution
On 20/08/2014 9:21 pm, Joel Sherrill wrote:
Chris.. We also have some gdb patches to work on upstreaming.
Yes. The patches need to be moved to gdb head and gdb changed the decls
and this broke the patches so need some work.
Chris
___
devel mailin
Thanks, checked in as:
http://git.rtems.org/rtems/commit/?id=0a66c1266f1f0968345b2a0bcb7acbeeba0c1d82
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains
On 20/08/14 13:21, Joel Sherrill wrote:
On August 20, 2014 1:26:19 AM CDT, Sebastian Huber
wrote:
On 19/08/14 18:38, Gedare Bloom wrote:
Anything holding it up at the moment?
For the SPARC GCC not all patches are in the GCC upstream, e.g. a
multilib
update is missing.
Can you provide a
On August 20, 2014 2:09:01 AM CDT, Ben Gras wrote:
>All,
>
>I'd love the Beagle BSP. I am fighting to find time to polish it,
>re-test it, and re-submit the patches.
>
>To decide whether that's feasible, is freezing the code for the release
>'any day now' or more like 'any week now'?
>
It won't
On August 20, 2014 1:26:19 AM CDT, Sebastian Huber
wrote:
>On 19/08/14 18:38, Gedare Bloom wrote:
>> Anything holding it up at the moment?
>
>For the SPARC GCC not all patches are in the GCC upstream, e.g. a
>multilib
>update is missing.
Can you provide a link?
Chris.. We also have some gdb
On 20/08/14 12:51, Peter Dufault wrote:
On Aug 19, 2014, at 12:38 , Gedare Bloom wrote:
Anything holding it up at the moment?
I'd like the PATCH for the MPC5554 flash put in, that's the only local change
I'm maintaining at the moment and it makes the cache operations reliable:
[PATCH] Pro
On Aug 19, 2014, at 12:38 , Gedare Bloom wrote:
> Anything holding it up at the moment?
I'd like the PATCH for the MPC5554 flash put in, that's the only local change
I'm maintaining at the moment and it makes the cache operations reliable:
[PATCH] Properly flush cache when writing to MPC55XX
On Tue, Aug 19, 2014 at 8:09 PM, Joel Sherrill
wrote:
>
> On 8/19/2014 1:00 PM, Hesham ALMatary wrote:
>> This BSP is intended to run on or1ksim (the main OpenRISC emulator).
>> ---
>> c/src/aclocal/rtems-cpu-subdirs.m4 | 1 +
>> c/src/lib/libbsp/or1k/Makefile.am
Hi Joel,
On Tue, Aug 19, 2014 at 8:09 PM, Joel Sherrill
wrote:
>
> On 8/19/2014 1:00 PM, Hesham ALMatary wrote:
>> This BSP is intended to run on or1ksim (the main OpenRISC emulator).
>> ---
>> c/src/aclocal/rtems-cpu-subdirs.m4 | 1 +
>> c/src/lib/libbsp/or1k/Makefile.am
Hi Ritesh,
On Wed, Aug 20, 2014 at 11:28 AM, Ritesh Harjani
wrote:
> Hi All,
>
> I have been following RTEMS from quite some time rather I would say my
> questions have been on & off from this community (although I haven't
> contributed anything yet). So, this mail is mainly regarding some help f
Hi All,
I have been following RTEMS from quite some time rather I would say my
questions have been on & off from this community (although I haven't
contributed anything yet). So, this mail is mainly regarding some help from
the community members so that I can pitch in to contribute something to
th
All,
I'd love the Beagle BSP. I am fighting to find time to polish it, re-test
it, and re-submit the patches.
To decide whether that's feasible, is freezing the code for the release
'any day now' or more like 'any week now'?
On Tue, Aug 19, 2014 at 11:43 PM, Joel Sherrill
wrote:
>
> On 8/19/
60 matches
Mail list logo
