From: nicola76@inwind.it (Nicola)
To: linux-mtd@lists.infradead.org
Subject: CFI/MTD weird problem
Date: 07 Feb 2003 18:03:24 +0100 [thread overview]
Message-ID: <1044637404.22176.37.camel@localhost.localdomain> (raw)
Booting a linux-2.4.19-rmk4-ds3 I get this weird problem:
1.Without MTD support module I get a good output to console until the
kernel prints out that there is no filesystem support. So my system's
printk works fine.
2.With MTD support module
The CFI probing is working correctly and detects QRY.
When I start tracing the code execution putting some printk into the
MTD/CFI code, I get a weird behavior where the console output is
corrupted BEFORE the calling of the MTD/CFI code, (see minicom log
below).
And I get out some '%' chars instead of the regular numerical values.
After some days debugging this problem I need a suggestion because I
have exhausted ideas about where to search.
TIA
next reply other threads:[~2003-02-07 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 17:03 Nicola [this message]
2003-02-07 17:15 ` CFI/MTD weird problem Graham Greene
2003-02-12 16:10 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2003-02-07 17:20 Nicola
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=1044637404.22176.37.camel@localhost.localdomain \
--to=nicola76@inwind.it \
--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