On 10/8/19 2:54 am, Sebastian Huber wrote:
> just my 2ct with respect to the lacking device tree support in the Xilinx
> Zynq BSP. This is just a historic accident. The BSP was written before we had
> any device tree support in RTEMS.
FDT support for the Zynq would be nice however it would
On 10/8/19 1:23 am, Jonathan Brandmeyer wrote:
> On Wed, Aug 7, 2019 at 7:07 PM Chris Johns wrote:
>
>> I dislike BSP_OPTS for a few reason; I will not expand on that topic here. I
>> can
>>
>>
>> 1. Add option support to the RSB. I am not exactly sure how this could be
>> made
>> to work
On 8/9/19 8:34 PM, Jiri Gaisler wrote:
>
>
> On 8/9/19 3:24 PM, Joel Sherrill wrote:
>> I thought I saw a patch pushed yesterday afternoon but a fresh build today
>> shows the same
>> breakage.
>>
>> Jiri .. feel free to push a fix for this and I will test when I get back.
> The problem right
On 8/9/19 3:24 PM, Joel Sherrill wrote:
> I thought I saw a patch pushed yesterday afternoon but a fresh build
> today shows the same
> breakage.
>
> Jiri .. feel free to push a fix for this and I will test when I get back.
The problem right now is that RSB has some breakage which causes the
Hello Nils,
thanks for the patch. It sounds like we will get a behaviour that is
more similar to FreeBSD one with it. But it has the potential to have a
big influence on existing BSPs so it would be good to have some more
feedback for it before merging it.
On 09/08/2019 15:53, Nils Hölscher
Hello Nils,
sorry, I missed the patch on the mailing list.
Best regards
Christian
On 09/08/2019 20:07, Nils Hölscher wrote:
> Hi Christian,
>
> I want to thank you again, since you actually helped me a lot with this
> problem.
> But I already patched this problem, didn't I.
>
> Thanks,
>
Hi Christian,
I want to thank you again, since you actually helped me a lot with this
problem.
But I already patched this problem, didn't I.
Thanks,
Nils
Christian Mauderer schrieb am Fr., 9. Aug. 2019, 19:50:
> Hello Nils,
>
> great that you found your problem. It sounds like it is a general
Hello Nils,
great that you found your problem. It sounds like it is a general bug in
libbsd. What did you change and do you have a patch that would fix this?
Best regards
Christian
On 09/08/2019 15:42, Nils Hölscher wrote:
> Hi,
>
> I was able to resolve the problem.
> The reason that all the
>
>
> Ok, good. Please always check if the babeltrace and Trace Compass give
> the right results after the changes.
>
Yes. Both are displaying same output.
>
> If you use cctx->switch_event[ item->cpu ] and similar a couple of times
> in a function, then please assign it to a local pointer and
Hello,
just my 2ct with respect to the lacking device tree support in the Xilinx Zynq
BSP. This is just a historic accident. The BSP was written before we had any
device tree support in RTEMS. In general, I think we should stick to what Linux
does on a certain platform. If it boots via a
- Am 9. Aug 2019 um 16:11 schrieb joel j...@rtems.org:
> On Fri, Aug 9, 2019, 8:45 AM Sebastian Huber <
> sebastian.hu...@embedded-brains.de> wrote:
>
>>
>> - Joel Sherrill schrieb:
>> > Coming in late but there isn't there a helper method to turn object names
>> > into strings from
On Wed, Aug 7, 2019 at 7:07 PM Chris Johns wrote:
> I dislike BSP_OPTS for a few reason; I will not expand on that topic here. I
> can
>
>
> 1. Add option support to the RSB. I am not exactly sure how this could be made
> to work but something like ...
>
>
On Fri, Aug 9, 2019, 8:45 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
> - Joel Sherrill schrieb:
> > Coming in late but there isn't there a helper method to turn object names
> > into strings from either 32 bit values or strings? Shouldn't that be
> used?
>
> This
Hi,
Please see attached the files containing my output.
OUT-BEFORE.txt: contains output without patch.
OUT-AFTER.txt: contains output with patch.
Thanks,
Nils
On Fri, 9 Aug 2019 at 15:53, Nils Hölscher wrote:
> I observed all Modules loading in the last fdt pass.
> The reason was, nexus bus
I observed all Modules loading in the last fdt pass.
The reason was, nexus bus loading with BUS_PASS_DEFAULT.
---
rtemsbsd/rtems/rtems-kernel-nexus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rtemsbsd/rtems/rtems-kernel-nexus.c
b/rtemsbsd/rtems/rtems-kernel-nexus.c
- Joel Sherrill schrieb:
> Coming in late but there isn't there a helper method to turn object names
> into strings from either 32 bit values or strings? Shouldn't that be used?
This program runs on the host.
>
> On Fri, Aug 9, 2019, 8:17 AM Sebastian Huber <
>
Hi,
I was able to resolve the problem.
The reason that all the devices attached in the last pass and not in the
pass they were assigned, was the nexus bus being loaded as a standard
driver Module.
So the pass level of nexus bus was BUS_PASS_DEFAULT and all devices depend
on nexus bus.
Please see
Coming in late but there isn't there a helper method to turn object names
into strings from either 32 bit values or strings? Shouldn't that be used?
On Fri, Aug 9, 2019, 8:17 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 09/08/2019 15:06, Ravindra Kumar Meena wrote:
> >
I thought I saw a patch pushed yesterday afternoon but a fresh build today
shows the same
breakage.
Jiri .. feel free to push a fix for this and I will test when I get back.
On Thu, Aug 8, 2019 at 2:37 PM Joel Sherrill wrote:
> This is really easy to fix and hopefully Jiri can produce a patch
On 09/08/2019 15:06, Ravindra Kumar Meena wrote:
rtems-main.c cleanup:
https://github.com/rmeena840/rtems-tools/commit/61d5dc45e43f0998ad9305d565926090215a5bdc
Switch_event per CPU added:
https://github.com/rmeena840/rtems-tools/commit/8ffe8bd2adea27772a9ab0e578539dd99fa0174b
Have a look.
rtems-main.c cleanup:
https://github.com/rmeena840/rtems-tools/commit/61d5dc45e43f0998ad9305d565926090215a5bdc
Switch_event per CPU added:
https://github.com/rmeena840/rtems-tools/commit/8ffe8bd2adea27772a9ab0e578539dd99fa0174b
Have a look.
>
--
*Ravindra Kumar Meena*,
B. Tech. Computer
On 08/08/2019 17:53, Joel Sherrill wrote:
Hi
I had forgotten about this but someone reminded me. I don't know how close
to correct it is or what's deficient. The wiki blames Gedare for it.
https://devel.rtems.org/attachment/wiki/Developer/Coding/Conventions/rtems.uncrustify
The last time I
On 08/08/2019 15:33, Joel Sherrill wrote:
Hi
If you are subscribed to the build@ mailing list, then you saw the
flurry of test
results from over night. I built every variant and ran the test suite
with RTEMS
debug on and off. Here are some observations:
+ rv64imafd only has one test pass
+
On Fri, Aug 9, 2019, 5:39 AM Hesham Almatary
wrote:
> Hi Joel,
>
>
> On Thu, 8 Aug 2019 at 14:34, Joel Sherrill wrote:
> >
> > Hi
> >
> > If you are subscribed to the build@ mailing list, then you saw the
> flurry of test
> > results from over night. I built every variant and ran the test suite
Hi Joel,
On Thu, 8 Aug 2019 at 14:34, Joel Sherrill wrote:
>
> Hi
>
> If you are subscribed to the build@ mailing list, then you saw the flurry of
> test
> results from over night. I built every variant and ran the test suite with
> RTEMS
> debug on and off. Here are some observations:
>
> +
I was able to run rv32imac using
qemu-system-riscv32 -no-reboot -nographic -machine virt -m 256M
-kernel hello.exe
On Tue, Aug 6, 2019 at 9:04 PM Vaibhav Gupta
wrote:
> Awesome, thanks!
>
> On Tue, Aug 6, 2019 at 8:50 PM Hesham Almatary <
> hesham.almat...@cl.cam.ac.uk> wrote:
>
>> Hi
---
user/bsps/arm/beagle.rst | 2 +-
user/exe/device-tree.rst | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/user/bsps/arm/beagle.rst b/user/bsps/arm/beagle.rst
index 6c8796b..87c6ecf 100644
--- a/user/bsps/arm/beagle.rst
+++ b/user/bsps/arm/beagle.rst
@@ -40,7 +40,7 @@
>
> > What to do for bound access for api_id? Should I use exit( EXIT_SUCCESS
> > ) for this?
>
> You ignore this item an continue.
>
Okay
https://github.com/rmeena840/rtems-tools/commit/24c7753238ab20fc8c002936657ee0f4c16a6e61
--
*Ravindra Kumar Meena*,
B. Tech. Computer Science and
On 08/08/2019 17:29, Ravindra Kumar Meena wrote:
print_item() cleanup:
https://github.com/rmeena840/rtems-tools/commit/76f1d2898729c9f885abaef1e33a58247c4760dd
What to do for bound access for api_id? Should I use exit( EXIT_SUCCESS
) for this?
You ignore this item an continue.
The
29 matches
Mail list logo
