> This means that our low-level design for providing thread stack protection
> may look something like this:-
>
> 1. For MPU based processors, the number of protected stacks will depend on
> the number of protection domains i.e. for MPUs with 8 protection domains we
> can have 7 protected
On Thu, May 21, 2020 at 6:36 PM Hesham Almatary
wrote:
>
> On Mon, 18 May 2020 at 06:10, Gedare Bloom wrote:
> >
> > you can push this one. I don't know if there are others?
>
> Thanks! Yeah, just one more here [1] but it's not vital/used yet.
>
If it's dead code, hold off until 6, thanks
> [1]
On Thu, May 21, 2020 at 5:43 AM Hesham Almatary
wrote:
> Yes, I completely agree with Gedare, and my reply doesn't entail
> otherwise. As Gedare stated a few requirements:
>
> "2. The basic protection isolates the text, rodata, and rwdata from
> each other. There is no notion of task-specific
On Mon, 18 May 2020 at 06:10, Gedare Bloom wrote:
>
> you can push this one. I don't know if there are others?
Thanks! Yeah, just one more here [1] but it's not vital/used yet.
[1] https://lists.rtems.org/pipermail/devel/2020-May/059772.html
>
> On Sun, May 17, 2020 at 7:06 PM Hesham Almatary
>
Hi
Appears to be something with the probe for gethostbyname. It fails with
this:
configure:19546: i386-rtems5-gcc -o conftest -qrtems
-B/home/joel/rtems-cron-5/rtems-source-builder/rtems/build/tmp/sb-1001-staging/i386-rtems5/lib/
