From: Chris Johns
Closes #3760
---
bsps/arm/shared/cp15/arm-cp15-set-ttb-entries.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/bsps/arm/shared/cp15/arm-cp15-set-ttb-entries.c
b/bsps/arm/shared/cp15/arm-cp15-set-ttb-entries.c
index
These patches add libdebugger support for the beagleboneblack.
Special JTAG based BBB BSP probe and configure code is needed to enable
the debug hardware in the ARM. The code requires a small hardware mod
to work as the BBB hardware by default does not enable software
debugging.
The libdebugger
From: Chris Johns
- Port the jbang code from C++ to C to enable DBGEN.
- Hook the libdebugger ARM backend support to return the base address
of the debug register set.
---
bsps/arm/beagle/start/bspdebug.c| 734
bsps/arm/beagle/start/bspdebug.h| 38 ++
From: Chris Johns
- Fix destorying the target and thread parts.
- Fix the ARM backend to support Cortex-A8 and ARM mode code.
- Use the DBGDSCR interrupt mask when single stepping.
- Use the DBGDSCR method of entry to debug mode to filter the
execptions.
- Add support for BSPs to control the
On 26/7/19 9:41 pm, Christian Mauderer wrote:
> I hadn't had a look at most patches yet and most likely that will need a
> bit of time. It's a lot of stuff. Most likely the bigger patches won't
> reach the mailing list so maybe adding a link to a branch on your github
> repo would be good.
There
On Fri, Jul 26, 2019 at 1:48 PM Peter Dufault wrote:
> The follwing commit below in libbsd added “verbose” flags to both
> rpcUdpInit() and nfsInit(). Code using libbsd needs a change to compile.
> I don’t like adding a compile time check.
>
> Shall I change the RTEMS ones to match even if the
The follwing commit below in libbsd added “verbose” flags to both rpcUdpInit()
and nfsInit(). Code using libbsd needs a change to compile.
I don’t like adding a compile time check.
Shall I change the RTEMS ones to match even if the flag doesn’t do anything?
[dufault@fubar rtems-libbsd]$ git
- Am 26. Jul 2019 um 14:56 schrieb Ravindra Kumar Meena rmeena...@gmail.com:
>>
>> Ok, very good. This look all right. It is amazing how much information
>> Trace Compass can display with only sched_switch events.
>>
> Great!! We have something working very useful. :) :)
>
>>
>> Please
On Fri, Jul 26, 2019 at 6:42 PM Vijay Kumar Banerjee <
vijaykumar9...@gmail.com> wrote:
>
>
>
> On Fri, Jul 26, 2019 at 5:11 PM Christian Mauderer <
> christian.maude...@embedded-brains.de> wrote:
>
>> On 26/07/2019 13:22, Vijay Kumar Banerjee wrote:
>> > Hello everyone!
>> >
>> > I'm excited to
On Fri, Jul 26, 2019 at 5:11 PM Christian Mauderer <
christian.maude...@embedded-brains.de> wrote:
> On 26/07/2019 13:22, Vijay Kumar Banerjee wrote:
> > Hello everyone!
> >
> > I'm excited to post the following patchset. With this patchset
> > I have the framebuffer working in BBB and have
>
> Ok, very good. This look all right. It is amazing how much information
> Trace Compass can display with only sched_switch events.
>
Great!! We have something working very useful. :) :)
>
> Please figure out how the state member values are defined. I think this
> is important to improve the
On 26/07/2019 13:22, Vijay Kumar Banerjee wrote:
> Hello everyone!
>
> I'm excited to post the following patchset. With this patchset
> I have the framebuffer working in BBB and have tested it with a
> BBB revC with HDMI connected Screen.
>
> This patchset uses mmap and hence it's necessary to
On Fri, Jul 26, 2019 at 4:53 PM Vijay Kumar Banerjee <
vijaykumar9...@gmail.com> wrote:
> Hello everyone!
>
> I'm excited to post the following patchset. With this patchset
> I have the framebuffer working in BBB and have tested it with a
> BBB revC with HDMI connected Screen.
>
> This patchset
---
.../sys/arm/ti/am335x/am335x_scm_padconf.c| 305
.../sys/arm/ti/am335x/am335x_scm_padconf.h| 47 ++
freebsd/sys/arm/ti/omap4/omap4_scm_padconf.h | 83
freebsd/sys/arm/ti/ti_pinmux.c| 463 ++
freebsd/sys/arm/ti/ti_pinmux.h
---
Makefile.todo | 13 ++
buildset/default.ini | 1 +
libbsd.py | 33 +++
rtemsbsd/include/bsp/nexus-devices.h | 1 +
.../machine/rtems-bsd-kernel-namespace.h | 9 +
---
freebsd/sys/dev/fb/fbd.c | 3 ++
libbsd.py | 4 +++
rtemsbsd/include/bsp/nexus-devices.h | 3 ++
.../machine/rtems-bsd-kernel-namespace.h | 35 +++
rtemsbsd/include/rtems/bsd/local/opt_fb.h | 0
5
---
Makefile.todo | 13 ++
libbsd.py | 12 +
rtemsbsd/include/bsp/nexus-devices.h | 2 +
.../machine/rtems-bsd-kernel-namespace.h | 2 +
rtemsbsd/include/rtems/bsd/local/fb_if.h | 45
---
Makefile.todo | 27 ++
buildset/default.ini | 1 +
libbsd.py | 45 +
rtemsbsd/include/bsp/nexus-devices.h | 1 +
.../machine/rtems-bsd-kernel-namespace.h | 65 +
---
freebsd/sys/dev/vt/colors/vt_termcolors.c | 181 ++
freebsd/sys/dev/vt/hw/fb/vt_fb.c | 528
freebsd/sys/dev/vt/vt_core.c | 2933 +
3 files changed, 3642 insertions(+)
create mode 100644 freebsd/sys/dev/vt/colors/vt_termcolors.c
create mode
---
freebsd/sys/dev/fb/fb.c | 762 ++
freebsd/sys/dev/fb/fbd.c | 372 +++
freebsd/sys/dev/vt/colors/vt_termcolors.h | 63 ++
freebsd/sys/dev/vt/hw/fb/vt_fb.h | 54 ++
4 files changed, 1251 insertions(+)
create mode 100644
Hello everyone!
I'm excited to post the following patchset. With this patchset
I have the framebuffer working in BBB and have tested it with a
BBB revC with HDMI connected Screen.
This patchset uses mmap and hence it's necessary to apply the
patche ON TOP OF mmap patch to avoid merge conflict.
Hello,
Joel asked me to document the normal patch review process. Should this
be in a "Contributing" chapter in the user manual or should this stuff
be in the RTEMS Software Engineering manual?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone
I have tested hello.exe on RPi2, BBB, and Zedboard and all are OK.
Please push.
I will run the full test suite after.
Thank you for the fix.
Chris
On 26/7/19 4:17 pm, Sebastian Huber wrote:
> There are no known ARMv7-M chips with a dual lockstep mode.
>
> Update #3773.
> ---
>
On 26/7/19 4:23 pm, Sebastian Huber wrote:
> On 26/07/2019 07:41, Chris Johns wrote:
>> On 26/7/19 3:07 pm, Sebastian Huber wrote:
>>> On 26/07/2019 07:06, Sebastian Huber wrote:
Hello Chris,
I am not sure, if using r8 is the right thing to do since r8..r14 are
banked
in
On 26/07/2019 07:41, Chris Johns wrote:
On 26/7/19 3:07 pm, Sebastian Huber wrote:
On 26/07/2019 07:06, Sebastian Huber wrote:
Hello Chris,
I am not sure, if using r8 is the right thing to do since r8..r14 are banked
in FIQ mode. I think the bsp_start_arm_drop_hyp_mode needs to be changed to
There are no known ARMv7-M chips with a dual lockstep mode.
Update #3773.
---
bsps/arm/shared/start/start.S | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/bsps/arm/shared/start/start.S b/bsps/arm/shared/start/start.S
index 80b7d44dbe..a7fd7eda62 100644
---
This makes it easier to review changes in start.S.
Update #3773.
---
bsps/arm/shared/start/bsp-start-init-registers.S | 105 ---
bsps/arm/shared/start/start.S| 59 -
c/src/lib/libbsp/arm/tms570/Makefile.am | 1 -
3 files changed, 55
This fixes the corruption of r3 by the call to
bsp_start_arm_drop_hyp_mode().
Moving the code makes it easier to review changes in start.S.
Close #3773.
---
bsps/arm/shared/start/bsp-start-in-hyp-support.S | 76
bsps/arm/shared/start/start.S| 42
28 matches
Mail list logo