That's definitely very illuminating, thank you so much for all the details!
A few more questions that have arisen for me. Feel free to skip over
them (I'll likely figure them out given enough time, so I'm only
asking in case any of them are obvious to anyone):
- The i386 doesn't use
On Wed, Aug 1, 2018 at 9:15 AM, Amaan Cheval wrote:
> That's definitely very illuminating, thank you so much for all the details!
>
> A few more questions that have arisen for me. Feel free to skip over
> them (I'll likely figure them out given enough time, so I'm only
> asking in case any of
On Wed, Aug 1, 2018 at 10:11 AM, Gedare Bloom wrote:
> On Wed, Aug 1, 2018 at 9:15 AM, Amaan Cheval
> wrote:
> > That's definitely very illuminating, thank you so much for all the
> details!
> >
> > A few more questions that have arisen for me. Feel free to skip over
> > them (I'll likely
---
tester/rtems/testing/coverage/symbol-sets.ini | 48 +--
1 file changed, 45 insertions(+), 3 deletions(-)
diff --git a/tester/rtems/testing/coverage/symbol-sets.ini
b/tester/rtems/testing/coverage/symbol-sets.ini
index a2ec7bc..aac0b9b 100644
---
On Wed, Aug 1, 2018 at 11:11 AM, Gedare Bloom wrote:
> On Wed, Aug 1, 2018 at 9:15 AM, Amaan Cheval wrote:
>> That's definitely very illuminating, thank you so much for all the details!
>>
>> A few more questions that have arisen for me. Feel free to skip over
>> them (I'll likely figure them
Is this relied on for IPSec? How secure is it?
On Wed, Aug 1, 2018 at 4:04 AM, Christian Mauderer
wrote:
> ---
> 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
>
On Tue, Jul 31, 2018 at 11:42 PM, Dannie Huang wrote:
> From: Danxue Huang <36866155+dh0...@users.noreply.github.com>
>
> ---
> .gitignore | 2 +
> README.md | 2 +
> gen_rst_from_makedoc.py | 125
>
> rst.py
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
Hello,
this patch set adds IPSec functionality to libbsds everything build set.
The first four patches prepare some necessary functionality. Patch 5 and
6 add the if_ipsec driver. 7 to 9 import ipsec-tools from the FreeBSD
ports. 10 is just some readability improvement for the build set. 11
adds
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
---
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,
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
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 +-
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
---
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 ++
---
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]
On 01/08/2018 15:26, Sebastian Huber wrote:
> On 31/07/18 21:17, Joel Sherrill wrote:
>> Hi
>>
>> The build of all BSPs looks a lot better thanks to the patch
>> Sebastian pushed. Only the tms570 variants fail to build.
>> They end with this:
>>
>> error: mv -f spqreslib/.deps/spqreslib-init.Tpo
Okay, I think I understand finally. Sorry about the rambling!
When rtems_interrupt_catch is called, that's installing a "raw" ISR by
modifying the processor specific table itself, so _ISR_Handler is
never called, but the user ISR is.
When rtems_interrupt_handler_install is called, that's an
I have started to reply twice but you jumped in ahead. :)
On Wed, Aug 1, 2018 at 12:12 PM, Amaan Cheval
wrote:
> If my previous email _is_ in fact correct, could someone confirm?
> Because this excerpt in the documentation here seems to contradict it
> (which was what lead to the confusion in
Thanks for the background!
Let's use the gen5200 as the ongoing example - my confusion arises
here (correct me if any of the following points is incorrect!). In
overly simplified call chains:
Register interrupt handler:
- bsp_interrupt_facility_initialize() -> ppc_exc_set_handler(vec,
If my previous email _is_ in fact correct, could someone confirm?
Because this excerpt in the documentation here seems to contradict it
(which was what lead to the confusion in the first place):
https://docs.rtems.org/branches/master/c-user/interrupt_manager.html#establishing-an-isr
With my
On Tue, Jul 31, 2018 at 11:50 PM, Dannie Huang wrote:
> Hi,
>
> This is the initial implementation commit of converting newlib markup to
> rst, the example .rst file looks like this photo (see attached photo
> please).
>
Can we see a side-by-side comparison with how newlib's documentation looks?
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 implementation commit of converting newlib markup to
> > rst, the example .rst file looks like this photo (see attached photo
> > please).
> >
>
>
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 critical one for security.
`read_random` is a low-level FreeBSD random
---
.gitignore | 1 +
gen_rst_from_makedoc.py | 71 ++--
makedoc2rst_converter.py | 85
3 files changed, 96 insertions(+), 61 deletions(-)
create mode 100644 makedoc2rst_converter.py
diff --git
Am 01.08.2018 um 10:04 schrieb Christian Mauderer:
> Hello,
>
> this patch set adds IPSec functionality to libbsds everything build set.
>
> The first four patches prepare some necessary functionality. Patch 5 and
> 6 add the if_ipsec driver. 7 to 9 import ipsec-tools from the FreeBSD
> ports.
On 02/08/2018 15:09, Christian Mauderer wrote:
> Just a note: two of the patches are too big for the mailing list.
Yeah, 4986580 + 1207698 bytes. Too big to allow.
Chris
___
devel mailing list
devel@rtems.org
28 matches
Mail list logo
