[En-Nut-Discussion] Unified GPIO implementation

[Ulrich Prinz]

Hi Thiago,

I just merged my internal Nut/OS to the branch and discontinued the 
internal one.
Now I think of how to go best way. Harald told me how to use the 
master-script to build all platforms and check if the compile is successful.
Then I could merge to trunk.

On the other hand, I can upgrade USARTs and uGPIO and then do the merge 
thing. I think USART ans uGPIO is important so let me finish my PHY 
abstraction and may be send one packet over the STM32 EMAC. Then uGPIO, 
USART and merge to trunk.

Oha, only a few weeks left till Christmas... And so much to do...

Ah, if we finished uGPIO, can we do a collection of LEDs? It is so 
helpfull to simply have a blinking LED and Nut/OS unifies USARTs, SPI, 
EMACs for all the supported Boards, but the LEDs and push buttons are 
missing.

Best regards
Ulrich

Am 26.10.2010 00:06, schrieb Thiago A. Corrêa:
> Hi,
>
> On Mon, Oct 25, 2010 at 4:57 PM, Ulrich Prinz<uprinz2 at netscape.net>  wrote:
>>> It isn't too much work to simply satisfy the specs. It can be
>>> optimized on each platform later after the merge, as long as the
>>> public interface doesn't change.
>>>
>> Hehe, that was the intention!
>>
>
>    Ok, I believe I've finished with "just satisfing the specs".
>    Notice that NUTGPIO_PORTA == NUTGPIO_PORT now, so all ports are
> shifted by 1 for some archs like ARM. For AVR32 it was already like
> that, so I just removed a case in the switch that became duplicated.
>
>    Could you take a look at it and see if that's what you intended?
>    Next I can take advantage of the fact that NUTGPIO_PORTx is now
> platform specific and make it&AVR32_GPIO.port[x] directly (make it
> the register address). I think similar optimization can be made for
> AVR 8 bits.
>
> Kind Regards,
>      Thiago A. Correa
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion