Re: Requirement Document generator tool

On 30/01/2020 23:13, Chris Johns wrote: > On 30/1/20 8:35 pm, Christian Mauderer wrote: >> On 29/01/2020 23:48, Chris Johns wrote: >>> On 29/1/20 7:40 pm, Christian Mauderer wrote: On 28/01/2020 23:15, Chris Johns wrote: > On 28/1/20 10:22 pm, Christian Mauderer wrote: >> I'm quite ind

Re: "atsamv" BSP legacy network driver status

On 30/01/2020 22:12, dufa...@hda.com wrote: > > >> On Jan 30, 2020, at 01:24 , Christian Mauderer >> wrote: >> >> The SDRAM initialization is done in bsp_start_hook_0. Most >> initialization is done in bsp_start_hook_1. You should be able to put >> the following into SDRAM without problems: >>

Re: RTEMS FS locking

On 31/1/20 12:48 pm, Charles Manning wrote: > On Fri, Jan 31, 2020 at 12:09 PM Chris Johns wrote: >> >> On 31/1/20 9:51 am, Charles Manning wrote: >>> I'm the Yaffs Guy and have been asked to do some work refreshing the >>> Yaffs core code that is in Sebastian's rtems-yaffs git as well as >>> inte

Re: RTEMS FS locking

On Fri, Jan 31, 2020 at 12:09 PM Chris Johns wrote: > > On 31/1/20 9:51 am, Charles Manning wrote: > > I'm the Yaffs Guy and have been asked to do some work refreshing the > > Yaffs core code that is in Sebastian's rtems-yaffs git as well as > > integrate it into the Yaffs tests. > > Excellent and

Re: RTEMS FS locking

On 31/1/20 9:51 am, Charles Manning wrote: > I'm the Yaffs Guy and have been asked to do some work refreshing the > Yaffs core code that is in Sebastian's rtems-yaffs git as well as > integrate it into the Yaffs tests. Excellent and welcome. > After a few false starts I now have an understanding

RTEMS FS locking

Hi All I'm the Yaffs Guy and have been asked to do some work refreshing the Yaffs core code that is in Sebastian's rtems-yaffs git as well as integrate it into the Yaffs tests. After a few false starts I now have an understanding of how to build a simulation test environment based on the quicksta

Re: Errors in .tcfg Do Not Stop the Build

On 31/1/20 8:34 am, Joel Sherrill wrote: > I made a mistake in a .tcfg file (forgot to write exclude: and just listed > the test name). There was a message in the build log where the error > was reported but the build itself continued and didn't produce any  > executables. The ultimate return statu

Re: Requirement Document generator tool

On 30/1/20 8:35 pm, Christian Mauderer wrote: > On 29/01/2020 23:48, Chris Johns wrote: >> On 29/1/20 7:40 pm, Christian Mauderer wrote: >>> On 28/01/2020 23:15, Chris Johns wrote: On 28/1/20 10:22 pm, Christian Mauderer wrote: > I'm quite indifferent which style we use But you a

Errors in .tcfg Do Not Stop the Build

Hi I made a mistake in a .tcfg file (forgot to write exclude: and just listed the test name). There was a message in the build log where the error was reported but the build itself continued and didn't produce any executables. The ultimate return status was 0 so we thought it passed. Is this just

Re: "atsamv" BSP legacy network driver status

> On Jan 30, 2020, at 01:24 , Christian Mauderer > wrote: > > The SDRAM initialization is done in bsp_start_hook_0. Most > initialization is done in bsp_start_hook_1. You should be able to put > the following into SDRAM without problems: > > - REGION_WORK > - REGION_BSS > - REGION_DATA > - R

Re: [PATCH 0/2] Add new Xen BSP target using GICv3 driver

On Thu, Jan 30, 2020, 9:10 AM Jeff Kubascik wrote: > On 1/28/2020 12:02 PM, Joel Sherrill wrote: > > > > I have merged all of Jeff's patches. Please check that they work as > merged > > and do not introduce warnings. > > > > Thanks. > > > > --joel > > > > On Thu, Jan 23, 2020 at 10:04 AM Jeff Ku

Re: [PATCH 0/2] Add new Xen BSP target using GICv3 driver

On 1/28/2020 12:02 PM, Joel Sherrill wrote: > > I have merged all of Jeff's patches.  Please check that they work as merged > and do not introduce warnings. > > Thanks. > > --joel > > On Thu, Jan 23, 2020 at 10:04 AM Jeff Kubascik > wrote: > > This pa

Re: Requirement Document generator tool

On 29/01/2020 23:48, Chris Johns wrote: > On 29/1/20 7:40 pm, Christian Mauderer wrote: >> On 28/01/2020 23:15, Chris Johns wrote: >>> On 28/1/20 10:22 pm, Christian Mauderer wrote: I'm quite indifferent which style we use >>> >>> But you are arguing a position, such as ... >>> but do you