Re: [PATCH 5/8] generic_or1k BSP clock driver correction

2016-03-02 Thread Hesham Almatary 
On Tue, Mar 1, 2016 at 2:03 PM, Jakob Viketoft
 wrote:
> 
> From: devel [devel-boun...@rtems.org] on behalf of Hesham Almatary 
> [heshamelmat...@gmail.com]
> Sent: Saturday, February 27, 2016 19:57
> To: Jakob Viketoft
> Cc: rtems-de...@rtems.org
> Subject: Re: [PATCH 5/8] generic_or1k BSP clock driver correction
>
>>On Sat, Feb 20, 2016 at 11:01 PM,   wrote:
>>> From: Jakob Viketoft 
>>>
>>>  - Improve the clock driver to use RTEMS default tick period
>>>or the on the one supplied by the application
>>>  - Avoid rewriting the timer settings, since all we need is to clear the 
>>> interrupt
>>>  - Remove any mention of or1ksim in favour of generic_or1k
>>>
>>> Close #2600
>>> ---
>>>  .../lib/libbsp/or1k/generic_or1k/clock/clockdrv.c  | 109 
>>> ++---
>>>  1 file changed, 51 insertions(+), 58 deletions(-)
>>>
>>> diff --git a/c/src/lib/libbsp/or1k/generic_or1k/clock/clockdrv.c 
>>> b/c/src/lib/libbsp/or1k/generic_or1k/clock/clockdrv.c
>>> index e01d2e5..60eec98 100644
>>> --- a/c/src/lib/libbsp/or1k/generic_or1k/clock/clockdrv.c
>>> +++ b/c/src/lib/libbsp/or1k/generic_or1k/clock/clockdrv.c
>>> @@ -3,13 +3,15 @@
>>>   *
>>>   * @ingroup bsp_clock
>>>   *
>>> - * @brief or1k clock support.
>>> + * @brief generic_or1k clock support.
>>>   */
>>>
>>>  /*
>>>   * generic_or1k Clock driver
>>>   *
>>>   * COPYRIGHT (c) 2014-2015 Hesham ALMatary 
>>> + * Copyright (c) 2014-2016 ÅAC Microtec AB 
>>> + * Jakob Viketoft 
>>>   *
>>>   * The license and distribution terms for this file may be
>>>   * found in the file LICENSE in this distribution or at
>>> @@ -25,35 +27,30 @@
>>>  #include 
>>>
>>>  /* The number of clock cycles before generating a tick timer interrupt. */
>>> -#define TTMR_NUM_OF_CLOCK_TICKS_INTERRUPT 0x09ED9
>>> -#define OR1K_CLOCK_CYCLE_TIME_NANOSECONDS 10
>>> +#define OR1K_CLOCK_CYCLE_TIME_NANOSECONDS (10 / 
>>> OR1K_BSP_CLOCK_FREQ)
>>clockdrv.c:30:61: error: 'OR1K_BSP_CLOCK_FREQ' undeclared (first use
>>in this function)
>
> Sorry for the delay in responding, it took me a while to figure this one out 
> since I had to build a new toolchain and stuff to make sure I was using same 
> as you. I had rather quickly transfered the change from what we were doing in 
> our own BSP.
>
Thanks for doing this.

> Basically, there is a copy-paste error between the generic_or1k/include/bsp.h 
> and generic_or1k/include/generic_or1k.h include guards which both define the 
> same thing. Change the one in bsp.h and everything compiles as it should. 
> This is somewhat outside this patch's intentions, but should this patch 
> address this as well?
>
Great catch. I already have a local fix, if you prefer not to submit a
patch for this bug separately, I am happy to submit it.

> Jakob Viketoft
> Senior Engineer in RTL and embedded software
>
> ÅAC Microtec AB
> Dag Hammarskjölds väg 48
> SE-751 83 Uppsala, Sweden
>
> T: +46 702 80 95 97
> http://www.aacmicrotec.com



-- 
Hesham
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH 5/8] generic_or1k BSP clock driver correction

2016-03-02 Thread Hesham Almatary 
Hi Jakob,

I reapplied your patches after the include guard issue and it compiles
fine. However, helloworld and ticker samples don't work on either
or1ksim or qemu. Both run fine without your patches applied. Since not
all the users have a hardware platform, RTEMS prefers that each port
runs at least hello and ticker on one or more simulators. So it would
be great if you can test your patches on or1ksim and/or qemu as the
main targets for testing.

There's a readme file at the generic_or1k directory that contains some
instructions how to run the test cases. Also, RTEMS has two other
systems for testing purposes like sim-scripts [1] which has scripts to
run test cases, and RTEMS Tester [2] that automates running the whole
500+ tests. or1k port within RTEMS Tester depends on qemu-system-or32
and not or1ksim.

I'd be happy to provide any help if required.

[1] https://devel.rtems.org/browser/rtems-testing/sim-scripts
[2] https://devel.rtems.org/wiki/Testing/Tester

Best,
Hesham

On Wed, Mar 2, 2016 at 11:44 AM, Hesham Almatary
 wrote:
> On Tue, Mar 1, 2016 at 2:03 PM, Jakob Viketoft
>  wrote:
>> 
>> From: devel [devel-boun...@rtems.org] on behalf of Hesham Almatary 
>> [heshamelmat...@gmail.com]
>> Sent: Saturday, February 27, 2016 19:57
>> To: Jakob Viketoft
>> Cc: rtems-de...@rtems.org
>> Subject: Re: [PATCH 5/8] generic_or1k BSP clock driver correction
>>
>>>On Sat, Feb 20, 2016 at 11:01 PM,   wrote:
 From: Jakob Viketoft 

  - Improve the clock driver to use RTEMS default tick period
or the on the one supplied by the application
  - Avoid rewriting the timer settings, since all we need is to clear the 
 interrupt
  - Remove any mention of or1ksim in favour of generic_or1k

 Close #2600
 ---
  .../lib/libbsp/or1k/generic_or1k/clock/clockdrv.c  | 109 
 ++---
  1 file changed, 51 insertions(+), 58 deletions(-)

 diff --git a/c/src/lib/libbsp/or1k/generic_or1k/clock/clockdrv.c 
 b/c/src/lib/libbsp/or1k/generic_or1k/clock/clockdrv.c
 index e01d2e5..60eec98 100644
 --- a/c/src/lib/libbsp/or1k/generic_or1k/clock/clockdrv.c
 +++ b/c/src/lib/libbsp/or1k/generic_or1k/clock/clockdrv.c
 @@ -3,13 +3,15 @@
   *
   * @ingroup bsp_clock
   *
 - * @brief or1k clock support.
 + * @brief generic_or1k clock support.
   */

  /*
   * generic_or1k Clock driver
   *
   * COPYRIGHT (c) 2014-2015 Hesham ALMatary 
 + * Copyright (c) 2014-2016 ÅAC Microtec AB 
 + * Jakob Viketoft 
   *
   * The license and distribution terms for this file may be
   * found in the file LICENSE in this distribution or at
 @@ -25,35 +27,30 @@
  #include 

  /* The number of clock cycles before generating a tick timer interrupt. */
 -#define TTMR_NUM_OF_CLOCK_TICKS_INTERRUPT 0x09ED9
 -#define OR1K_CLOCK_CYCLE_TIME_NANOSECONDS 10
 +#define OR1K_CLOCK_CYCLE_TIME_NANOSECONDS (10 / 
 OR1K_BSP_CLOCK_FREQ)
>>>clockdrv.c:30:61: error: 'OR1K_BSP_CLOCK_FREQ' undeclared (first use
>>>in this function)
>>
>> Sorry for the delay in responding, it took me a while to figure this one out 
>> since I had to build a new toolchain and stuff to make sure I was using same 
>> as you. I had rather quickly transfered the change from what we were doing 
>> in our own BSP.
>>
> Thanks for doing this.
>
>> Basically, there is a copy-paste error between the 
>> generic_or1k/include/bsp.h and generic_or1k/include/generic_or1k.h include 
>> guards which both define the same thing. Change the one in bsp.h and 
>> everything compiles as it should. This is somewhat outside this patch's 
>> intentions, but should this patch address this as well?
>>
> Great catch. I already have a local fix, if you prefer not to submit a
> patch for this bug separately, I am happy to submit it.
>
>> Jakob Viketoft
>> Senior Engineer in RTL and embedded software
>>
>> ÅAC Microtec AB
>> Dag Hammarskjölds väg 48
>> SE-751 83 Uppsala, Sweden
>>
>> T: +46 702 80 95 97
>> http://www.aacmicrotec.com
>
>
>
> --
> Hesham



-- 
Hesham
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2016

2016-03-02 Thread Viktoriya Vasiliev 
Hello Gedare,



> Welcome to RTEMS! You should see our Getting Started guide especially
> oriented toward GSoC students, at
> https://devel.rtems.org/wiki/GSoC/GettingStarted
>
> Please note the current master branch of RTEMS is now version 4.12, so
> adjust any use of 4.11 to be 4.12 when working with 'master' branch.
>

Sorry for the late reply; first of all I will like to congratulate RTEMS
for her selection to participate in the Google Summer of Code 2016. I am
interested in working on Improving the POSIX compliance for RTEMS project.
I will get started on my proposal while preparing my patch. I will share
with you or +Joel when ready.

Thanks,
Viktoriya
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2016

2016-03-02 Thread Joel Sherrill 
On Wed, Mar 2, 2016 at 12:11 PM, Viktoriya Vasiliev <
viktoriyavasil...@gmail.com> wrote:

> Hello Gedare,
>
>
>
>> Welcome to RTEMS! You should see our Getting Started guide especially
>> oriented toward GSoC students, at
>> https://devel.rtems.org/wiki/GSoC/GettingStarted
>>
>> Please note the current master branch of RTEMS is now version 4.12, so
>> adjust any use of 4.11 to be 4.12 when working with 'master' branch.
>>
>
> Sorry for the late reply; first of all I will like to congratulate RTEMS
> for her selection to participate in the Google Summer of Code 2016. I am
> interested in working on Improving the POSIX compliance for RTEMS project.
> I will get started on my proposal while preparing my patch. I will share
> with you or +Joel when ready.
>
> I hope you are referring to the hello world patch. :)

On the POSIX Compliance, I have some work in progress that needs to be
submitted
so don't starting coding without chatting with us. Plenty to do so no
worries, just
coordination needed.

As part of defining the work on that project, we will have to help you pick
an order to tackle things in. We can do that as part of your proposal.
If you want to take a swing at one of the easier issues to get a taste,
perhaps
Gedare and I can identify something to tackle.

--joel




> Thanks,
> Viktoriya
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2016

2016-03-02 Thread Gedare Bloom 
ok, please discuss further with Joel, as he is the primary mentor for
that project.

On Wed, Mar 2, 2016 at 1:11 PM, Viktoriya Vasiliev
 wrote:
> Hello Gedare,
>
>
>>
>> Welcome to RTEMS! You should see our Getting Started guide especially
>> oriented toward GSoC students, at
>> https://devel.rtems.org/wiki/GSoC/GettingStarted
>>
>> Please note the current master branch of RTEMS is now version 4.12, so
>> adjust any use of 4.11 to be 4.12 when working with 'master' branch.
>
>
> Sorry for the late reply; first of all I will like to congratulate RTEMS for
> her selection to participate in the Google Summer of Code 2016. I am
> interested in working on Improving the POSIX compliance for RTEMS project. I
> will get started on my proposal while preparing my patch. I will share with
> you or +Joel when ready.
>
> Thanks,
> Viktoriya
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2016

2016-03-02 Thread Joel Sherrill 
On Wed, Mar 2, 2016 at 12:48 PM, Gedare Bloom  wrote:

> ok, please discuss further with Joel, as he is the primary mentor for
> that project.
>
> +1

But now that we have someone interested, I would like to order the possible
things to tackle with you.

Some of them are newlib and we can possibly get some mentoring help
from there.

--joel


> On Wed, Mar 2, 2016 at 1:11 PM, Viktoriya Vasiliev
>  wrote:
> > Hello Gedare,
> >
> >
> >>
> >> Welcome to RTEMS! You should see our Getting Started guide especially
> >> oriented toward GSoC students, at
> >> https://devel.rtems.org/wiki/GSoC/GettingStarted
> >>
> >> Please note the current master branch of RTEMS is now version 4.12, so
> >> adjust any use of 4.11 to be 4.12 when working with 'master' branch.
> >
> >
> > Sorry for the late reply; first of all I will like to congratulate RTEMS
> for
> > her selection to participate in the Google Summer of Code 2016. I am
> > interested in working on Improving the POSIX compliance for RTEMS
> project. I
> > will get started on my proposal while preparing my patch. I will share
> with
> > you or +Joel when ready.
> >
> > Thanks,
> > Viktoriya
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Gsoc 2016 project proposal

2016-03-02 Thread punit vara 
 I have asked for BBB BSP proposal before but I haven't found any good
response from someone. What are the projects you are going to mentor @joel
? Would anyone please suggest me to pick any other project ?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Gsoc 2016 project proposal

2016-03-02 Thread Hesham Almatary 
Hi Punit,

You can have a look at the open projects here [1] and find one or more
that match your experience/interests.

[1] https://devel.rtems.org/wiki/Developer/OpenProjects

Regards,

On Wed, Mar 2, 2016 at 7:14 PM, punit vara  wrote:
>  I have asked for BBB BSP proposal before but I haven't found any good
> response from someone. What are the projects you are going to mentor @joel ?
> Would anyone please suggest me to pick any other project ?
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel



-- 
Hesham
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

BBB GSoC Projects was Re: Gsoc 2016 project proposal

2016-03-02 Thread Joel Sherrill 
On Wed, Mar 2, 2016 at 1:24 PM, Hesham Almatary 
wrote:

> Hi Punit,
>
> You can have a look at the open projects here [1] and find one or more
> that match your experience/interests.
>
> [1] https://devel.rtems.org/wiki/Developer/OpenProjects
>
>
I have added Ben Gras. He knows more about the BBB than anyone. I am unsure
what is left
to do. Have you compared the status of last year's projects versus the git
repository?

--joel


> Regards,
>
> On Wed, Mar 2, 2016 at 7:14 PM, punit vara  wrote:
> >  I have asked for BBB BSP proposal before but I haven't found any good
> > response from someone. What are the projects you are going to mentor
> @joel ?
> > Would anyone please suggest me to pick any other project ?
> >
> > ___
> > devel mailing list
> > devel@rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
>
>
>
> --
> Hesham
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: BBB GSoC Projects was Re: Gsoc 2016 project proposal

2016-03-02 Thread punit vara 
Yes I have checked previous year work of ketul . He has done ADC and GPIO
BSP . It seems SPI,USB BSP need to be developed as I have checked rtems.git
and I am not sure about I2C .I asked last year student Ketul .According to
him , I2c is also need to be modified. I tried to contact Ben but he is
unreachable on mailing list :-(

On Thu, Mar 3, 2016 at 12:57 AM, Joel Sherrill  wrote:

>
>
> On Wed, Mar 2, 2016 at 1:24 PM, Hesham Almatary 
> wrote:
>
>> Hi Punit,
>>
>> You can have a look at the open projects here [1] and find one or more
>> that match your experience/interests.
>>
>> [1] https://devel.rtems.org/wiki/Developer/OpenProjects
>>
>>
> I have added Ben Gras. He knows more about the BBB than anyone. I am
> unsure what is left
> to do. Have you compared the status of last year's projects versus the git
> repository?
>
> --joel
>
>
>> Regards,
>>
>> On Wed, Mar 2, 2016 at 7:14 PM, punit vara  wrote:
>> >  I have asked for BBB BSP proposal before but I haven't found any good
>> > response from someone. What are the projects you are going to mentor
>> @joel ?
>> > Would anyone please suggest me to pick any other project ?
>> >
>> > ___
>> > devel mailing list
>> > devel@rtems.org
>> > http://lists.rtems.org/mailman/listinfo/devel
>>
>>
>>
>> --
>> Hesham
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Gsoc 2016 project proposal

2016-03-02 Thread punit vara 
I am interested in following projects apart from BBB BSP :

1. Improve Posix compliance
2.  TCP/IP stack update (Please suggest me more readings for this)

What are the prerequisites I need to do to improve my chances ? please let
me know.

On Thu, Mar 3, 2016 at 12:54 AM, Hesham Almatary 
wrote:

> Hi Punit,
>
> You can have a look at the open projects here [1] and find one or more
> that match your experience/interests.
>
> [1] https://devel.rtems.org/wiki/Developer/OpenProjects
>
> Regards,
>
> On Wed, Mar 2, 2016 at 7:14 PM, punit vara  wrote:
> >  I have asked for BBB BSP proposal before but I haven't found any good
> > response from someone. What are the projects you are going to mentor
> @joel ?
> > Would anyone please suggest me to pick any other project ?
> >
> > ___
> > devel mailing list
> > devel@rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
>
>
>
> --
> Hesham
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: BBB GSoC Projects was Re: Gsoc 2016 project proposal

2016-03-02 Thread Joel Sherrill 
On Wed, Mar 2, 2016 at 1:41 PM, punit vara  wrote:

> Yes I have checked previous year work of ketul . He has done ADC and GPIO
> BSP . It seems SPI,USB BSP need to be developed as I have checked rtems.git
> and I am not sure about I2C .I asked last year student Ketul .According to
> him , I2c is also need to be modified. I tried to contact Ben but he is
> unreachable on mailing list :-(
>
>
Let me reach out to Ketul and see if a private ping helps.

Start with the assumption that USB needs work. That involves the
rtems-libbsd tree and
there is likely code to import from FreeBSD that will help a lot.

SPI and i2c are close to one another in my understanding. Likely Ketul is
referring to changes
in the RTEMS i2c interfaces.

My recollection is that the NIC had performance issues based on the version
of U-Boot
used. There was some traffic at the end of GSoC about this. I don't know if
it was
ever resolved.  But the NIC should work. Maybe worth benchmarking.

--joel


On Thu, Mar 3, 2016 at 12:57 AM, Joel Sherrill  wrote:
>
>>
>>
>> On Wed, Mar 2, 2016 at 1:24 PM, Hesham Almatary > > wrote:
>>
>>> Hi Punit,
>>>
>>> You can have a look at the open projects here [1] and find one or more
>>> that match your experience/interests.
>>>
>>> [1] https://devel.rtems.org/wiki/Developer/OpenProjects
>>>
>>>
>> I have added Ben Gras. He knows more about the BBB than anyone. I am
>> unsure what is left
>> to do. Have you compared the status of last year's projects versus the
>> git repository?
>>
>> --joel
>>
>>
>>> Regards,
>>>
>>> On Wed, Mar 2, 2016 at 7:14 PM, punit vara  wrote:
>>> >  I have asked for BBB BSP proposal before but I haven't found any good
>>> > response from someone. What are the projects you are going to mentor
>>> @joel ?
>>> > Would anyone please suggest me to pick any other project ?
>>> >
>>> > ___
>>> > devel mailing list
>>> > devel@rtems.org
>>> > http://lists.rtems.org/mailman/listinfo/devel
>>>
>>>
>>>
>>> --
>>> Hesham
>>> ___
>>> devel mailing list
>>> devel@rtems.org
>>> http://lists.rtems.org/mailman/listinfo/devel
>>>
>>
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: BBB GSoC Projects was Re: Gsoc 2016 project proposal

2016-03-02 Thread punit vara 
On Thu, Mar 3, 2016 at 1:26 AM, Joel Sherrill  wrote:

>
>
> On Wed, Mar 2, 2016 at 1:41 PM, punit vara  wrote:
>
>> Yes I have checked previous year work of ketul . He has done ADC and GPIO
>> BSP . It seems SPI,USB BSP need to be developed as I have checked rtems.git
>> and I am not sure about I2C .I asked last year student Ketul .According to
>> him , I2c is also need to be modified. I tried to contact Ben but he is
>> unreachable on mailing list :-(
>>
>>
> Let me reach out to Ketul and see if a private ping helps.
>
> Start with the assumption that USB needs work. That involves the
> rtems-libbsd tree and
> there is likely code to import from FreeBSD that will help a lot.
>
> SPI and i2c are close to one another in my understanding. Likely Ketul is
> referring to changes
> in the RTEMS i2c interfaces.
>
> My recollection is that the NIC had performance issues based on the
> version of U-Boot
> used. There was some traffic at the end of GSoC about this. I don't know
> if it was
> ever resolved.  But the NIC should work. Maybe worth benchmarking.
>
> --joel
>
>
> On Thu, Mar 3, 2016 at 12:57 AM, Joel Sherrill  wrote:
>>
>>>
>>>
>>> On Wed, Mar 2, 2016 at 1:24 PM, Hesham Almatary <
>>> heshamelmat...@gmail.com> wrote:
>>>
 Hi Punit,

 You can have a look at the open projects here [1] and find one or more
 that match your experience/interests.

 [1] https://devel.rtems.org/wiki/Developer/OpenProjects


>>> I have added Ben Gras. He knows more about the BBB than anyone. I am
>>> unsure what is left
>>> to do. Have you compared the status of last year's projects versus the
>>> git repository?
>>>
>>> --joel
>>>
>>>
 Regards,

 On Wed, Mar 2, 2016 at 7:14 PM, punit vara  wrote:
 >  I have asked for BBB BSP proposal before but I haven't found any good
 > response from someone. What are the projects you are going to mentor
 @joel ?
 > Would anyone please suggest me to pick any other project ?
 >
 > ___
 > devel mailing list
 > devel@rtems.org
 > http://lists.rtems.org/mailman/listinfo/devel



 --
 Hesham
 ___
 devel mailing list
 devel@rtems.org
 http://lists.rtems.org/mailman/listinfo/devel

>>>
>>>
>>
> Thank you . Please let me know about Usb if you get some information. I
will also look into NIC benchmarking.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: BBB GSoC Projects was Re: Gsoc 2016 project proposal

2016-03-02 Thread Marcos Díaz 
On Wed, Mar 2, 2016 at 4:56 PM, Joel Sherrill  wrote:

>
>
> On Wed, Mar 2, 2016 at 1:41 PM, punit vara  wrote:
>
>> Yes I have checked previous year work of ketul . He has done ADC and GPIO
>> BSP . It seems SPI,USB BSP need to be developed as I have checked rtems.git
>> and I am not sure about I2C .I asked last year student Ketul .According to
>> him , I2c is also need to be modified. I tried to contact Ben but he is
>> unreachable on mailing list :-(
>>
>>
> Let me reach out to Ketul and see if a private ping helps.
>
> Start with the assumption that USB needs work. That involves the
> rtems-libbsd tree and
> there is likely code to import from FreeBSD that will help a lot.
>
> SPI and i2c are close to one another in my understanding. Likely Ketul is
> referring to changes
> in the RTEMS i2c interfaces.
>
> My recollection is that the NIC had performance issues based on the
> version of U-Boot
> used. There was some traffic at the end of GSoC about this. I don't know
> if it was
> ever resolved.  But the NIC should work. Maybe worth benchmarking.
>
We had more of these problems when trying to use I2C. It was fixed in
https://git.rtems.org/rtems/commit/?id=8c5c53f4788eb74264a053f8293fed26da85b764.
I think we dont need tos ee these problems any more

>
> --joel
>
>
> On Thu, Mar 3, 2016 at 12:57 AM, Joel Sherrill  wrote:
>>
>>>
>>>
>>> On Wed, Mar 2, 2016 at 1:24 PM, Hesham Almatary <
>>> heshamelmat...@gmail.com> wrote:
>>>
 Hi Punit,

 You can have a look at the open projects here [1] and find one or more
 that match your experience/interests.

 [1] https://devel.rtems.org/wiki/Developer/OpenProjects


>>> I have added Ben Gras. He knows more about the BBB than anyone. I am
>>> unsure what is left
>>> to do. Have you compared the status of last year's projects versus the
>>> git repository?
>>>
>>> --joel
>>>
>>>
 Regards,

 On Wed, Mar 2, 2016 at 7:14 PM, punit vara  wrote:
 >  I have asked for BBB BSP proposal before but I haven't found any good
 > response from someone. What are the projects you are going to mentor
 @joel ?
 > Would anyone please suggest me to pick any other project ?
 >
 > ___
 > devel mailing list
 > devel@rtems.org
 > http://lists.rtems.org/mailman/listinfo/devel



 --
 Hesham
 ___
 devel mailing list
 devel@rtems.org
 http://lists.rtems.org/mailman/listinfo/devel

>>>
>>>
>>
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>



-- 

__




Marcos Díaz

Software Engineer


San Lorenzo 47, 3rd Floor, Office 5

Córdoba, Argentina


Phone: +54 351 4217888 / +54 351 4218211/ +54 351 7617452

Skype: markdiaz22
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: BBB GSoC Projects was Re: Gsoc 2016 project proposal

2016-03-02 Thread Joel Sherrill 
On Wed, Mar 2, 2016 at 2:22 PM, Marcos Díaz <
marcos.d...@tallertechnologies.com> wrote:

>
>
> On Wed, Mar 2, 2016 at 4:56 PM, Joel Sherrill  wrote:
>
>>
>>
>> On Wed, Mar 2, 2016 at 1:41 PM, punit vara  wrote:
>>
>>> Yes I have checked previous year work of ketul . He has done ADC and
>>> GPIO BSP . It seems SPI,USB BSP need to be developed as I have checked
>>> rtems.git and I am not sure about I2C .I asked last year student Ketul
>>> .According to him , I2c is also need to be modified. I tried to contact Ben
>>> but he is unreachable on mailing list :-(
>>>
>>>
>> Let me reach out to Ketul and see if a private ping helps.
>>
>> Start with the assumption that USB needs work. That involves the
>> rtems-libbsd tree and
>> there is likely code to import from FreeBSD that will help a lot.
>>
>> SPI and i2c are close to one another in my understanding. Likely Ketul is
>> referring to changes
>> in the RTEMS i2c interfaces.
>>
>> My recollection is that the NIC had performance issues based on the
>> version of U-Boot
>> used. There was some traffic at the end of GSoC about this. I don't know
>> if it was
>> ever resolved.  But the NIC should work. Maybe worth benchmarking.
>>
> We had more of these problems when trying to use I2C. It was fixed in
>
> https://git.rtems.org/rtems/commit/?id=8c5c53f4788eb74264a053f8293fed26da85b764.
> I think we dont need tos ee these problems any more
>
>>
>>
Marcos.. does this mean that the BBB i2c is complete now?

And is my understanding that this covers SPI correct?

What else on the BBB is left?

--joel


> --joel
>>
>>
>> On Thu, Mar 3, 2016 at 12:57 AM, Joel Sherrill  wrote:
>>>


 On Wed, Mar 2, 2016 at 1:24 PM, Hesham Almatary <
 heshamelmat...@gmail.com> wrote:

> Hi Punit,
>
> You can have a look at the open projects here [1] and find one or more
> that match your experience/interests.
>
> [1] https://devel.rtems.org/wiki/Developer/OpenProjects
>
>
 I have added Ben Gras. He knows more about the BBB than anyone. I am
 unsure what is left
 to do. Have you compared the status of last year's projects versus the
 git repository?

 --joel


> Regards,
>
> On Wed, Mar 2, 2016 at 7:14 PM, punit vara 
> wrote:
> >  I have asked for BBB BSP proposal before but I haven't found any
> good
> > response from someone. What are the projects you are going to mentor
> @joel ?
> > Would anyone please suggest me to pick any other project ?
> >
> > ___
> > devel mailing list
> > devel@rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
>
>
>
> --
> Hesham
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>


>>>
>>
>> ___
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>>
>
>
>
> --
>
> __
>
> 
>
>
> Marcos Díaz
>
> Software Engineer
>
>
> San Lorenzo 47, 3rd Floor, Office 5
>
> Córdoba, Argentina
>
>
> Phone: +54 351 4217888 / +54 351 4218211/ +54 351 7617452
>
> Skype: markdiaz22
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2016

2016-03-02 Thread Chris Johns 

On 03/03/2016 05:49, Joel Sherrill wrote:



On the POSIX Compliance, I have some work in progress that needs to be
submitted
so don't starting coding without chatting with us. Plenty to do so no
worries, just
coordination needed.

As part of defining the work on that project, we will have to help you pick
an order to tackle things in. We can do that as part of your proposal.
If you want to take a swing at one of the easier issues to get a taste,
perhaps
Gedare and I can identify something to tackle.



There is also updating the POSIX User manual. :)

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC 2016

2016-03-02 Thread Joel Sherrill 
On Wed, Mar 2, 2016 at 7:10 PM, Chris Johns  wrote:

> On 03/03/2016 05:49, Joel Sherrill wrote:
>
>>
>>
>> On the POSIX Compliance, I have some work in progress that needs to be
>> submitted
>> so don't starting coding without chatting with us. Plenty to do so no
>> worries, just
>> coordination needed.
>>
>> As part of defining the work on that project, we will have to help you
>> pick
>> an order to tackle things in. We can do that as part of your proposal.
>> If you want to take a swing at one of the easier issues to get a taste,
>> perhaps
>> Gedare and I can identify something to tackle.
>>
>>
> There is also updating the POSIX User manual. :)
>
> Yes and we both know that documentation by itself is not a GSoC task. But
anytime someone does work in an area, it is expected the documentation
will get touched for that area. So some documentation work is expected. :)


> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel