On Thu, Oct 31, 2019 at 5:14 AM Joel Sherrill wrote:
>
>
>
> On Thu, Oct 31, 2019, 1:30 AM Sebastian Huber
> wrote:
>>
>> On 30/10/2019 10:35, Vaibhav Gupta wrote:
>> > So what's the final stand on this?
>> >
>> > Should be working on standalone guide or add the contents to RTEMS
>> > Software E
On Fri, Nov 1, 2019 at 3:16 AM Hesham Almatary
wrote:
>
> On Thu, 31 Oct 2019 at 08:52, Sebastian Huber
> wrote:
> >
> > On 29/10/2019 10:34, Hesham Almatary wrote:
> > > This is to hide the new BSPs from GCC builds when building
> > > all RISC-V BSPs with configure --target=riscv-rtems5
> >
> >
Hi Sebastian,
On Thu, Oct 31, 2019 at 2:31 AM Sebastian Huber
wrote:
>
> I have to add that some progress is blocked by a Doorstop pull request:
>
> https://github.com/doorstop-dev/doorstop/pull/428
>
How are things going with the Doorstop community, they are responsive
to your requests and engag
I am not sure about the current state of the Raspberry Pi BSPs, but I can try
to explain the differences in the models and how that might affect RTEMS
support:
* The original single Core Raspberry Pis which include the B, B+, A+ were
the target for the original BSP
* The Pi Zero is a $5
On Thu, 31 Oct 2019 at 08:52, Sebastian Huber
wrote:
>
> On 29/10/2019 10:34, Hesham Almatary wrote:
> > This is to hide the new BSPs from GCC builds when building
> > all RISC-V BSPs with configure --target=riscv-rtems5
>
> Can you still build the clang variants after this change?
>
No. That's ju
