> On 11/03/2015 1:27 am, Karel Gardas wrote:
> > Yes, this is a big patch but if you do not merge it now and later
> > following waf work you do tree/file placement refactoring than the patch
> > would be even harder to merge.
I was thinking this would land in 4.12 then waf would be based off of t
On 11/03/2015 4:17 am, Richa Sehgal wrote:
I am Richa Sehgal currently pursuing Master’s at University of Illinois
Urbana Champaign, USA. I did my undergraduate from Indian Institute of
Technology Delhi (IIT-Delhi).
I am interested in contributing to the Run Time Tracing project in GSOC
2015.
On Fri, Mar 13, 2015 at 8:38 PM, Chris Johns wrote:
> On 14/03/2015 12:30 am, Gedare Bloom wrote:
>>
>> I would like to consider landing the drvmgr and pci patch-set as a
>> sparc-specific feature (e.g. only included in builds for sparc.)
>
>
> How is this controlled or are you saying we state in
On 14/03/2015 12:30 am, Gedare Bloom wrote:
I would like to consider landing the drvmgr and pci patch-set as a
sparc-specific feature (e.g. only included in builds for sparc.)
How is this controlled or are you saying we state in the release notes
this is only currently tested on SPARC BSPs ?
On 11/03/2015 1:27 am, Karel Gardas wrote:
On 03/ 9/15 08:31 PM, Amar Takhar wrote:
On 2015-03-09 14:23 -0400, Gedare Bloom wrote:
We are close to branching 4.11, but I think there may be value in
merging the patch set for 4.11. Would it be acceptable to all if we
I would be against this.
On 14/03/2015 10:30 am, Marcos Díaz wrote:
Hi,
Indeed we have it working but we only can use it with the cache disabled
because the system crashes otherway.
About what's next, I think there should be a revision of the code and
debugging in order to make it work with the cache enabled. And also s
On 13/03/2015 7:29 pm, Sebastian Huber wrote:
On 12/03/15 18:41, Joel Sherrill wrote:
Hi
Many BSPs can link a test but don't actually have enough memory
to run the test. They will fail in the first few lines when the requested
memory for the RTEMS work area is not available. I hacked together
On 13/03/2015 7:37 pm, emanuel stiebler wrote:
On 2015-03-13 05:55, Chris Johns wrote:
Have a look in this line ...
https://git.rtems.org/rtems-source-builder/tree/source-builder/sb/windows.py#n56
.. and remove line 57 and make line 58 'host_triple = build_triple' so
the host and build nam
On March 13, 2015 6:30:40 PM CDT, "Marcos Díaz"
wrote:
>Hi,
>Indeed we have it working but we only can use it with the cache
>disabled because the system crashes otherway.
This could be an MMU setup issue. A region marked cacheable that shouldn't be.
>About what's next, I think there should b
Hi,
Indeed we have it working but we only can use it with the cache disabled
because the system crashes otherway.
About what's next, I think there should be a revision of the code and
debugging in order to make it work with the cache enabled. And also see the
way of submitting it to rtems. It was
Hi Ragu.
We're successfully using it in production code. We had no time to
contribute it yet, AFAIK blocked in the source builder. Marcos,
details please?
Daniel.
On Fri, Mar 13, 2015 at 6:00 PM, ragu nath wrote:
> Hi,
>
> I would like to know what is the status of running lwIP on beaglebone
Hi,
I would like to know what is the status of running lwIP on beaglebone
black on RTEMS. I understand that there was some considerable amount
of work already done on running lwIP on BBB. It would be really
helpful if I can get the details on what has already been done and
what are the remainin
Closes #2304
---
cpukit/score/cpu/or1k/rtems/score/cpu.h | 4
1 file changed, 4 insertions(+)
diff --git a/cpukit/score/cpu/or1k/rtems/score/cpu.h
b/cpukit/score/cpu/or1k/rtems/score/cpu.h
index 0be9bca..9afb381 100644
--- a/cpukit/score/cpu/or1k/rtems/score/cpu.h
+++ b/cpukit/score/cpu/or1
You should read the blog pages starting at
http://alanstechnotes.blogspot.com/2013/03/rtems-on-raspberry-pi.html
There are a few blog posts there. Some is outdated but mostly it
should work I guess, using git.rtems,org for the git repositories now
that all support is in "upstream" RTEMS Project re
Hi,
I am new to using Raspberry pi. I saw the READ ME for Raspberry pi BSP. I
have got the files stated there, except the config.txt. I also read some
steps on the Raspberry pi website regarding getting the image onto the SD
card.
Also, I do not understand what the stripping step will do. I need
On Fri, Mar 13, 2015 at 12:05 PM, Юрий Шевцов wrote:
> Am I right that completing Hello is just change and somehow submit lines in
> samples/hello/init.c ? And how can I submit the proof, of course?)
>
Correct. You can send an email here with patch attached and a link to
a screenshot posted somewh
Hi,
RPi is a good open project. The BSP is in c/src/lib/libbsp/arm/raspberrypi
I think the prior gsoc effort has some links/pointers in it. You will
need to have the board and prove you can build RTEMS for it and run
it.
Gedare
On Fri, Mar 13, 2015 at 11:43 AM, Юрий Шевцов wrote:
> Hello there
Am I right that completing Hello is just change and somehow submit lines in
samples/hello/init.c ? And how can I submit the proof, of course?)
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Hello there! I would like to participate in GSoC with RTEMS Project. As for
now I'm considering to improve RPi support. Project's page says that some
progress has done. Where can I found this code and some examples for other
boards maybe. I have lurked RTEMS git repo a little but haven't found any
On March 13, 2015 8:30:46 AM CDT, Gedare Bloom wrote:
>On Fri, Mar 13, 2015 at 1:04 AM, Chris Johns wrote:
>> On 11/03/2015 1:33 am, Amar Takhar wrote:
>>>
>>> Can we come up with a plan for branching 4.11?
>>>
>>> We need to push off any commits made that are unrelated to tickets
>open in
>>>
On Fri, Mar 13, 2015 at 1:04 AM, Chris Johns wrote:
> On 11/03/2015 1:33 am, Amar Takhar wrote:
>>
>> Can we come up with a plan for branching 4.11?
>>
>> We need to push off any commits made that are unrelated to tickets open in
>> milestone 4.11 to the next release. This way any changes we make
On 2015-03-13 13:57 +0100, Sebastian Huber wrote:
>
>
> On 13/03/15 13:38, Amar Takhar wrote:
> > On 2015-03-13 09:45 +0100, Sebastian Huber wrote:
> >>> #include
> >>> -Iinclude/cpu/sparc/sis/
> >> This is exactly what we need.
> > I agree we need this right now but it's not a requirement for t
On 13/03/15 13:38, Amar Takhar wrote:
On 2015-03-13 09:45 +0100, Sebastian Huber wrote:
#include
-Iinclude/cpu/sparc/sis/
This is exactly what we need.
I agree we need this right now but it's not a requirement for the future.
For me this is a requirement for the future. A lot of applicati
On 2015-03-13 09:45 +0100, Sebastian Huber wrote:
> > #include
> > -Iinclude/cpu/sparc/sis/
>
> This is exactly what we need.
I agree we need this right now but it's not a requirement for the future.
> > The whole purpose of explicit paths it to avoid picking up the wrong header
> > file which
On 13/03/15 11:43, Jakub Jelinek wrote:
On Fri, Mar 13, 2015 at 11:38:12AM +0100, Sebastian Huber wrote:
I would like to commit this patch to GCC 4.9 and 5.0.
libgomp/ChangeLog
2015-03-13 Sebastian Huber
* configure.tgt (*-*-rtems*): Use local-exec TLS model.
* configure.ac
I would like to commit this patch to GCC 4.9 and 5.0.
libgomp/ChangeLog
2015-03-13 Sebastian Huber
* configure.tgt (*-*-rtems*): Use local-exec TLS model.
* configure.ac (*-*-rtems*): Assume Pthread is supported.
(pthread.h): Check for this header file.
* config
Merge parts of the latest from FreeBSD to Newlib. This has
two reasons.
1. We want to use the FreeBSD timecounters for timekeeping in RTEMS.
See also https://devel.rtems.org/ticket/2271.
2. This makes the port of the network stack from FreeBSD easier.
newlib/ChangeLog
2015-03-12 Sebastian Hub
On 11/03/15 22:18, Joel Sherril wrote:
+/**
+ * @brief Benchmark Timer Value Type
+ *
+ * This type is used to contain benchmark times. The units are BSP specific.
+ */
+typedef uint32_t benchmark_timer_t;
The @brief for functions should be a complete sentence and not a headline.
--
Sebastia
On 13/03/15 01:48, Amar Takhar wrote:
On 2015-03-13 11:36 +1100, Chris Johns wrote:
There is complexity in terms of what a user sees which we need to address.
I also have no problem with more than one -I when building RTEMS and
feel we have too. I cannot see a suitable way around this.
This
On 2015-03-13 05:55, Chris Johns wrote:
Have a look in this line ...
https://git.rtems.org/rtems-source-builder/tree/source-builder/sb/windows.py#n56
.. and remove line 57 and make line 58 'host_triple = build_triple' so
the host and build names are the same by default.
If this works you mi
On 12/03/15 18:41, Joel Sherrill wrote:
Hi
Many BSPs can link a test but don't actually have enough memory
to run the test. They will fail in the first few lines when the requested
memory for the RTEMS work area is not available. I hacked together
a script which adds together the code, data, b
On 13/03/15 06:04, Chris Johns wrote:
1. We need a suitable newlib snapshot to reference.
I have one pending Newlib patch, so the March snapshot would be nice.
This gives us two weeks from now to commit everything Newlib related.
--
Sebastian Huber, embedded brains GmbH
Address : Dornier
32 matches
Mail list logo
