From: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
To: Avik Sil <savik@zilog.com>
Cc: Nicolas Pitre <nico@cam.org>, linux-mtd@lists.infradead.org
Subject: Re: MTD XIP related issue
Date: Fri, 14 Nov 2008 14:42:53 +0200 [thread overview]
Message-ID: <491D724D.2030804@teltonika.lt> (raw)
In-Reply-To: <130F820E6D339446BB9EEC7FAF40A06DDEDF4B@mailziel.zilog.org>
Avik Sil wrote:
> While porting Linux kernel 2.6.26 on an ARM922T based custom board for
> XIP kernel, I came across the following bug report during boot-up:
Had the same problem. See my comments on your config file
[...]
> My kernel configuration is:
[...]
> #
>
> # RAM/ROM/Flash chip drivers
>
> #
>
> CONFIG_MTD_CFI=y
>
> # CONFIG_MTD_JEDECPROBE is not set
>
> CONFIG_MTD_GEN_PROBE=y
>
> # CONFIG_MTD_CFI_ADV_OPTIONS is not set
>
> CONFIG_MTD_MAP_BANK_WIDTH_1=y
>
> CONFIG_MTD_MAP_BANK_WIDTH_2=y
>
> CONFIG_MTD_MAP_BANK_WIDTH_4=y
Select only the supported BANK_WIDTH.
The problem is that if multiple bank widths are selected, then in code which is placed
in RAM for XIP to work appears reference to __udivsi3(if I remember correctly) and
this function is on FLASH and FLASH at that moment is inaccessible.
Sometimes it works because this function is already cached by CPU.
Nicolas: I think there should be some way to work around this... If not maybe we should
add compile #error if multiple bank widths and XIP are selected...
> # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set
>
> # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set
>
> # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set
>
> CONFIG_MTD_CFI_I1=y
>
> CONFIG_MTD_CFI_I2=y
Don't remember, but this may have the same effect also.
> # CONFIG_MTD_CFI_I4 is not set
>
> # CONFIG_MTD_CFI_I8 is not set
>
> # CONFIG_MTD_CFI_INTELEXT is not set
>
> CONFIG_MTD_CFI_AMDSTD=y
>
> # CONFIG_MTD_CFI_STAA is not set
>
> CONFIG_MTD_CFI_UTIL=y
>
> # CONFIG_MTD_RAM is not set
>
> # CONFIG_MTD_ROM is not set
>
> # CONFIG_MTD_ABSENT is not set
>
> CONFIG_MTD_XIP=y
next prev parent reply other threads:[~2008-11-14 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 14:08 MTD XIP related issue Avik Sil
2008-11-14 12:42 ` Paulius Zaleckas [this message]
2008-11-17 9:26 ` Avik Sil
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=491D724D.2030804@teltonika.lt \
--to=paulius.zaleckas@teltonika.lt \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.org \
--cc=savik@zilog.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