[PATCH] fdt pinctrl: Add a hack to initialize only TDA pins

--- freebsd/sys/dev/fdt/fdt_pinctrl.c | 5 + 1 file changed, 5 insertions(+) diff --git a/freebsd/sys/dev/fdt/fdt_pinctrl.c b/freebsd/sys/dev/fdt/fdt_pinctrl.c index c2e0c612..89de9281 100644 --- a/freebsd/sys/dev/fdt/fdt_pinctrl.c +++ b/freebsd/sys/dev/fdt/fdt_pinctrl.c @@ -131,8 +131,13

Re: Which Python version for new tool code?

On Fri, Aug 2, 2019 at 12:43 PM Peter Dufault wrote: > > > > On Aug 2, 2019, at 11:28 , Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > > > >> As best I can tell, no official repository includes Python 3. There are > >> un-official addon repos > >> with Python 3. > >> > >> The

[PATCH] Add a hack to initialize TDA pins

Hello all, This following patch uses a device tree overlay to enable the initialization of only the required pins, to avoid conflict with other drivers in the BSP. However, this might not be the best solution and also it increases the dependency on the device tree overlay. I have checked this

[PATCH v2 7/8] am335x display drivers: Import from FreeBSD

--- freebsd/sys/arm/ti/am335x/am335x_ecap.c | 202 freebsd/sys/arm/ti/am335x/am335x_lcd.c | 1085 ++ freebsd/sys/arm/ti/am335x/am335x_lcd.h | 60 ++ freebsd/sys/arm/ti/am335x/am335x_pwm.h | 35 + freebsd/sys/arm/ti/am335x/am335x_pwmss.c | 165

[PATCH v2 6/8] fbd: Port to RTEMS

--- Makefile.todo | 13 ++ freebsd/sys/dev/fb/fbd.c | 4 ++ libbsd.py | 8 rtemsbsd/include/bsp/nexus-devices.h | 3 ++ .../machine/rtems-bsd-kernel-namespace.h | 21 -

[PATCH v2 2/8] Pinmux: Port to RTEMS

--- Makefile.todo | 13 ++ buildset/default.ini | 1 + libbsd.py | 33 +++ rtemsbsd/include/bsp/nexus-devices.h | 1 + .../machine/rtems-bsd-kernel-namespace.h | 9 +

[PATCH v2 4/8] TDA19988: Port to RTEMS

--- Makefile.todo | 26 ++ buildset/default.ini | 1 + libbsd.py | 41 + rtemsbsd/include/bsp/nexus-devices.h | 1 + .../machine/rtems-bsd-kernel-namespace.h | 65 +

[PATCH v2 8/8] am335x display drivers: Port to RTEMS

--- libbsd.py | 8 rtemsbsd/include/bsp/nexus-devices.h | 2 ++ rtemsbsd/include/machine/rtems-bsd-kernel-namespace.h | 2 ++ 3 files changed, 12 insertions(+) diff --git a/libbsd.py b/libbsd.py index f94f7b3d..96cc4e3b 100644

[PATCH v2 3/8] TDA19988: Import from FreeBSD

--- freebsd/sys/arm/ti/am335x/tda19988.c | 812 ++ freebsd/sys/dev/extres/clk/clk.h | 146 freebsd/sys/dev/videomode/edid.c | 649 + freebsd/sys/dev/videomode/ediddevs.h | 91 +++ freebsd/sys/dev/videomode/ediddevs_data.h | 107

[PATCH v2 5/8] fbd: Import from FreeBSD

--- freebsd/sys/dev/fb/fb.c | 762 ++ freebsd/sys/dev/fb/fbd.c | 372 +++ freebsd/sys/dev/fb/fbreg.h| 345 ++ freebsd/sys/dev/vt/colors/vt_termcolors.h | 63 ++ freebsd/sys/dev/vt/hw/fb/vt_fb.h | 54

[PATCH] bsp/beagle: Add nocache section

--- bsps/arm/beagle/start/bspstart.c | 5 + bsps/arm/beagle/start/linkcmds.beagle | 7 --- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/bsps/arm/beagle/start/bspstart.c b/bsps/arm/beagle/start/bspstart.c index 47db5cc529..224f9ecf3b 100644 ---

Re: GSoC Project | Basic Support for Trace Compass

- Am 2. Aug 2019 um 19:14 schrieb Ravindra Kumar Meena rmeena...@gmail.com: >> >> It seems that there are some special cases for the swapper which has a >> tid of 0. Could you please adjust the code so that idle threads get a >> tid of 0. >> > > Done. The graph now has more detail now. I

