This documentation is in ReST and has been ported
from rtems-tools.git. There are a few changes and
it contains the format for the ini configuration
files.
---
images/user/rtemswhitebg.jpg | Bin 0 -> 117890 bytes
user/tools/rtems-tester.rst | 639 +++
2 fi
Hello,
I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for RSB
and built RSB. But when I am trying to build rtems-generic target I get the
mistake.
This is my sequence of steps:
git clone git://git.rtems.org/rtems-source-builder.git
#patch applied here
mkdir -p ./development/
Unrelatedly to the contents, please use -v2 to identify revised patches.
On Tue, May 30, 2017 at 2:01 AM, Sebastian Huber
wrote:
> Hello Hesham,
>
> thanks for your RISCV support.
>
> - Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary
> heshamelmat...@gmail.com:
>
>> ---
>> rtems/config/4.12/
On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov wrote:
> Hello,
> I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for RSB
> and built RSB. But when I am trying to build rtems-generic target I get the
> mistake.
> This is my sequence of steps:
>
> git clone git://git.rtems.org/r
2017-05-30 18:31 GMT+03:00 Gedare Bloom :
> On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov
> wrote:
> > Hello,
> > I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for
> RSB
> > and built RSB. But when I am trying to build rtems-generic target I get
> the
> > mistake.
> > This
On Tue, May 30, 2017 at 12:09 PM, Denis Obrezkov
wrote:
> 2017-05-30 18:31 GMT+03:00 Gedare Bloom :
>>
>> On Tue, May 30, 2017 at 7:49 AM, Denis Obrezkov
>> wrote:
>> > Hello,
>> > I am trying to build RTEMS for RISC-V BSP. I applied Hesham's patch for
>> > RSB
>> > and built RSB. But when I am t
On Tue, May 30, 2017 at 1:10 PM, Tanu Hari Dixit wrote:
> Hello Gedare,
>
> I just added the image following what was already in rtems-tools.git
> repo. Maybe it is not really needed there. Maybe it was added to the
> previous doc because it was a stand-alone doc. I will pull that out.
> What do y
Contains the ReST file for documentation for rtems-tester.
Also contains the new format for the ini configuration files.
---
user/tools/rtems-tester.rst | 639
1 file changed, 639 insertions(+)
create mode 100644 user/tools/rtems-tester.rst
diff --git
---
images/user/rtemswhitebg.jpg | Bin 0 -> 117890 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 images/user/rtemswhitebg.jpg
diff --git a/images/user/rtemswhitebg.jpg b/images/user/rtemswhitebg.jpg
new file mode 100644
index
.
Hello Gedare,
I have sent the patches separately.
Thank you,
Tanu.
On Tue, May 30, 2017 at 10:50 PM, Gedare Bloom wrote:
> On Tue, May 30, 2017 at 1:10 PM, Tanu Hari Dixit
> wrote:
>> Hello Gedare,
>>
>> I just added the image following what was already in rtems-tools.git
>> repo. Maybe it is
Hi,
I'm trying to run rtems-test for pc386 with the added --coverage tag for
couverture-qemu. All tests default to dry-run because of errors in qemu.cfg
error: qemu.cfg:81: execute failed: qemu-system-i386 -m 128 -boot b -hda
/home/cpod/development/rtems/test/rtems-tools/tester/rtems/testing/cove
Hi Cillian,
I usually do a git grep -i "" to find out where possibly a
macro or variable is used elsewhere in the code. Not the best way, but
works mostly.
Also %{qemu_cmd} has been defined here in the same file
(https://devel.rtems.org/browser/rtems-tools/tester/rtems/testing/qemu.cfg#L60).
I als
Hi Denis,
Yes, that's a leftover flag that used to exist in the 2-year-old
toolchain. There's no m32 (or m64) flag anymore. I submitted a fix
(54bf80e) to my repo. You'll most likely get similar issues though in
later stages. Fix-ups are welcome.
Cheers,
Hesham
On Wed, May 31, 2017 at 3:19 AM, G
Hi Sebastian,
On Tue, May 30, 2017 at 4:01 PM, Sebastian Huber
wrote:
> Hello Hesham,
>
> thanks for your RISCV support.
>
> - Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary
> heshamelmat...@gmail.com:
>
>> ---
>> rtems/config/4.12/rtems-riscv32.bset | 32 +++
>> rtems/
On Wed, May 31, 2017 at 1:21 AM, Gedare Bloom wrote:
> Unrelatedly to the contents, please use -v2 to identify revised patches.
>
Yes please ignore the first patch, thanks for the reminder.
> On Tue, May 30, 2017 at 2:01 AM, Sebastian Huber
> wrote:
>> Hello Hesham,
>>
>> thanks for your RISCV s
Hi Tanu,
Thanks for the help, I had been grepping through the files and backtracking
through the definitions. I was just wondering was there a quick way to just
print it out that I didn't know about.
I also couldn't find the recipe for the bsp but the previous work I'm
continuing on from worked f
Ah nevermind.. just realised its already printing them out.
On 30 May 2017 9:50 pm, "Cillian O'Donnell" wrote:
> Hi Tanu,
>
> Thanks for the help, I had been grepping through the files and
> backtracking through the definitions. I was just wondering was there a
> quick way to just print it out t
- Am 30. Mai 2017 um 22:41 schrieb Hesham Almatary heshamelmat...@gmail.com:
> Hi Sebastian,
>
> On Tue, May 30, 2017 at 4:01 PM, Sebastian Huber
> wrote:
>> Hello Hesham,
>>
>> thanks for your RISCV support.
>>
>> - Am 30. Mai 2017 um 3:51 schrieb Hesham Almatary
>> heshamelmat...@gm
Hello Gedare,
could you announce the time of the next GSoC meeting(s)?
--
Regards, Denis Obrezkov
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Yes, tomorrow at 11am EST (GMT-4) again. These will be recurring
events every Wednesday at the same time (unless I/Joel don't show up!)
On Tue, May 30, 2017 at 6:51 PM, Denis Obrezkov wrote:
> Hello Gedare,
>
> could you announce the time of the next GSoC meeting(s)?
>
> --
> Regards, Denis Obrez
EDIT: 10am EST (GMT-4)
10a-11a.
On Tue, May 30, 2017 at 7:25 PM, Gedare Bloom wrote:
> Yes, tomorrow at 11am EST (GMT-4) again. These will be recurring
> events every Wednesday at the same time (unless I/Joel don't show up!)
>
> On Tue, May 30, 2017 at 6:51 PM, Denis Obrezkov
> wrote:
>> Hello
Thanks. Next time use the -v2 flag to specify a revised version of a patch.
On Tue, May 30, 2017 at 2:55 PM, Tanu Hari Dixit wrote:
> Hello Gedare,
>
> I have sent the patches separately.
>
> Thank you,
> Tanu.
>
> On Tue, May 30, 2017 at 10:50 PM, Gedare Bloom wrote:
>> On Tue, May 30, 2017 at
Does it work without --coverage flag?
On Tue, May 30, 2017 at 5:23 PM, Cillian O'Donnell
wrote:
> Ah nevermind.. just realised its already printing them out.
>
> On 30 May 2017 9:50 pm, "Cillian O'Donnell" wrote:
>>
>> Hi Tanu,
>>
>> Thanks for the help, I had been grepping through the files and
On 31/05/2017 03:10, Tanu Hari Dixit wrote:
I just added the image following what was already in rtems-tools.git
repo. Maybe it is not really needed there. Maybe it was added to the
previous doc because it was a stand-alone doc.
Yes this is correct. The User Manual is newer and has a consisten
On 29/05/2017 22:29, Tanu Hari Dixit wrote:
From: tokencolour
Could we please have your name in the commit? It make the git log much
more meaningful. For example:
From: Tanu Hari Dixit
Thanks
Chris
2 typos fixed
---
README.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-
On 29/05/2017 19:39, Cillian O'Donnell wrote:
I added #include "rld.h" in rtemstoolkit/rld-process.h and that was it,
build successful, happy days!
Excellent work. Could you please post a patch for rtems-tools.git master
to fix this?
Thanks
Chris
_
Hi,
I am testing RSB patches to move 4.12 to gcc 7.1.0/binutils-2.28.
The SH arch fails to build on FreeBSD 11.0. The issue is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80923.
RTEMS BSP Builder results summary for:
$ rtems-bsp-builder --rtems-tools=/build/rtems/tools/4.12-7.1
--rtems=/opt/wo
Hi Denis,
Please use priv-1.10 branch. I rebased it (against master) and added
some fixes to make the build progress. Still, there's more work
needed. Your contributions are welcomed.
Cheers,
Hesham
.
On Wed, May 31, 2017 at 6:16 AM, Hesham Almatary
wrote:
> Hi Denis,
>
> Yes, that's a leftover
28 matches
Mail list logo
