From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: Re: xip changes between 2.6.11 and 20050530?
Date: Fri, 29 Jul 2005 08:50:12 +0200 [thread overview]
Message-ID: <20050729065012.GA8186@ku-gbr.de> (raw)
In-Reply-To: <42E920CC.2020105@mvista.com>
Am 2005-07-28 11:15 -0700 schrieb Todd Poynor:
> >Hm.. funny. Beside the trouble with my toolchains the working one
> >creates definately only a bootable xipuImage if CONFIG_FPE_NWFPE is
> >enabled. I wonder myself, why...
>
> Dunno about that option, but check the assembly code generated for the
> xip_* routines to see if any functions are called that are not marked
> __xipram? If so, linux may be attempting to execute from flash memory
Ok, I can check that.
To be sure:
Any xip_* function only calls functions marked __xipram (which are
located in RAM then hopefully also) and only __xipram marked functions
call functions located still in flash?
> while the flash is not in the proper (read array or whatever) state.
Something like that seems to habben, indeed...
Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next prev parent reply other threads:[~2005-07-29 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 14:45 xip changes between 2.6.11 and 20050530? Konstantin Kletschke
2005-07-06 16:44 ` Todd Poynor
2005-07-07 8:22 ` Konstantin Kletschke
2005-07-07 12:33 ` Konstantin Kletschke
2005-07-28 12:17 ` Konstantin Kletschke
2005-07-28 12:39 ` Konstantin Kletschke
2005-07-28 15:01 ` Nicolas Pitre
2005-07-28 18:07 ` Konstantin Kletschke
2005-07-28 18:15 ` Todd Poynor
2005-07-29 6:50 ` Konstantin Kletschke [this message]
2005-07-29 20:02 ` Todd Poynor
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=20050729065012.GA8186@ku-gbr.de \
--to=lists@ku-gbr.de \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.