答复: [PATCH] modify punitvara's works on BBB i2c, and now can read the eeprom info.

Hi all: I think it can use in i2c devices, but i don't test it. and the read_eeprom is using reading the eeprom. and i will modify it in the future, conform my code to the RTEMS code specification. Best regrads Sichen Zhao 发自 Outlook

Re: [PATCH] modify punitvara's works on BBB i2c, and now can read theeeprom info.

I think it can use in i2c devices, but i don't test it. and the read_eeprom is using reading the eeprom. and i will modify it in the future, conform to the RTEMS code specification. -- Original -- From: "beng";; Date: Tue, Mar 21,

Re: [PATCH] modify punitvara's works on BBB i2c, and now can read the eeprom info.

Dear all, SZ, great initiative. Gedare and Sebastian have commented. For my part, can I just check - the implementation is supposed to be generic to i2c devices, correct? If so, can you explain what read_eeprom is for? Is it just as demo? Is the code generic otherwise? Cheers, Ben On

Current 4.11.2 tickets.

Hi, Can all developers please take a look at the 4.11.2 roadmap and the in-progress and new tickets and update, fix or change as appropriate. https://devel.rtems.org/milestone/4.11.2 Thanks Chris ___ devel mailing list devel@rtems.org

Re: RTEMS 4.11.2 milestone date

On 17/03/2017 12:34, Chris Johns wrote: On 17/03/2017 10:58, Gedare Bloom wrote: On Thu, Mar 16, 2017 at 7:52 PM, Joel Sherrill wrote: You couldn't build powerpc gdb because of the error symbol. There was something Ah yes something in the simulator is referencing a C symbol

Re: timeouts and failure

On 20/03/2017 17:20, Sebastian Huber wrote: On 18/03/17 21:52, Joel Sherrill wrote: FWIW here are my results for sparc/erc32: Passed: 548 Failed: 1 Timeouts: 5 Invalid:0 - Total:554 Failures: spcontext01.exe Yes, this is expected. Timeouts: fileio.exe

Re: GSOC 2017 Beagleboard BSP projects

On Sun, Mar 19, 2017 at 4:38 PM, Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > - Ursprüngliche Mail - > > Von: "赵 思晨" > > An: "RTEMS" > > Gesendet: Sonntag, 19. März 2017 15:29:03 > > Betreff: GSOC 2017 Beagleboard BSP

Re: [PATCH 1/5] Adding modified FREEBSD headers to sync RTEMS termios with FREEBSD

Agreed a BSP or user space code should not use the same name as anything that is included in POSIX. :) How did my build sweep miss this? --joel On Mon, Mar 20, 2017 at 1:01 PM, Kirspel, Kevin wrote: > Actually the best thing to do is change the structure member name

Fwd: GSoC 2017 Student application period is now open!

Hi Students can now begin to apply. We are looking forward to some high quality and interesting applications. :) --joel -- Forwarded message -- From: 'Stephanie' via Google Summer of Code Discuss < google-summer-of-code-disc...@googlegroups.com> Date: Mon, Mar 20, 2017 at 1:57

RE: [PATCH 1/5] Adding modified FREEBSD headers to sync RTEMS termios with FREEBSD

Actually the best thing to do is change the structure member name and fix up any access to that member. Kevin Kirspel Electrical Engineer - Sr. Staff Idexx Roswell 235 Hembree Park Drive Roswell GA 30076 Tel: (770)-510- ext. 81642 Direct: (770)-688-1642 Fax: (770)-510-4445 From: devel

RE: [PATCH 1/5] Adding modified FREEBSD headers to sync RTEMS termios with FREEBSD

I tracked the arm failure down to a header file (s3c2410.h) that contains a structure that has a member with the same name as a termios #define. Re-ordering the include file declarations in each affected C file will fix the problem (I’m not sure that’s the best solution but it will do for now).

Re: [PATCH 1/5] Adding modified FREEBSD headers to sync RTEMS termios with FREEBSD

I just built all BSPs and didn't see any failures. Sebastian.. what was going on with the build you saw fail? --joel On Mon, Mar 20, 2017 at 9:19 AM, Joel Sherrill wrote: > > > On Tue, Mar 14, 2017 at 8:54 AM, Kirspel, Kevin > wrote: > >> I tested it

Re: [PATCH 1/5] Adding modified FREEBSD headers to sync RTEMS termios with FREEBSD

On Tue, Mar 14, 2017 at 8:54 AM, Kirspel, Kevin wrote: > I tested it against xilinx_zynq_a9_qemu. I'm not sure it exists, but if > there is a way to compile the patch against every (or most) BSP then we > could ensure no BSP is broken. > > There are scripts in

Re: Large number of failures on leon3

This seems to be a problem with the leon3 bsp, most of the failing tests work fine on erc32 and leon2. This is regardless of which simulator is used. Maybe the SMP additions to leon3 breaks something when SMP is disabled ...? It also goes back in time - I am using git master from early December

Re: timeouts and failure

On 18/03/17 21:52, Joel Sherrill wrote: FWIW here are my results for sparc/erc32: Passed: 548 Failed: 1 Timeouts: 5 Invalid:0 - Total:554 Failures: spcontext01.exe Yes, this is expected. Timeouts: fileio.exe top.exe termios.exe capture.exe monitor.exe