This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: diag_printf
- From: "Andy Simpkins" <andy dot simpkins at mindsail dot com>
- To: "Vinayak P Risbud" <vinayak at multitech dot co dot in>, "Jani Monoses" <jani at iv dot ro>
- Cc: "Ecos-Discuss" <ecos-discuss at sources dot redhat dot com>
- Date: Fri, 27 Sep 2002 14:04:08 +0100
- Subject: RE: [ECOS] diag_printf
on your board diag_printf should relate to hal_diag.c (this uses a fully
blocking serial driver)
where as the normal serial functions will end up being sent using
e7t_serial.c (with the serial port under interrupt control)
Andy
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Vinayak P
Risbud
Sent: 27 September 2002 13:49
To: Jani Monoses
Cc: Ecos-Discuss
Subject: Re: [ECOS] diag_printf
But, at the end..which function of serial driver is called
I am asking this because, there are two serial writes.
For e7t board,
One under /packages/hal/arm/e7t/current/src/hal_diag.c
another,
/packages/devs/serial/arm/e7t/current/src/e7t_serial.c
The main problem, I am facing is..I am not able to walk
through
lot of complicated macros...
If you can explain me bit in detail..or explain me..how
macros
can be read easily..I am thankful to you.
regards
Vinayak
Jani Monoses wrote:
> > Hi,
> > I am not able trace the diag_printf function.
> > Which function of my serial driver is called,
> > when, I execute diag_printf ?
> it eventually calls HAL_DIAG_WRITE_CHAR which is defined in each hal.
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss