Hi Gedare,
> On Wed, 2022-11-02 at 09:58 -0600, Gedare Bloom wrote:
>
> t0 contains the address of .Lsecondary_processor_go
>
> start.S has:
> ```asm
> #if __riscv_xlen == 32
> .align 2
> #elif __riscv_xlen == 64
> .align 3
> #endif
>
> .Lsecondary_processor_go:
> ```
> Can you confirm
On 3/11/2022 2:50 pm, Chris Johns wrote:
> On 3/11/2022 10:30 am, Gedare Bloom wrote:
>> It was pointed out in Discord that the "third_party_list" command is
>> unusual with respect to other waf commands, which are given as oneword
>> formats (other than bsp_list and bsp_defaults). I think it
On 3/11/2022 10:30 am, Gedare Bloom wrote:
> It was pointed out in Discord that the "third_party_list" command is
> unusual with respect to other waf commands, which are given as oneword
> formats (other than bsp_list and bsp_defaults). I think it makes sense
> to go with such a oneword format for
It was pointed out in Discord that the "third_party_list" command is
unusual with respect to other waf commands, which are given as oneword
formats (other than bsp_list and bsp_defaults). I think it makes sense
to go with such a oneword format for consistent commands. So I will
instead start
t0 contains the address of .Lsecondary_processor_go
start.S has:
```asm
#if __riscv_xlen == 32
.align 2
#elif __riscv_xlen == 64
.align 3
#endif
.Lsecondary_processor_go:
```
Can you confirm the value of __riscv_xlen is properly defined to 64
for the PolarFire?
On Wed, Nov 2, 2022 at
On Wed, Nov 2, 2022 at 9:10 AM Gedare Bloom wrote:
>
> On Wed, Nov 2, 2022 at 1:10 AM Christian MAUDERER
> wrote:
> >
> > Hello Chris,
> >
> > Am 01.11.22 um 22:08 schrieb Chris Johns:
> > > On 2/11/2022 3:25 am, o...@c-mauderer.de wrote:> Is it a good idea to
> > > make it a
> > > mandatory
On Wed, Nov 2, 2022 at 9:14 AM Joel Sherrill wrote:
>
>
>
> On Wed, Nov 2, 2022 at 10:10 AM Gedare Bloom wrote:
>>
>> On Wed, Nov 2, 2022 at 1:10 AM Christian MAUDERER
>> wrote:
>> >
>> > Hello Chris,
>> >
>> > Am 01.11.22 um 22:08 schrieb Chris Johns:
>> > > On 2/11/2022 3:25 am,
On Wed, Nov 2, 2022 at 10:10 AM Gedare Bloom wrote:
> On Wed, Nov 2, 2022 at 1:10 AM Christian MAUDERER
> wrote:
> >
> > Hello Chris,
> >
> > Am 01.11.22 um 22:08 schrieb Chris Johns:
> > > On 2/11/2022 3:25 am, o...@c-mauderer.de wrote:> Is it a good idea to
> make it a
> > > mandatory
On Wed, Nov 2, 2022 at 1:10 AM Christian MAUDERER
wrote:
>
> Hello Chris,
>
> Am 01.11.22 um 22:08 schrieb Chris Johns:
> > On 2/11/2022 3:25 am, o...@c-mauderer.de wrote:> Is it a good idea to make
> > it a
> > mandatory attribute? It makes the yaml files
> >> bigger. It will only mean that we
On Tue, Nov 1, 2022 at 9:46 AM Joel Sherrill wrote:
>
>
>
> On Tue, Nov 1, 2022 at 8:55 AM Gedare Bloom wrote:
>>
>> On Mon, Oct 31, 2022 at 4:07 PM Chris Johns wrote:
>> >
>> > On 1/11/2022 2:59 am, Gedare Bloom wrote:
>> > > I am planning to roll out several text formatting changes over the
Hello Chris,
Am 01.11.22 um 22:08 schrieb Chris Johns:
On 2/11/2022 3:25 am, o...@c-mauderer.de wrote:> Is it a good idea to make it a
mandatory attribute? It makes the yaml files
bigger. It will only mean that we have to look for copy and paste bugs instead
of missing attributes if someone
Hi Sebastian,
The "Store/AMO address misaligned" trap occured in the "start.S"
at "amoswap.w zero, zero, 0(t0)" while testing the sample
application with the latest RTEMS master for RISC-V on
the Microchip PolarFire SoC.
The trap occured after this
12 matches
Mail list logo
