On 03/08/18 00:10, Joel Sherrill wrote:
This looks like a solution for having a way to test the Nios II.
There is support for Nios II in upstream Qemu since 2017.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax
Add an example.
Close #3482.
---
c-user/partition_manager.rst | 65
1 file changed, 54 insertions(+), 11 deletions(-)
diff --git a/c-user/partition_manager.rst b/c-user/partition_manager.rst
index 68761da..010f63a 100644
--- a/c-user/partition_manager
On 02/08/18 15:59, Gedare Bloom wrote:
It should be mentioned that if the user plans to store data types with
a stricter alignment requirement in the partitions, that they would
need to ensure the more strict alignment.
Oh, this was the reason why I opened this documentation file in the
first
Address multiple comments:
1. Refactored makedoc2rst class.
2. Refactored main module
3. Removed strcmp.rst
On Thu, Aug 2, 2018 at 9:44 PM, Dannie Huang wrote:
> ---
> README.md| 4 +-
> gen_rst_from_makedoc.py | 31 +--
> makedoc2rst.py | 99 +++
---
README.md| 4 +-
gen_rst_from_makedoc.py | 31 +--
makedoc2rst.py | 99
makedoc2rst_converter.py | 85 -
strcmp.rst | 47 ---
5 fil
Hello,
If you find some time, please do a final review of this patch and provide
suggestions if it's not mergeable yet :)
There are only three days left, I seek some advice on the wrapup work on
coverage
analysis . The current status is :
* This patch adds support to generate separate report for
On Thu, Aug 2, 2018 at 9:20 AM, Christian Mauderer
wrote:
> Am 02.08.2018 um 15:16 schrieb Gedare Bloom:
>> On Thu, Aug 2, 2018 at 1:28 AM, Christian Mauderer
>> wrote:
>>> Am 01.08.2018 um 16:28 schrieb Gedare Bloom:
Is this relied on for IPSec? How secure is it?
>>>
>>> Hello Gedare,
>>>
>
nvm I see the doc patch, thanks
On Thu, Aug 2, 2018 at 9:58 AM, Gedare Bloom wrote:
> This makes sense. Probably there is some documentation in c-user
> manual that needs tweaking.
>
> On Thu, Aug 2, 2018 at 8:55 AM, Sebastian Huber
> wrote:
>> The partition buffer area alignment required by rte
This makes sense. Probably there is some documentation in c-user
manual that needs tweaking.
On Thu, Aug 2, 2018 at 8:55 AM, Sebastian Huber
wrote:
> The partition buffer area alignment required by rtems_partition_create()
> was too strict since it was checked via _Addresses_Is_aligned() which
>
Close #3482.
---
c-user/partition_manager.rst | 24 +---
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/c-user/partition_manager.rst b/c-user/partition_manager.rst
index 68761da..61a6c7a 100644
--- a/c-user/partition_manager.rst
+++ b/c-user/partition_manager.r
The partition buffer area alignment required by rtems_partition_create()
was too strict since it was checked via _Addresses_Is_aligned() which
uses CPU_ALIGNMENT. The CPU_ALIGNMENT must take long double and vector
data type alignment requirements into account. For the partition
maintenance only p
Use the CPU_SIZEOF_POINTER alignment instead. The internal alignment
requirement is defined by the use of Chain_Node (consisting of two
pointers) to manage the free chain of partitions.
It seems that previously the condition
CPU_PARTITION_ALIGNMENT >= sizeof(Chain_Node)
was true on all CPU po
Am 02.08.2018 um 15:16 schrieb Gedare Bloom:
> On Thu, Aug 2, 2018 at 1:28 AM, Christian Mauderer
> wrote:
>> Am 01.08.2018 um 16:28 schrieb Gedare Bloom:
>>> Is this relied on for IPSec? How secure is it?
>>
>> Hello Gedare,
>>
>> the IPSec implementation in FreeBSD and therefore in RTEMS too use
On Thu, Aug 2, 2018 at 1:28 AM, Christian Mauderer
wrote:
> Am 01.08.2018 um 16:28 schrieb Gedare Bloom:
>> Is this relied on for IPSec? How secure is it?
>
> Hello Gedare,
>
> the IPSec implementation in FreeBSD and therefore in RTEMS too uses that
> function. So you are right that it is a critic
On Thu, Aug 2, 2018 at 12:55 AM, Dannie Huang wrote:
> ---
> .gitignore | 1 +
> gen_rst_from_makedoc.py | 71 ++--
> makedoc2rst_converter.py | 85
>
> 3 files changed, 96 insertions(+), 61 dele
I think these << >> blocks ought to be typeset as inline code blocks?
On Thu, Aug 2, 2018 at 1:03 AM, Dannie Huang wrote:
>
>
> On Wed, Aug 1, 2018 at 8:56 AM, Gedare Bloom wrote:
>>
>> On Tue, Jul 31, 2018 at 11:50 PM, Dannie Huang
>> wrote:
>> > Hi,
>> >
>> > This is the initial implementatio
The partition buffer area alignment required by rtems_partition_create()
was too strict since it was checked via _Addresses_Is_aligned() which
uses CPU_ALIGNMENT. The CPU_ALIGNMENT must take long double and vector
data type alignment requirements into account. For the partition
maintenance only p
Use the CPU_SIZEOF_POINTER alignment instead. The internal alignment
requirement is defined by the use of Chain_Node (consisting of two
pointers) to manage the free chain of partitions.
Update #3482.
---
cpukit/include/rtems/rtems/partimpl.h | 20 ++--
cpukit/score/
---
libbsd.txt | 128 +
1 file changed, 128 insertions(+)
diff --git a/libbsd.txt b/libbsd.txt
index c7a90f64..ba0ab2c4 100644
--- a/libbsd.txt
+++ b/libbsd.txt
@@ -1233,6 +1233,134 @@ workaround is to just restart it every time it exits
---
libbsd.py | 1 +
.../include/rtems/bsd/test/network-config.h.in | 2 +
testsuite/ipsec01/README | 5 +
.../setup_FreeBSD_as_communication_partner.sh | 82 +++
testsuite/ipsec01/test_main.c
The cloned interfaces have to be set up befor the interface list is
created. Otherwise it's not possible to configure a cloned interface
with a `ifconfig_gifX` line.
---
rtemsbsd/rtems/rtems-bsd-rc-conf-net.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/rtemsbsd/rtems/rtem
---
libbsd.py | 7 +
.../include/machine/rtems-bsd-rc-conf-services.h | 2 +
rtemsbsd/include/rtems/ipsec.h | 53 ++
rtemsbsd/rtems/rtems-bsd-racoon.c | 143 ++
rtemsbsd/rtems/rtems-bsd-rc-conf-ips
This ports the kernel space parts for ipsec and adds them to the
everything-buildset.
---
buildset/default.ini | 1 +
buildset/everything.ini | 1 +
freebsd/sys/net/if_ipsec.c | 4
libbsd.py| 2
---
freebsd/sys/net/if_ipsec.c | 1004
freebsd/sys/net/if_ipsec.h | 39 ++
2 files changed, 1043 insertions(+)
create mode 100644 freebsd/sys/net/if_ipsec.c
create mode 100644 freebsd/sys/net/if_ipsec.h
diff --git a/freebsd/sys/net/if_ipsec.c b/fre
---
rtemsbsd/include/machine/rtems-bsd-config.h | 21 +
rtemsbsd/include/machine/rtems-bsd-sysinit.h | 6 ++
2 files changed, 27 insertions(+)
diff --git a/rtemsbsd/include/machine/rtems-bsd-config.h
b/rtemsbsd/include/machine/rtems-bsd-config.h
index 72876d01..491d9a72
---
freebsd/sys/sys/random.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/freebsd/sys/sys/random.h b/freebsd/sys/sys/random.h
index 396ec2b1..996ca5c1 100644
--- a/freebsd/sys/sys/random.h
+++ b/freebsd/sys/sys/random.h
@@ -50,11 +50,21 @@ read_random_uio(void *a __unused, u_int
Source: https://svnweb.freebsd.org/ports/head/security/ipsec-tools/files/
revision 468617.
---
ipsec-tools/src/libipsec/libpfkey.h | 2 +-
ipsec-tools/src/libipsec/pfkey.c | 33 ---
ipsec-tools/src/racoon/gssapi.c | 5 ++
ipsec-tools/src/racoon/handler.h | 3 +-
i
---
buildset/everything.ini | 3 +++
1 file changed, 3 insertions(+)
diff --git a/buildset/everything.ini b/buildset/everything.ini
index e5593f59..0eee99e7 100644
--- a/buildset/everything.ini
+++ b/buildset/everything.ini
@@ -8,9 +8,12 @@ name = everything
extends = default.ini
[modules]
+#
In some applications, it's usefull if the files generated by lex or yacc
are not build automatically. With that it is for example possible to
create a wrapper source file that sets some defines before the generated
code is parsed.
---
builder.py| 12
waf_libbsd.py | 26 +++
Some variables generated by Yacc / Lex need a special treatment. That
had been done by manual editing of the generated headers in the past.
This patch integrate these changes into the generator.
---
userspace-header-gen.py | 32 +++-
1 file changed, 31 insertions(+), 1
This file seems to be imported from a long gone version.
---
freebsd/sys/crypto/sha2/sha2.h | 141 -
1 file changed, 141 deletions(-)
delete mode 100644 freebsd/sys/crypto/sha2/sha2.h
diff --git a/freebsd/sys/crypto/sha2/sha2.h b/freebsd/sys/crypto/sha2/sh
I've added a test (or more an example) for the ipsec support. In the
process of doing that, I also fixed a bug in rc.conf support for cloned
interfaces and added a RTEMS_BSD_CONFIG_IPSEC option that can be used
together with the rtems-bsd-config.h.
Note that most likely patch 7 and 9 are still too
On 02/08/18 10:32, Chris Johns wrote:
On 02/08/2018 17:47, Sebastian Huber wrote:
On 01/08/18 12:06, Hesham Almatary wrote:
On Wed, Aug 1, 2018 at 10:18 AM, Sebastian Huber wrote:
Module: rtems
Branch: master
Commit: 529154bad207a42a6d0f03343c7e215eab97ced5
Changeset:
http://git.rtem
On 02/08/2018 17:47, Sebastian Huber wrote:
> On 01/08/18 12:06, Hesham Almatary wrote:
>> On Wed, Aug 1, 2018 at 10:18 AM, Sebastian Huber wrote:
>>> Module: rtems
>>> Branch: master
>>> Commit: 529154bad207a42a6d0f03343c7e215eab97ced5
>>> Changeset:
>>> http://git.rtems.org/rtems/commit
On 01/08/18 12:06, Hesham Almatary wrote:
On Wed, Aug 1, 2018 at 10:18 AM, Sebastian Huber wrote:
Module:rtems
Branch:master
Commit:529154bad207a42a6d0f03343c7e215eab97ced5
Changeset:
http://git.rtems.org/rtems/commit/?id=529154bad207a42a6d0f03343c7e215eab97ced5
Author:Sebas
35 matches
Mail list logo