public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-mtd@lists.infradead.org
Subject: XIP on 2.6.13 broken
Date: Mon, 5 Sep 2005 12:15:07 +0200	[thread overview]
Message-ID: <20050905101502.GA21861@synertronixx3> (raw)

Hi People!

I recently ported my code running perfect on 2.6.12 to 2.6.13.
I use an Intel K3 Flash device (cfi_cmdset_0001.c).

However, the recent XIP on 2.6.13 is very unstable. It mostly freezes
when the bootup init.d processes start to read/write the / partition.
Sometimes it comes to live but for example usb-storage gets an
garbaged read (ls -la) from an mounted usb-device.
linux-wlan-ng is not able to issue one succesful ping command.
The error seemed to be either in the usb host-controller driver or in
the linux-wlan-ng package so I searched the error there for a couple
of days. 

But I found out, the system is working perfect when I disable
xip!

Well, I think I followed the change from the #ifdef mess in
include/linux/mtd/xip.h to asm/arch/mtd-xip.h correct...

Here it is:

#ifndef __ARCH_IMX_MTD_XIP_H__
#define __ARCH_IMX_MTD_XIP_H__

#include <asm/arch/imx-regs.h>

#define xip_irqpending()        ( IMX_NIPNDH || IMX_NIPNDL )

#define xip_currtime()          (IMX_TCN(IMX_TIM1_BASE))
#define xip_elapsed_since(x)    (signed)((IMX_TCN(IMX_TIM1_BASE) -(x)) * 31)

#define xip_iprefetch() asm volatile (".rep 8; nop; .endr");

#define xip_cpu_idle()  asm volatile ("mcr p14, 0, %0, c7, c0, 0" :: "r" (1))

#warning KGK 

#endif /* __ARCH_IMX_MTD_XIP_H__ */


Hm, well, where could I start to search for a significant change?

Regards, Konsti

-- 
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E  A080 1E69 3FDA EF62 FCEF

             reply	other threads:[~2005-09-05 10:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05 10:15 Konstantin Kletschke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-06 12:44 XIP on 2.6.13 broken Konstantin Kletschke

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=20050905101502.GA21861@synertronixx3 \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox