On Tue, Aug 15, 2023, 13:10 Joel Sherrill wrote:
>
>
> On Tue, Aug 15, 2023 at 11:57 AM Brett Sterling <
> brett.sterl...@odysseysr.com> wrote:
>
>> Hello all!
>>
>> To get this out of the way prior to all of the requested debugging
>> information - I don't need the legacy stack, any networking s
On Tue, Aug 15, 2023 at 11:57 AM Brett Sterling <
brett.sterl...@odysseysr.com> wrote:
> Hello all!
>
> To get this out of the way prior to all of the requested debugging
> information - I don't need the legacy stack, any networking stack will do.
> I started with legacy because that was what was
Hello all!
To get this out of the way prior to all of the requested debugging information
- I don't need the legacy stack, any networking stack will do. I started with
legacy because that was what was shown on the RTEMS documentation pages. We're
trying to integrate RTEMS into our system and
I add Vijay since he has been working with this.
On Tue, Aug 15, 2023 at 9:27 AM Brett Sterling
wrote:
> Hello all,
>
> My goal is to integrate networking into our RTEMS solution, so I started
> here: https://docs.rtems.org/branches/master/legacy-networking/index.html.
>
> But, as soon as I had
Hello all,
My goal is to integrate networking into our RTEMS solution, so I started here:
https://docs.rtems.org/branches/master/legacy-networking/index.html.
But, as soon as I had started, I hit a failure. I tried the 'quick start'
(https://docs.rtems.org/branches/master/legacy-networking/qui
