From: Simon Vogl <vogl@soft.uni-linz.ac.at>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Dan Merillat <harik.attar@gmail.com>,
Jayasri Sangu <JayasriS@aaesys.com>
Subject: Re: Intel P30 flash support MTD 2.4.16 kernel
Date: Sat, 27 May 2006 12:06:36 +0200 [thread overview]
Message-ID: <447824AC.8080501@soft.uni-linz.ac.at> (raw)
In-Reply-To: <1148719386.5239.125.camel@localhost.localdomain>
Thomas,
>>I found out this minute that this could apply to my pxa271 core (with
>>on-chip p30 flash!)
>>as well - it reports the sim.op. bit, while the data sheet says no.
>>Could you tell me what your
>>symptoms were, and your cure (a code snippet, preferrably)?
>>
>>
>
>The real cure is to replace the chips by working ones. The hack is to
>
>
I would love to do that, but the flash is wire-bonded to the processor
in a single package -
My nano-manipulators are on repair at the momen ;)
>mask out the simultaneous ops bit when reading the CFI features.
>
>
>
Tried that, but did not cure the whole problem: The chip reports read
errors when accessing certain
addresses (above 0x1000000, i get that ominous 0x00080 reads...). I
recieved another sample board,
will try if this problem persists (as a side note: u-boot can access
the chip perfectly well... )
Simon
> tglx
>
>
prev parent reply other threads:[~2006-05-27 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 22:56 Intel P30 flash support MTD 2.4.16 kernel Jayasri Sangu
2006-05-16 23:32 ` David Woodhouse
2006-05-17 21:50 ` Dan Merillat
2006-05-20 8:35 ` Simon Vogl
2006-05-27 8:43 ` Thomas Gleixner
2006-05-27 10:06 ` Simon Vogl [this message]
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=447824AC.8080501@soft.uni-linz.ac.at \
--to=vogl@soft.uni-linz.ac.at \
--cc=JayasriS@aaesys.com \
--cc=dwmw2@infradead.org \
--cc=harik.attar@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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