Re: Which Python version for new tool code?

> On Aug 2, 2019, at 11:28 , Sebastian Huber > wrote: > >> As best I can tell, no official repository includes Python 3. There are >> un-official addon repos >> with Python 3. >> >> The users who are using RHEL 7 are unlikely to allow those repos to be used. > > Puh, this is a bit

[PATCH] Update Newlib to pick up ndbm addition (newlib=6661a67)

--- rtems/config/5/rtems-default.bset | 2 +- rtems/config/5/rtems-epiphany.bset | 2 +- rtems/config/5/rtems-or1k.bset | 2 +- rtems/config/5/rtems-riscv.bset| 2 +- rtems/config/5/rtems-x86_64.bset |

Re: GSoC Project | Basic Support for Trace Compass

> > > I did following thing in print_item() but nothing is shown in the console > > output: > > > > if(item->event == RTEMS_RECORD_THREAD_ID){ > >printf("this thing is present\n"); > > } > > > I checked in a fix for this problem. > Thanks a lot. It worked. -- *Ravindra Kumar Meena*, B.

Re: GSoC Project | Basic Support for Trace Compass

- Am 2. Aug 2019 um 18:09 schrieb Ravindra Kumar Meena rmeena...@gmail.com: >> >> I just checked out the original version with some minor edits. This output >> should be enough to figure out how it works. >> >> You have to extend the switch case in print_item() to check for >>

Re: RISCV BSP

Thanks a lot. Then I will be working with "rv32imac" and "rv64imac" Vaibhav Gupta On Fri, Aug 2, 2019 at 1:33 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 02/08/2019 09:50, Vaibhav Gupta wrote: > > Hello, > > I was about to test the testsuite code, need to confirm > > on

Re: GSoC Project | Basic Support for Trace Compass

> > I just checked out the original version with some minor edits. This output > should be enough to figure out how it works. > > You have to extend the switch case in print_item() to check for > RTEMS_RECORD_THREAD_ID and RTEMS_RECORD_THREAD_NAME. The thread name events > contain the bytes in the

Re: [PATCH v4] user/exe: Add Device Tree section

Please make two small changes noted below, and this can be pushed (if the PDF build looks right). On Fri, Aug 2, 2019 at 4:44 AM Vijay Kumar Banerjee wrote: > > --- > user/bsps/arm/beagle.rst | 21 + > user/exe/device-tree.rst | 92 >

Re: Add UUID to requirements (and other specification items)?

