Interface between a C library and board support package

[Bilgehan.Balban@gmail.com]

Hi,

A simple question - it's not completely clear for me the interface
between a generic C library (such as glib or newlib) and a board
support package that implements it.

I've looked at newlib source code, and it is clear how it is done for
syscalls such as sys_open, sys_read, sys_write, the bsp supplies the
corresponding _open _read _write etc. in it's own implementation.

But how about malloc or printf? Could you briefly explain main points
of entry between a bsp and a C library in general?

Thanks,
Bahadir

[Jack Klein]

Re: Interface between a C library and board support package

On 18 Aug 2005 08:28:23 -0700, Bilgehan.Balban @gmail.com wrote in
comp.lang.c:
[color=blue]
> Hi,
>
> A simple question - it's not completely clear for me the interface
> between a generic C library (such as glib or newlib) and a board
> support package that implements it.[/color]

The C language does not define any interface between the standard C
library and any operating system, BSP, BIOS, or anything else. It
defines an abstract API with defined properties and does not even
specify how it is implemented at that API level, let alone levels
beyond that.
[color=blue]
> I've looked at newlib source code, and it is clear how it is done for
> syscalls such as sys_open, sys_read, sys_write, the bsp supplies the
> corresponding _open _read _write etc. in it's own implementation.[/color]

This level of "under the hood" detail is actually off-topic here,
because it is not defined by the language and much of it can't be
implemented in standard C.
[color=blue]
> But how about malloc or printf? Could you briefly explain main points
> of entry between a bsp and a C library in general?[/color]

Actually, no we can't, not here. The places you want to ask about
this are groups like news:comp.arch. embedded, support groups for your
particular compiler, such as news:gnu.*, support groups for your
particular OS, if you use one (news:comp.os.l inux.embedded if you are
using Linux in an embedded system, which is becoming popular these
days), and finally support groups for your particular embedded
processor, if there are any, such as for example news:comp.sys.a rm.

The C language literally does not specify how the library interfaces
to anything else, that is entirely up to the library provider.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.l earn.c-c++

http://www.contrib.andrew.cmu.edu/~ajo/docs/FAQ-acllc.html