This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: diag_printf
- From: "Gary D. Thomas" <gary dot thomas at mind dot be>
- To: Pete Barrie <peter dot barrie at cis dot strath dot ac dot uk>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: 05 Mar 2003 13:58:54 -0700
- Subject: Re: [ECOS] diag_printf
- References: <5.1.1.6.0.20030305205110.0376be40@pophost.cis.strath.ac.uk>
On Wed, 2003-03-05 at 13:53, Pete Barrie wrote:
> Can somebody tell me what the mutual exclusion issues are with diag_printf()
> I cannot find anything specific in the documentation.
What sort of issues are you thinking about?
'diag_printf()' is designed to be "straight to the hardware",
mainly used for diagnostic purposes. As such, it will access
the hardware directly, without any regard for other threads
or uses of the diagnostic device. If you are using a serial
port that is also used for diag_printf(), then the diagnostic
purpose simply wins. Other uses of the same hardware are
possible, but they need to be cognizant of these facts.
--
.--------------------------------------------------------.
| Mind: Embedded Linux and eCos Development |
|--------------------------------------------------------|
| Gary Thomas email: gary dot thomas at mind dot be |
| Mind ( http://mind.be ) tel: +1 (970) 229-1963 |
| gpg: http://www.chez-thomas.org/gary/gpg_key.asc |
'--------------------------------------------------------'
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss