Hello demo on RPI

[Alan Cudmore]

Nice work Qiao!

Andre had submitted the patches for GPIO, SPI, and I2C including
recommended fixes. It was then recommended that we switch to the new Linux
based I2C API, and we ( or I ) got stuck there.
For the time I have available, it was not going to be a 1 or 2 day fix to
move Andre's I2C implementation to the new Linux based API. It was taking
me a while just to understand what needed to be done.

A little later today, I will try to come up with a proposal to split the Pi
work so it can be done by 3 participants.. But we need to decide if
re-doing the I2C implementation should be part of the work, or if we should
use Andre's initial implementation as a baseline for everyone.

Also, I will submit basic patches to create a raspberrypi2 BSP variant. I
have built both the raspberrypi and raspberrypi2 BSPs and tested ticker so
far.

Alan


On Sun, Mar 15, 2015 at 7:11 AM, Gedare Bloom <gedare at rtems.org> wrote:

>
>
> On Sun, Mar 15, 2015 at 5:50 AM, QIAO YANG <yangqiao0505 at me.com> wrote:
>
>> Hi !
>>
>> I've managed to run a hello demo on RPI B/B+, including a demo for
>> loading an image by u-boot (I don't have an ethernet cable on my hand, but
>> I'm going to be able to load the image by tftp for dev).
>>
>> If I've got it right, to prepare my proposal I may choose part of the
>> TODO list , look into the implementation detail and schedule it. The work
>> list may be divided for 3 students to complete.
>>
>> I've checked out the André's branch with GPIO, I2C, SPI implementations.
>> Should we develop based on his branch or the upstream? Have we said that
>> the I2C, SPI API has changed? I wonder that if anyone is working on it and
>> if we will merge Andre's work to upstream at the begining of GSOC. If not,
>> maybe I can get start by trying to do this job.
>>
>> The obvious projects I see from
> https://devel.rtems.org/wiki/Developer/Projects/Open/ImproveRaspberryPiBSP
> are:
> 1) Get #1-3 mergeable. May not take much. Then do #4 SD-card support and
> refactor the i2c to use the newer cpukit/dev/i2c interface.
> 2) #5 Graphics Frame Buffer + #7 HDMI/Graphics console
> 3) #6 USB + #7 Networking
> 4) Raspberry Pi 2 support, but this probably isn't enough.
>
> -Gedare
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20150315/1190060c/attachment-0002.html>