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

On Dec 11, 2007 2:51 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> On Tue, Dec 11, 2007 at 11:09:40AM +0100, ?yvind Harboe wrote:
> > On Dec 11, 2007 11:03 AM, Andrew Lunn <andrew@lunn.ch> wrote:
> > >
> > > > I mainly want the busted check in flash_erase() to be removed.
> > > > ASSERT's are probably fine.
> > >
>
> What is actually wrong with this check?

I have no idea what this check is supposed to do.

If a valid range is passed in, it is a no-operation, otherwise it does
something mysterious
that looks just wrong to me.

I'm afraid all I can conclude is that it should be deleted as plain
wrong/unused. The
fact that it is harmless for valid ranges has allowed it to survive to date,
that's the antrophic principle for you I guess.

Someone else would have to speak up for it.

It would be a shame if plain wrong harmless code that nobody understands
could never be deleted from eCos :-)

> I don't want to remove this until i fully understand what is causing
> your problem and how this code is wrong. Please could you explain what
> you are seeing.

The problem is that I relied on flash_erase() to return an error upon illegal
address range. When I tested with an illegal address range,
flash_erase() did not
return an error. Upon inspecting the code, I saw something that looked
like it is *trying* to check the address, but I have found no explanation
for that code, so I see a couple of alternatives:

- if nobody understands this code, delete it after a week or two to
wait for someone to
speak up and see what happens. Probably nothing.
- keep this code forever as it is harmless(with valid addresses)
nobody will be hurt by it.
- add address check to flash_erase() & program and return error message


-- 
Ø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:13 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 [this message]
2007-12-11 14:28             ` Gary Thomas
2007-12-11 14:38               ` Øyvind Harboe

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=c09652430712110611k73d3e335j468fae41bd341a10@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@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).