[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] [Bug #3327] I read from phorum that outb() is deprec
From: |
E. Weddington |
Subject: |
Re: [avr-libc-dev] [Bug #3327] I read from phorum that outb() is deprecated? But still can found a note from library "Use outb |
Date: |
Tue, 29 Apr 2003 10:22:44 -0600 |
On 29 Apr 2003 at 9:06, Theodore A. Roth wrote:
>
>
> On Tue, 29 Apr 2003, E. Weddington wrote:
>
> :) On 28 Apr 2003 at 23:41, address@hidden wrote:
> :)
> :) > There are some portability issues that are better handled by
> using :) > outb() instead of the <SFR> = <VAL>; idiom. :) :) Such as?
>
> Not so much portability, but a valid point:
> http://www.egnite.de/pipermail/en-nut-discussion/2003-April/000670.h
> tml
>
> Also, It's conceivable that someone could want to use a chunk of on
> linux (using direct io access) or some other system and avr. Of
> course, it would be some ugly code full of #if's and such.
>
> If someone has some compelling arguments for deprecating outb and
> friends, the bug report can be reopened.
>
Hmmm.
You're right.
After going through the convolutions in sfr_defs.h, the outb, inb,
etc. macros look to be equivalent to the <sfr> = <val> idiom. And I
can now see the portability issues.
Perhaps (eventually) adding a note about portability issues and the
reasons for using / not using these macros in the docs would help
though.
No arguments. Bug stays invalid and closed.
Thanks Ted.
Eric