From: Nicolas Pouillon <nipo@ssji.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Patch !
Date: Mon, 4 Oct 2004 18:38:27 +0200 [thread overview]
Message-ID: <20041004183827.7bcc5071.nipo@ssji.net> (raw)
In-Reply-To: <1096877111.21297.208.camel@thomas>
[Mon, 04 Oct 2004 10:05:11 +0200]
Thomas Gleixner <tglx@linutronix.de> eut le bonheur d'écrire:
> If you can start something like a kernel or a repairtool via JTAG you
> should have access.
Hm, sould document more on JTAG ;)
> > > #define. The code runs on 2.4 too. See compatmac.h
> >
> > I'll have a look at it ;)
Ok, it does compile.
I still have problems like oops when accessing MTD (same than before).
error is "Unhandled fault: imprecise external abort (0xcf6) at
0x20800014", which seems a blur.
I cant understand why Xscale complains, but I saw this issue has been
addressed some times on arm-linux ML, without fix (at least not in same
threads)
> Is the chip configured for 16-bit interface mode ?
PXA boots of it and its BOOT_SEL is configured to "Asynchronous 16bit
ROM", elsewhere, in mem controller, it is configured as "16bit fast
flash or rom, non burst read". so I assume it is.
> If yes, there are more tweaks neccecary.
I can see some NAND_BUSWIDTH_16 options, but how can this be enabled at
probe time ?
--
Nipo <nipo@ssji.net>
Gnu-PGP: 1024D/1DBF658F
http://nipo.ssji.net/nipo.asc
next prev parent reply other threads:[~2004-10-04 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 13:46 Issues with a Doc Milplus Nicolas Pouillon
2004-10-01 13:57 ` David Woodhouse
2004-10-01 14:27 ` Nicolas Pouillon
2004-10-02 13:55 ` Patch ! Nicolas Pouillon
2004-10-02 20:42 ` Thomas Gleixner
2004-10-03 1:11 ` Nicolas Pouillon
[not found] ` <20041003030653.2e0452a7.nipo@ssji.net>
[not found] ` <1096768161.21297.129.camel@thomas>
2004-10-03 20:18 ` Nicolas Pouillon
2004-10-04 8:05 ` Thomas Gleixner
2004-10-04 16:38 ` Nicolas Pouillon [this message]
2004-10-04 17:59 ` Thomas Gleixner
2004-10-04 20:47 ` Nicolas Pouillon
2004-10-04 21:04 ` Thomas Gleixner
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=20041004183827.7bcc5071.nipo@ssji.net \
--to=nipo@ssji.net \
--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