public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	 	"eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: Check for illegal address range in io/flash
Date: Tue, 11 Dec 2007 14:38:00 -0000	[thread overview]
Message-ID: <c09652430712110638v45bf3ab0k22a2c190368f7016@mail.gmail.com> (raw)
In-Reply-To: <475E9DCB.3080902@mlbassoc.com>

> As I read the code, the "check" you are talking about is only to make
> sure that the address [range] which gets printed makes sense.  There is
> similar code within the loop to handle the edge case where the FLASH
> region being erased buts up against the top of possible address space.

Gotit. I don't see the corresponding code in flash_program_buf().

The explanation above would be helpful in the code I think.

-- 
Øyvind Harboe
http://www.zylin.com - eCos ARM & FPGA  developer kit

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2007-12-11 14:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c09652430712110102x684bcd2apd276cb0ff287caac@mail.gmail.com>
     [not found] ` <20071211094252.GD30586@lunn.ch>
     [not found]   ` <c09652430712110149t4e157058r3a1a579c4330ac@mail.gmail.com>
     [not found]     ` <20071211100356.GF30586@lunn.ch>
     [not found]       ` <c09652430712110209t7fd2cab9va31087a52c7d2895@mail.gmail.com>
2007-12-11 13:51         ` Andrew Lunn
2007-12-11 14:13           ` Øyvind Harboe
2007-12-11 14:28             ` Gary Thomas
2007-12-11 14:38               ` Øyvind Harboe [this message]

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=c09652430712110638v45bf3ab0k22a2c190368f7016@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    /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).