RFC Obseleting ods302 and gen68302 BSPs

2016-01-11 Thread Joel Sherrill
Hi If anyone has objections to removing these BSPs and associated variants, please speak up. Otherwise, I will be shortly filing a ticket for each to be removed prior to 4.12. Thanks. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org

RFC Obsoleting mbx8xx BSP

2016-01-11 Thread Joel Sherrill
Hi If anyone has objections to removing these BSPs and associated variants, please speak up. Otherwise, I will be shortly filing a ticket for each to be removed prior to 4.12. Thanks. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org

Re: Problem with system time in lpc176x bsp

2016-01-11 Thread Marcos Diaz
Hi Sebastian, we did some more testing and found out what's causing the problem. Based on what I posted at https://lists.rtems.org/pipermail/devel/2015-December/013235.html, the problem arises when the ticker interrupt occurs while a task is executing one of the instructions that make up the follo

Re: Problem with system time in lpc176x bsp

2016-01-11 Thread Joel Sherrill
At this point, a ticket is needed for anything applied to 4.11 that is not release mechanics related. --joel On Mon, Jan 11, 2016 at 11:47 AM, Marcos Diaz < marcos.d...@tallertechnologies.com> wrote: > Hi Sebastian, > > we did some more testing and found out what's causing the problem. Based > o

Re: Problem with system time in lpc176x bsp

2016-01-11 Thread Marcos Díaz
I will issue a ticket. But I noticed that in my patch I include changes to common code that Sebastian suggested, and this will break any other BSP that uses rtems timecounter simple downcounter or upcounter, since these function's signatures changed. Should we update all BSPs? Or make changes more

Re: Problem with system time in lpc176x bsp

2016-01-11 Thread Joel Sherrill
On Mon, Jan 11, 2016 at 12:28 PM, Marcos Díaz < marcos.d...@tallertechnologies.com> wrote: > I will issue a ticket. But I noticed that in my patch I include changes to > common code that Sebastian suggested, and this will break any other BSP > that uses rtems timecounter simple downcounter or upco

Re: Problem with system time in lpc176x bsp

2016-01-11 Thread Marcos Díaz
I made a fast search: These BSPs use *rtems_timecounter_simple_downcounter*: arm/shared/armv7m m68k/mcf52235 m68k/mcf5225x m68k/mcf5329 m68k/uC5282 powerpc/mpc55xxevb sparc/erc32 sparc/leon2 sparc/leon3 sparc/shared These use *rtems_timecounter_simple_upcounter*: powerpc/mpc55xxevb arm/lpc22xx We

Re: Problem with system time in lpc176x bsp

2016-01-11 Thread Sebastian Huber
Hello, I already created a ticket which blocks the 4.11 release for this bug: https://devel.rtems.org/ticket/2502 I sent a new version of the patch to one of your previous threads some days ago: https://lists.rtems.org/pipermail/devel/2016-January/013289.html There is still a bug in it, since

Re: Problem with system time in lpc176x bsp

2016-01-11 Thread Marcos Díaz
Well, we could still use the patch you sent with the protection in is pending, but I think this will break the BSPs I mentioned, since you changed timecounter functions signatures. Am I right? On Mon, Jan 11, 2016 at 4:18 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, >

Re: Problem with system time in lpc176x bsp

2016-01-11 Thread Joel Sherrill
On Mon, Jan 11, 2016 at 1:25 PM, Marcos Díaz < marcos.d...@tallertechnologies.com> wrote: > Well, we could still use the patch you sent with the protection in is > pending, but I think this will break the BSPs I mentioned, since you > changed timecounter functions signatures. Am I right? > > Let's

Re: Rtems-test cortex-m3

2016-01-11 Thread Aurelio Remonda
On Mon, Jan 11, 2016 at 3:47 AM, Sebastian Huber wrote: > > > On 08/01/16 17:41, Aurelio Remonda wrote: >> >> Thanks for your answers! I am running the tests for >> realview_pbx_a9_qemu for the moment. >> I have a few questions if you don't mind >> >> With the git repository version of rtems >> ./