Re: Tiering, Expected Failures, and BSPs which Run on Multiple Sims/HW

On Fri, Oct 25, 2019 at 9:18 AM Thomas Doerfler < thomas.doerf...@embedded-brains.de> wrote: > Hi, > > > Am 25.10.19 um 16:08 schrieb Joel Sherrill: > > > > One question we need to discuss is what about BSPs which can run on > > multiple simulators and possibly real hardware. For example, the

Re: Attributes in build specification items

On Fri, Oct 25, 2019 at 2:35 AM Sebastian Huber wrote: > > Hello, > > for the new build system the specification what to build is contained in > so called build specification items. The items are files in YAML format > and are maintained by Doorstop and a text editor. For example a build >

Re: Tiering, Expected Failures, and BSPs which Run on Multiple Sims/HW

Hi, Am 25.10.19 um 16:08 schrieb Joel Sherrill: > > One question we need to discuss is what about BSPs which can run on > multiple simulators and possibly real hardware. For example, the sparc > BSPs can run on real hardware, sis, qemu, and tsim. How do we > distinguish the same BSP's expected

Tiering, Expected Failures, and BSPs which Run on Multiple Sims/HW

Hi Last week, there was a rare meeting of a handful of core developers. One issue was implementing the tiers of BSPs we have discussed for a couple of years now. There is general agreement on the basics of the tiering. Tier 1 has test results on hardware. Tier 2 on simulator only. Tier 3 is known

RSB Qemu Leon3 patches error

Hi I am not sure what's up with the Leon patches but I am getting a checksum error and wanted to see if Jiri or someone else knowledgeable could investigate and fix. warning: checksum error: 0001-LEON3-Add-emulation-of-AMBA-plug-play.patch warning: removing:

Re: [PATCH v2] [rsb] Update Spike build

Thanks for updating this. When building on a very clean machine, dtc needs to be referenced and in the PATH. hecking for dtc... no configure: error: device-tree-compiler not found Is this working for you when dtc is not installed before building spike? On Thu, Oct 24, 2019 at 4:39 PM Chris

Re: RTEMS Google Code-In 2019

It's not that we don't like GCI or would like to mentor. Everyone who has been an org admin has conflicts with most of the schedule this year. That's also the backbone of our mentor set. We have historically alternated years. --joel On Fri, Oct 25, 2019 at 2:02 AM Ravindra Kumar Meena wrote:

Detect change in configuration file and re-configure in waf?

Hello, the new build system uses a set of *.ini files to configure the build. They are stored in the build lock file: build/.lock-waf_linux2_build:options = {..., 'rtems_options': 'bsps.ini', ...} I would like to issue a re-configuration if one of the *.ini files changes. It would be nice

Attributes in build specification items

Hello, for the new build system the specification what to build is contained in so called build specification items. The items are files in YAML format and are maintained by Doorstop and a text editor. For example a build specification item for an integer configuration option could look like:

Re: [PATCH v2 1/5] riscv: Generate linkcmds.base from the shared linkcmds.base.in

The patch set is fine to commit. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist

Re: RTEMS Google Code-In 2019

Hello Himanshu, I am interested in mentoring for Google Code-in 2019. Looking forward to be a part of it. Thanks On Fri, 25 Oct, 2019, 1:32 am Vaibhav Gupta, wrote: > Hello everyone! > > I am interested in mentoring for Google Code-In 2019. > > -- Vaibhav Gupta > > On Fri, Oct 25, 2019, 1:28