GSOC 2017 beagleboard bsp project

Hi all: I already rephrase my proposal, remove the part" add the WLAN protocol 802.11", and add the "USB dongle support". If any one has advice or question about my proposal, please email me. Thank you Best Regards Sichen Zhao from Outlook ___

Re: Large number of failures on leon3

On 03/21/2017 10:26 PM, Joel Sherrill wrote: > > > On Tue, Mar 21, 2017 at 5:17 AM, Jiri Gaisler > wrote: > > The culprit seems to be the CASA instruction. The leon3 bsp is > built to always need this instruction, regardless if SMP is > enabled or not. The sis s

Re: Dates in the proposal templates

Hi Gedare, Thank you for clarifying. Regards, Tanu Hari Dixit. On Wed, Mar 22, 2017 at 8:59 PM, Gedare Bloom wrote: > You aren't missing anything. I believe this is already mentioned that > you may need to adapt the template. Thanks. > > On Wed, Mar 22, 2017 at 11:22 AM, Tanu Hari Dixit > wro

Re: Queries regarding Tracing related bugs and GSoC 2017

On Sun, Mar 19, 2017 at 11:23 AM, vivek kukreja wrote: > Hello developers, > > I have worked on CTF tracing last year under GSoC. I was working on my > previous deliverables and i noticed there are some bugs in the current > capture and function tracing examples on qemu for arm/xilinx_zynq_a9, > r

Re: Dates in the proposal templates

You aren't missing anything. I believe this is already mentioned that you may need to adapt the template. Thanks. On Wed, Mar 22, 2017 at 11:22 AM, Tanu Hari Dixit wrote: > Hello all, > > The dates in the "Proposed Schedule" section in the GSoC template > (https://devel.rtems.org/wiki/GSoC) are o

Re: Interested in GSoC 2017 Project: Memory Protection.

On Wed, Mar 22, 2017 at 11:13 AM, Abhimanyu Rawat < h2015...@pilani.bits-pilani.ac.in> wrote: > Indeed, PowerPC code is somewhat developed, would you recommend if there > are some specific features in PowerPC that I should revisit? As this is > little confusing as some work has been done on except

Dates in the proposal templates

Hello all, The dates in the "Proposed Schedule" section in the GSoC template (https://devel.rtems.org/wiki/GSoC) are off by a few days, probably. They are last year's dates, probably. There are three phases this time as opposed to two halves for evaluation. Am I missing something? Can somebody con

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

Hi Gedare Bloom, Hi Ben: Latest news. I just modify the PV's i2c code these days, and now it can read the EEPROM preliminarily by the interrupt not the polling , it is the different way from my previously submitted work(the diff.patch). Without the read eeprom function and other not standardiz

Re: Interested in GSoC 2017 Project: Memory Protection.

Indeed, PowerPC code is somewhat developed, would you recommend if there are some specific features in PowerPC that I should revisit? As this is little confusing as some work has been done on exception handler, page tables, cache already, so what should I target next and what to modify first? Past

Re: Interested in GSoC 2017 Project: Memory Protection.

On Wed, Mar 22, 2017 at 10:07 AM, Abhimanyu Rawat < h2015...@pilani.bits-pilani.ac.in> wrote: > > On Wed, Mar 22, 2017 at 7:17 PM, Gedare Bloom wrote: > >> Please prefer to try to keep general GSoC / RTEMS project discussions on >> the mailing list. Direct e-mail is ok but inefficient in many cas

Re: Interested in GSoC 2017 Project: Memory Protection.

On Wed, Mar 22, 2017 at 10:41 AM, Joel Sherrill wrote: > I may have missed this but Gedare has been working on adding > the mmap/shm services from POSIX. It would be nice for the > dynamic changes interface he mentioned to have an interface > to these calls. I am sure Gedare has thought of how th

Re: Interested in GSoC 2017 Project: Memory Protection.

Hello Dr. Joel, Dr. Bloom obviously have this approach lined up, and that is why he advised me to go work on the low level support for some more bsp's in order to start supporting a firm MMU/MPU interface to applications running. I guess now I need to support more bsp's in order to get to a pragma

Re: Interested in GSoC 2017 Project: Memory Protection.

I may have missed this but Gedare has been working on adding the mmap/shm services from POSIX. It would be nice for the dynamic changes interface he mentioned to have an interface to these calls. I am sure Gedare has thought of how this would work already. :) --joel On Thu, Mar 9, 2017 at 1:14 PM

Re: Interested in GSoC 2017 Project: Memory Protection.

On Wed, Mar 22, 2017 at 7:17 PM, Gedare Bloom wrote: > Please prefer to try to keep general GSoC / RTEMS project discussions on > the mailing list. Direct e-mail is ok but inefficient in many cases and > should only be preferred for communciations of a personal or private matter. > > On Wed, Mar

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

Thanks, I checked it in as: https://git.rtems.org/rtems/commit/?id=1c6926c11f2e5efcb166c668b097d64a0321d66e -- 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-

Re: 答复: 答复: 回复： GSOC 2017 Beagleboard BSP projects

Hi all, Christian and I had a talk about this discussion. The thing is: one of our customers does require WPA support rather soon, therefore (most likely) we will do a first implementation/port within the next 2-3 months. We are not yet sure whether the results are fit enough to be published at on

答复: 答复: 回复： GSOC 2017 Beagleboard BSP projects

Hi Christian Mauderer ,Hi Gedare Bloom: I think i can add the porting wpa to my proposal, and it will be the last part of my GSOC goal. And i guess may left a mouth or less to do the wpa porting, and may can not finish it. but i will try my best. What do you think so? Best Regards Sichen Zha

Re: 答复: 回复： GSOC 2017 Beagleboard BSP projects

Am 21.03.2017 um 18:35 schrieb Gedare Bloom: > On Tue, Mar 21, 2017 at 9:51 AM, 赵 思晨 wrote: >> Hello Christian Mauderer: >> >> I think there are still some misunderstanding: >> >> >> I want to add the hardware independent parts of WLAN (IEEE802.11 standard), >> cause i think the USB driver and WLA