On Fri, Aug 2, 2019 at 5:17 AM Sebastian Huber wrote: > > Hello, > > do you think an UUID > (https://en.wikipedia.org/wiki/Universally_unique_identifier) is useful > to have for all requirements (and other specification items)? The > proposal for identifiers already ensures that all identifiers

Re: GSoC Project | Basic Support for Trace Compass

- Am 2. Aug 2019 um 17:25 schrieb Ravindra Kumar Meena rmeena...@gmail.com: >> >> The task name information is already in qoriq_e6500_64.bin: >> >> *:0:VERSION:5 >> *:0:PROCESSOR_MAXIMUM:17 >> *:0:PER_CPU_COUNT:1 >> *:0:FREQUENCY:59682f00 >> *:0:THREAD_ID:9010001 >>

Re: Which Python version for new tool code?

- Am 2. Aug 2019 um 15:52 schrieb joel j...@rtems.org: > On Fri, Aug 2, 2019 at 8:21 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> On 02/08/2019 15:14, Joel Sherrill wrote: >> > >> > On Fri, Aug 2, 2019 at 3:10 AM Sebastian Huber >> > > >

Re: GSoC Project | Basic Support for Trace Compass

> > The task name information is already in qoriq_e6500_64.bin: > > *:0:VERSION:5 > *:0:PROCESSOR_MAXIMUM:17 > *:0:PER_CPU_COUNT:1 > *:0:FREQUENCY:59682f00 > *:0:THREAD_ID:9010001 > *:0:THREAD_NAME:49444c45 > *:0:THREAD_ID:9010002 > *:0:THREAD_NAME:49444c45 > *:0:THREAD_ID:9010003 >

Re: Which Python version for new tool code?

On Fri, Aug 2, 2019 at 8:21 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 02/08/2019 15:14, Joel Sherrill wrote: > > > > On Fri, Aug 2, 2019 at 3:10 AM Sebastian Huber > > > > wrote: > > > > Hello, > > > > the EOL of

Re: Which Python version for new tool code?

On 02/08/2019 15:14, Joel Sherrill wrote: On Fri, Aug 2, 2019 at 3:10 AM Sebastian Huber > wrote: Hello, the EOL of Python 2.7 is soon, so it will be Python 3 for sure: https://pythonclock.org/ The EOL of Python 3.4 was March 18,

Re: Which Python version for new tool code?

On Fri, Aug 2, 2019 at 3:10 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > the EOL of Python 2.7 is soon, so it will be Python 3 for sure: > > https://pythonclock.org/ > > The EOL of Python 3.4 was March 18, 2019: > >

RTEMS Source Builder failed for MX Linux

Hi Chris, Sorry for late reply as I am busy here for admission in an university. So I tried the solution suggested by you and it somewhere got build failed. This time it didn't asked for sudo privilege and went on building but somewhere build got failed. I checked the error report but there is no

Add UUID to requirements (and other specification items)?

Hello, do you think an UUID (https://en.wikipedia.org/wiki/Universally_unique_identifier) is useful to have for all requirements (and other specification items)? The proposal for identifiers already ensures that all identifiers have a proper namespace (e.g. RTEMS), so there is no strong need

Re: GSoC Project | Basic Support for Trace Compass

On 02/08/2019 10:45, Sebastian Huber wrote: On 02/08/2019 10:38, Sebastian Huber wrote: On 31/07/2019 08:30, Ravindra Kumar Meena wrote: > The bit field is documented in the manual. I would simplify this to: > > cctx->switch_out_int[ item->cpu ].prev_state = ( ( ( item->data    

[PATCH v4] user/exe: Add Device Tree section

--- user/bsps/arm/beagle.rst | 21 + user/exe/device-tree.rst | 92 user/exe/index.rst | 1 + 3 files changed, 95 insertions(+), 19 deletions(-) create mode 100644 user/exe/device-tree.rst diff --git a/user/bsps/arm/beagle.rst

Re: GSoC Project | Basic Support for Trace Compass

On 02/08/2019 10:38, Sebastian Huber wrote: On 31/07/2019 08:30, Ravindra Kumar Meena wrote: > The bit field is documented in the manual. I would simplify this to: > > cctx->switch_out_int[ item->cpu ].prev_state = ( ( ( item->data >> 24 ) > & 0x7 ) == 1 ) ? TASK_IDLE

Which Python version for new tool code?

Hello, the EOL of Python 2.7 is soon, so it will be Python 3 for sure: https://pythonclock.org/ The EOL of Python 3.4 was March 18, 2019: https://www.python.org/downloads/release/python-3410/ Is it all right to start with Python 3.5? -- Sebastian Huber, embedded brains GmbH Address :

Re: RISCV BSP

On 02/08/2019 09:50, Vaibhav Gupta wrote: Hello, I was about to test the testsuite code, need to confirm on which RISCV BSP we are going to work? For example, for ARM I was asked for xilinx-zynq So is there any specific one for riscv too, or should I build any of it? While you work on this,

RISCV BSP

Hello, I was about to test the testsuite code, need to confirm on which RISCV BSP we are going to work? For example, for ARM I was asked for xilinx-zynq So is there any specific one for riscv too, or should I build any of it? Vaibhav Gupta ___ devel

Re: GSoC Project | Basic Support for Trace Compass

On 02/08/2019 08:29, Ravindra Kumar Meena wrote: Why do you implement a hash map on your own? I would have renamed the record-main.c to record-main.cc and use std::map for example or something from boost. I tried this but this generates a lot of warnings from the same file and

Re: GSoC Project | Basic Support for Trace Compass

> > Why do you implement a hash map on your own? I would have renamed the > record-main.c to record-main.cc and use std::map for example or > something from boost. > I tried this but this generates a lot of warnings from the same file and other files also. Converting from C to another language

Re: Addition of Rule Checkers

On 02/08/2019 03:35, Chris Johns wrote: On 30/7/19 4:32 pm, Sebastian Huber wrote: On 30/07/2019 01:01, Joel Sherrill wrote: On Mon, Jul 29, 2019 at 5:23 PM Gedare Bloom mailto:ged...@rtems.org>> wrote:     On Wed, Jul 24, 2019 at 7:16 AM Joel Sherrill mailto:j...@rtems.org>> wrote: