[PATCH] Add GPIO, I2C and SPI support for the RPi BSP

[Gedare Bloom]

A standalone framework for drivers would be quite useful. That, or
improved support for drivers (HAL) in RTEMS is needed to achieve a
maintainable solution. -Gedare

On Wed, Nov 5, 2014 at 10:10 AM, Alan Cudmore <alan.cudmore at gmail.com> wrote:
> This is a tough problem. We have plenty of inexpensive SPI and I2C devices
> to mix and match with low cost boards such as the Pi and Beaglebone, but it
> could all become obsolete quickly.
> If we put a bunch of SPI and I2C drivers in the RTEMS repo, then how do we
> test and maintain them without duplicating a custom breadboard setup?
>
> Even an examples repo will have to come with a schematic to build the setup
> necessary to run a program.
>
> I have RTEMS drivers for some of the devices I have connected to my Pi, such
> as the DS1302 RTC, an I2C GPIO expansion port, and an LCD display. I was
> going to expand my RKI application to have a driver framework, so these type
> of drivers could be integrated and tested without having to integrate them
> into the RTEMS tree and BSP.
>
> Alan
>
> On Wed, Nov 5, 2014 at 9:32 AM, Gedare Bloom <gedare at rtems.org> wrote:
>>
>> I'm in support of putting bsp-specific examples in examples-v2. And
>> renaming the repository...
>>
>> Reducing repo sprawl is good.
>>
>> -Gedare
>>
>> On Wed, Nov 5, 2014 at 12:32 AM, Chris Johns <chrisj at rtems.org> wrote:
>> > On 5/11/2014 2:40 pm, Gedare Bloom wrote:
>> >>
>> >> These are ideal for BSP-specific testing framework, which we presently
>> >> lack. I'm not certain where they should go.
>> >
>> >
>> > What about examples-v2 ? You could add a boards directory and the code
>> > under
>> > arch/bsp. The waf build system lets you know when a specific arch/bsp is
>> > being built.
>> >
>> >> Maybe a repo for BSP-specific examples is a useful idea.
>> >
>> >
>> > I am attempting to lower the number of repos we have. Every repo needs
>> > testing.
>> >
>> > Chris
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>