public inbox for ecos-cvs@sourceware.org
help / color / mirror / Atom feed
From: jlarmour@sourceware.org
To: ecos-cvs@ecos.sourceware.org
Subject: ecos/packages/io/flash/current ChangeLog doc/f ...
Date: Thu, 19 Feb 2009 00:14:00 -0000	[thread overview]
Message-ID: <20090219001426.1371.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/ecos
Module name:	ecos
Changes by:	jlarmour@sourceware.org	2009-02-19 00:14:26

Modified files:
	packages/io/flash/current: ChangeLog 
	packages/io/flash/current/doc: flash.sgml 
	packages/io/flash/current/include: flash.h 
	packages/io/flash/current/src: flash.c flashiodev.c 
	                               flashiodevlegacy.c legacy_api.c 
	                               legacy_dev.c 

Log message:
	* include/flash.h: Modest API change: cyg_flash_init() no longer
	takes a printf function argument. Instead two new API functions
	are available: cyg_flash_set_printf() and
	cyg_flash_set_global_printf().
	
	* src/flash.c (CHATTER): Don't attempt output if printf function
	is NULL.
	(cyg_flash_init): No longer takes printf arg.
	(cyg_flash_set_printf): New. Set per-device printf function, locking
	if needed.
	(cyg_flash_set_global_printf): New. Set printf function for all
	devices, locking if needed.
	
	* src/flashiodev.c (flashiodev_init): cyg_flash_init no longer takes
	printf arg, and we can leave global printf at default.
	* src/flashiodevlegacy.c (flashiodev_init): Ditto.
	
	* src/legacy_api.c (flash_init): cyg_flash_init no longer takes
	printf arg. So call cyg_flash_set_global_printf as well.
	
	* src/legacy_dev.c (legacy_flash_init): legacy drivers can't handle
	NULL printf function, so provide a dummy.
	
	* doc/flash.sgml: Document removal of printf functionality of
	cyg_flash_init() and document cyg_flash_set_printf() and
	cyg_flash_set_global_printf().


             reply	other threads:[~2009-02-19  0:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19  0:14 jlarmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-21 19:18 jld
2011-05-13  8:09 jld
2009-03-07 11:59 jld
2009-03-07 11:58 jld
2009-02-20 22:33 jlarmour
2009-02-20 22:06 jlarmour
2008-11-23  2:41 jlarmour
2004-09-05 20:13 msalter
2004-08-21 13:47 asl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090219001426.1371.qmail@sourceware.org \
    --to=jlarmour@sourceware.org \
    --cc=ecos-cvs@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).