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/redboot/current ChangeLog cdl/re ...
Date: Tue, 11 Nov 2008 04:32:00 -0000	[thread overview]
Message-ID: <20081111043211.13336.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/ecos
Module name:	ecos
Changes by:	jlarmour@sourceware.org	2008-11-11 04:32:11

Modified files:
	packages/redboot/current: ChangeLog 
	packages/redboot/current/cdl: redboot.cdl 
	packages/redboot/current/include: fis.h flash_config.h redboot.h 
	packages/redboot/current/include/net: net.h 
	packages/redboot/current/src: fconfig.c io.c load.c main.c 
	                              parse.c xyzModem.c 
	packages/redboot/current/src/fs: e2fs.c 
	packages/redboot/current/src/net: net_io.c 

Log message:
	* src/fconfig.c, src/flash.c, src/io.c, src/load.c, src/main.c,
	src/xyzModem.c, include/redboot.h: more signed vs. unsigned char
	issues.
	
	* src/fs/e2fs.c (e2fs_mount): Avoid compiler strict aliasing
	problem.
	
	* include/fis.h (struct fis_image_desc): Make fis name be
	signed char to reduce warnings.
	* include/flash_config.h (struct _config): Make config_data
	be signed char to reduce warnings.
	* include/redboot.h: mon_write_char and mon_read_char_with_timeout
	take unsigned char, to reduce warnings.
	* src/parse.c: Add const to err_printf format.
	* src/fconfig.c: Many signed/unsigned warning cleanups.
	* src/io.c: Ditto.
	* src/xyzModem.c: Ditto.
	* src/load.c: Ditto.
	* src/flash.c: Ditto.
	
	* src/fconfig.c (flash_write_config): Warning cleanup.
	* src/net/net_io.c (do_ip_addr): Warning cleanup.
	* src/flash.c (fis_create): Warning cleanup.
	
	* include/net/net.h: Include redboot.h for tick functions.
	
	* include/net/net.h: Pull tick functions into redboot.h as they
	are used more widely than the net stack.
	* include/redboot.h: Declare tick functions.
	* src/main.c (cyg_start): Correctly compute workspace_end so it
	works even on high RAM values [bug #1000202].
	Don't use workspace_end directly for context init - it gets
	modified.
	(do_go): Don't use workspace_end directly for context init -
	it gets	modified.


             reply	other threads:[~2008-11-11  4:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11  4:32 jlarmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-03-06 16:45 grante
2011-12-02 18:31 jld
2008-11-18  1:02 jlarmour
2007-06-04 20:31 asl
2006-12-19  3:11 jlarmour
2006-11-30 17:03 asl
2006-09-06 14:26 asl
2006-05-09 15:52 gthomas
2006-02-25 14:21 asl
2005-09-08 12:14 gthomas
2005-09-03 13:35 asl
2005-04-21 18:08 asl
2004-11-09 19:12 asl
2004-10-13 21:22 asl
2004-09-01 21:21 msalter
2004-08-21 12:43 asl
2004-08-16  8:35 asl
2004-02-24 23:09 gthomas
2004-02-11 13:40 jlarmour
2004-02-04 15:44 gthomas
2003-12-08 15:37 gthomas
2003-12-02 14:40 gthomas
2003-11-01  9:08 gthomas
2003-10-15 15:52 gthomas
2003-10-11 21:22 gthomas
2003-10-02 20:13 gthomas
2003-09-22 17:35 gthomas
2003-09-20 14:35 gthomas
2003-08-19 17:23 gthomas
2003-07-01 16:25 msalter
2003-05-20 18:43 msalter
2003-03-28 13:49 gthomas
2003-02-24 14:32 jlarmour
2003-02-14  2:49 jlarmour
2002-08-24  4:34 gthomas
2002-08-24  4:20 gthomas
2002-08-12  0:54 asl
2002-08-06  7:29 gthomas
2002-07-09 13:23 gthomas
2002-07-01 13:55 gthomas

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=20081111043211.13336.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).