On 2020-02-06 17:15, Sebastian Huber wrote:
On 05/02/2020 22:13, Chris Johns wrote:
After all one of roles of the RTEMS Foundation is education.
I added a ticket for this:
https://devel.rtems.org/ticket/3867
Thanks
Chris
___
devel mailing list
d
On 06/02/2020 07:35, Amar Takhar wrote:
> On 2020-02-06 07:19 +0100, Christian Mauderer wrote:
>
>> Someone applied a FreeBSD patch directly to libbsd (which works well).
>> In that case git noted that the original author is in the "from" header
>> and send him an email that his patch has been ap
On 06/02/2020 07:35, Amar Takhar wrote:
Most likely it's a lot harder to construct a similar situation for the
RTEMS core repository. But I wouldn't entirely rule it out. Is there
some possibility to avoid such mails or do we just accept that in the
worst case someone unrelated receives mails?
On 2020-02-06 07:19 +0100, Christian Mauderer wrote:
> Someone applied a FreeBSD patch directly to libbsd (which works well).
> In that case git noted that the original author is in the "from" header
> and send him an email that his patch has been applied. He was a bit
> astonished to receive tha
On 05/02/2020 16:56, Jan Sommer wrote:
diff --git a/rtemsbsd/include/machine/clock.h b/rtemsbsd/include/machine/clock.h
index 936ffd88..415e2b55 100644
--- a/rtemsbsd/include/machine/clock.h
+++ b/rtemsbsd/include/machine/clock.h
@@ -1 +1,2 @@
-/* EMPTY */
+extern int tsc_is_invariant;
+extern u
On 05/02/2020 16:56, Jan Sommer wrote:
diff --git a/rtemsbsd/include/machine/bus.h b/rtemsbsd/include/machine/bus.h
deleted file mode 100644
index 2f0e7ad6..
--- a/rtemsbsd/include/machine/bus.h
+++ /dev/null
@@ -1,783 +0,0 @@
-/**
- * @file
- *
This change breaks all other architectur
On 06/02/2020 06:31, Amar Takhar wrote:
> On 2020-02-05 20:28 -0700, Gedare Bloom wrote:
>> I would like it to be a single email to indicate there is a new
>> breakage. Enough to indicate "hey go take a look at the full build
>> results! something is wrong here"
>
> That's what it does. Breakage
On 05/02/2020 22:13, Chris Johns wrote:
On 5/2/20 5:58 pm, Chris Johns wrote:
On 5/2/20 5:31 pm, Sebastian Huber wrote:
On 05/02/2020 03:09, Chris Johns wrote:
On 4/2/20 8:20 pm, Sebastian Huber wrote:
Hello,
I reworked the heavily out dated system initialization chapter in the RTEMS
BSP an
On 2020-02-05 20:28 -0700, Gedare Bloom wrote:
> I would like it to be a single email to indicate there is a new
> breakage. Enough to indicate "hey go take a look at the full build
> results! something is wrong here"
That's what it does. Breakage isn't always the same across builds. Waiting
un
On Wed, Feb 5, 2020 at 2:26 PM Chris Johns wrote:
>
> On 6/2/20 8:18 am, Amar Takhar wrote:
> > Currently emails sent out directly are limited to Joel, Chris and myself.
> > This
> > was setup during a testing phase.
> >
> > Typically what will happen is if a Builder within Buildbot changes from
RTEMS Release Build - 5.0.0-m2002
RTEMS 5 Release snapshot m2002 is avaliable for testing.
It can be found at:
https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2002
Please test and report any issues to the u...@rtems.org or devel@rtems.org
mailing lists or please raise a ticket.
If you
On 6/2/20 10:00 am, Amar Takhar wrote:
> On 2020-02-06 08:31 +1100, Chris Johns wrote:
>
>> Can we enable this for one BSP from each tier 1 architectures?
>
> Yes, can you provide a list?
The master list is here ...
https://git.rtems.org/rtems-tools/tree/config/rtems-bsps-tiers.ini
Chris
_
On 2020-02-06 08:31 +1100, Chris Johns wrote:
> Can we enable this for one BSP from each tier 1 architectures?
Yes, can you provide a list?
> > Buildbot does support both Pushover and Pushjet as well.
>
> Is this like social media and that stuff? ;)
Both are apps that allow for android / ios
On 6/2/20 8:18 am, Amar Takhar wrote:
> Currently emails sent out directly are limited to Joel, Chris and myself.
> This
> was setup during a testing phase.
>
> Typically what will happen is if a Builder within Buildbot changes from:
>
> Working -> Broken
> Broken -> Working
>
> It will s
Currently emails sent out directly are limited to Joel, Chris and myself. This
was setup during a testing phase.
Typically what will happen is if a Builder within Buildbot changes from:
Working -> Broken
Broken -> Working
It will send an email to the 'responsible users'. You can see a lis
On 2020-02-05 07:49 +0100, Sebastian Huber wrote:
> Hello Amar,
>
> thanks for setting up the Buildbot. I will probably receive most of the
> Working -> Broken emails.
Sure. Yes I agree that is what I've seen. :)
> If you are subscribed to the bu...@rtems.org mailing list, do you
> already g
On 6/2/20 6:01 am, Lou Woods wrote:
>> On 5/2/20 3:34 am, Lou Woods wrote:
>>> Added pc386 BSP support to rtems-tester.
>> How does this differ from pc.ini? Why is a copy needed?
> The bsp specified is different pc686 versus pc386. On second thought, perhaps
> the patch can be discarded. The exec
On 5/2/20 5:58 pm, Chris Johns wrote:
> On 5/2/20 5:31 pm, Sebastian Huber wrote:
>> On 05/02/2020 03:09, Chris Johns wrote:
>>> On 4/2/20 8:20 pm, Sebastian Huber wrote:
Hello,
I reworked the heavily out dated system initialization chapter in the RTEMS
BSP and Driver Guide:
>>>
> On 5/2/20 3:34 am, Lou Woods wrote:
> > Added pc386 BSP support to rtems-tester.
>
> How does this differ from pc.ini? Why is a copy needed?
The bsp specified is different pc686 versus pc386. On second thought, perhaps
the patch can be discarded. The execution is no different for the two BSPs,
Hello Lou,
We compiled the current master with your options and tried to run ticker.exe on
our hardware.
If we start RTEMS with -console=/dev/com1,115200 it works, but if we try to
configure it to use 9600 baud we also only get garbage data.
It seems the baud rate calculation is off for slower c
---
libbsd.py | 7 +--
waf_libbsd.py | 2 +-
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/libbsd.py b/libbsd.py
index bd24cd61..3823c03f 100644
--- a/libbsd.py
+++ b/libbsd.py
@@ -1556,6 +1556,8 @@ class dev_nic(builder.Module):
'sys/i386/include/specialr
- Files needed to make rtems-libbsd build again for i386
---
freebsd/sys/i386/include/machine/bus.h| 6 +
.../sys/x86/include/machine/intr_machdep.h| 175
freebsd/sys/x86/include/machine/legacyvar.h | 73
freebsd/sys/x86/include/machine/metadata.h| 57 +++
freeb
Hello,
I assembled a patch set which enabled building rtems-libbsd for i386-based BSPs
again (currently without dev_nic_e1000 enabled).
It's my first patch set for rtems-libbsd, but I tried to follow the contribute
guidelines as close as possible
I also have a similar patchset for amd64 in pre
- Update imported files to compile rtems-libbsd for i386 based BSPs
- Currently does not support the option "dev_nic_e1000 = on"
---
freebsd/sbin/sysctl/sysctl.c | 10 +-
freebsd/sys/dev/pci/pci_pci.c |2 +
freebsd/sys/i386/i386/legacy.c | 381 ---
On Wed, Feb 5, 2020, 12:58 AM Bran S wrote:
> Trying to solve ticket https://devel.rtems.org/ticket/1977
>
> The mode parameter sets access permissions for the created message queue.
> Examples:
> S_IRUSR 00400 user has read permission
> S_IWUSR 00200 user has write permission
> S_IXUSR 00100
On 05/02/2020 09:51, jan.som...@dlr.de wrote:
-Ursprüngliche Nachricht-
Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de]
Gesendet: Dienstag, 4. Februar 2020 17:15
An: rtems-de...@rtems.org
Cc: Sommer, Jan
Betreff: Re: [PATCH 3/3] i386: Port to RTEMS
On 31/01/2020 18:26
> -Ursprüngliche Nachricht-
> Von: Sebastian Huber [mailto:sebastian.hu...@embedded-brains.de]
> Gesendet: Dienstag, 4. Februar 2020 17:15
> An: rtems-de...@rtems.org
> Cc: Sommer, Jan
> Betreff: Re: [PATCH 3/3] i386: Port to RTEMS
>
> On 31/01/2020 18:26, Jan Sommer wrote:
>
> > diff -
Adjust copyright. Linker sets were introduced in 2015.
Update #2408.
Close #3865.
---
c-user/index.rst | 4 +--
c-user/linker_sets.rst | 69 +++---
2 files changed, 56 insertions(+), 17 deletions(-)
diff --git a/c-user/index.rst b/c-user/index.
Close #3865.
---
c-user/linker_sets.rst | 66 +++---
1 file changed, 52 insertions(+), 14 deletions(-)
diff --git a/c-user/linker_sets.rst b/c-user/linker_sets.rst
index f22c7bc..b02e290 100644
--- a/c-user/linker_sets.rst
+++ b/c-user/linker_sets.rst
@
29 matches
Mail list logo
