From: Jonathan Larmour <jifl@eCosCentric.com>
To: Bart Veer <bartv@ecoscentric.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: eCos 3.0 beta 1 punch list #2
Date: Tue, 17 Feb 2009 09:18:00 -0000 [thread overview]
Message-ID: <499A80DA.5030403@eCosCentric.com> (raw)
In-Reply-To: <499A12DD.4060609@eCosCentric.com>
[ker-snip]
Sorry I sounded a bit harsh there. It was late and I was tired. But I do
believe that a .0 release should go out with an API which will work in future.
More constructively, until I know what the "messy" bit is, I suggest adding:
externC cyg_flash_printf *cyg_flash_set_printf( const cyg_flashaddr_t
base, cyg_flash_printf *pf);
which associates the printf function of flash at base 'base' with function
'pf', returning its previous setting. There would also be:
#define CYG_FLASH_SET_PRINTF_ALL ((cyg_flashaddr_t)-1);
which is used to set all devices' printf functions (and always return NULL).
We can instantly deprecate use of cyg_flash_init with non-NULL argument.
And if the messiness is too much to deal with after all, we can continue
with cyg_flash_init, and in future it would be more or less #defined to
cyg_flash_set_printf.
Jifl
--
*See us at Embedded World 2009, Nürnberg, Germany, 3-5 Mar, Stand 11-300*
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
next prev parent reply other threads:[~2009-02-17 9:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 9:07 John Dallaway
2009-02-13 19:56 ` Bart Veer
2009-02-17 1:29 ` Jonathan Larmour
2009-02-17 9:18 ` Jonathan Larmour [this message]
2009-02-17 9:34 ` Flash subsystem update [ was Re: eCos 3.0 beta 1 punch list #2 ] John Dallaway
2009-02-17 22:01 ` Flash subsystem update John Dallaway
2009-02-18 12:47 ` Bart Veer
2009-02-19 0:08 ` Jonathan Larmour
2009-02-19 11:50 ` Bart Veer
2009-02-19 14:40 ` John Dallaway
2009-02-19 15:13 ` Bart Veer
2009-02-19 20:53 ` Jonathan Larmour
2009-02-20 9:16 ` John Dallaway
2009-02-19 20:31 ` Jonathan Larmour
2009-02-20 12:55 ` Bart Veer
2009-02-20 21:22 ` Jonathan Larmour
2009-02-17 21:07 ` eCos 3.0 beta 1 punch list #2 Bart Veer
2009-02-17 23:10 ` Jonathan Larmour
2009-02-19 0:48 ` Jonathan Larmour
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=499A80DA.5030403@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=bartv@ecoscentric.com \
--cc=ecos-maintainers@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).