> CBFalconer <cbfalco...@yahoo.com> wrote:
>
>> I find no reference to iohw.h. Where is this documented?
>
> here:
> <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1021.pdf>
> see section 4 Basic I/O hardware addressing
>
> This is one of those optional add on specs for embedded folks.
> (Don't expect to see it in Visual C++ anytime soon :)
On Oct 16, 4:37 pm, CBFalconer <cbfalco...@yahoo.com> wrote:
>
> I find no reference to iohw.h. Where is this documented?
here:
<http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1021.pdf>
see section 4 Basic I/O hardware addressing
This is one of those optional add on specs for embedded folks. (Don't
expect to see it in Visual C++ anytime soon :)
But if most embedded compilers won't provide it then the embedded
community won't adopt it and it will rot on the vine.
==============================================
"
Embedded-C (ISO/IEC TR 18037:2004)
ISO/IEC TR 18037:2004
Extensions to the programming language C to support fixed-point
arithmetic, named address spaces and basic I/O hardware addressing.
These features are commonly found in embedded processors and are not
supported by the standard C language.
Technical Gains
Until recently, embedded processors were programmed in assembly
language to make use of all the specific performance improving
hardware features. By standardizing the C interface it is possible to
program embedded processors with their ever increasing complex
functionality using a high level language, thereby increasing
portability and stability of the programs.
Previous Revisions/Versions
Embedded C is largely based on DSP-C, an industry standard defined by
ACE and Philips.
"
Reply by Walter Banks●October 17, 20082008-10-17
CBFalconer wrote:
> Marco wrote:
> >
> > A while back the ISO C group added to the C standard with TR18015
> > and TR18037
> > <iohw.h>
> > to create low-level I/O hardware drivers in C that are easier to
> > port. Is anyone using this? Do many vendors support this yet?
>
> On the latest draft of the future C standard, found at:
>
> <http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1336.pdf>
>
> I find no reference to iohw.h. Where is this documented?
ISO/IEC 18037
w,,
Reply by CBFalconer●October 16, 20082008-10-16
Marco wrote:
>
> A while back the ISO C group added to the C standard with TR18015
> and TR18037
> <iohw.h>
> to create low-level I/O hardware drivers in C that are easier to
> port. Is anyone using this? Do many vendors support this yet?
Marco,
iohw.h and its support libraries makes sense because they create a standard
interface. The missing part of iohw.h is they are neither a fully developed
application interface or a low level interface
Quite a few companies have implemented the named address space parts
of 18037 and the direct processor access. The named address and user
address parts can accomplish a very portable low level hardware interface.
The real role of 18037 is to define the low level interfaces and fixed point
math. In hindsight iohw.h was an important stepping stone to understanding
what was needed at a low level.
I know some application developers that created higher level application
interfaces on this base. (Especially in the cell phone industry)
Regards
--
Walter Banks
Byte Craft Limited
http://www.bytecraft.com
Marco wrote:
> A while back the ISO C group added to the C standard with TR18015 and
> TR18037
>
> <iohw.h>
> to create low-level I/O hardware drivers in C that are easier to port
> Is anyone using this?
> Do many vendors support this yet?
>
> TIA
Reply by Marco●October 16, 20082008-10-16
A while back the ISO C group added to the C standard with TR18015 and
TR18037
<iohw.h>
to create low-level I/O hardware drivers in C that are easier to port
Is anyone using this?
Do many vendors support this yet?
TIA