This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: J3 flash lockbits across reset

From: Andrew Lunn <andrew at lunn dot ch>
To: alfred hitch <alfred dot hitch at gmail dot com>
Cc: ecos-discuss at sources dot redhat dot com
Date: Thu, 12 Jan 2006 10:40:31 +0100
Subject: Re: [ECOS] J3 flash lockbits across reset
References: <29f916510601120033m64d536e7geeede5747f2ad952@mail.gmail.com> <20060112084449.GT5620@lunn.ch> <29f916510601120136v36a71d2dj21aaaeb56a37a834@mail.gmail.com>

On Thu, Jan 12, 2006 at 04:36:52AM -0500, alfred hitch wrote:
> 3) Going to RAM is anyways needed.
> My ques. was does one needs to ensure that there are no process which
> issue a read / write to flash in parallel at the time 1st lock command
> was issued.

That is why i said disable interrupts. Apart from a NMI nothing else
can happen.

        Andrew

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

References:
- J3 flash lockbits across reset
  - From: alfred hitch
- Re: J3 flash lockbits across reset
  - From: Andrew Lunn
- Re: J3 flash lockbits across reset
  - From: alfred hitch

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]