From: juan@hispafuentes.com (Juan Ramon Jimenez)
To: linux-mtd@lists.infradead.org
Subject: Problems with NAND support
Date: 06 Aug 2001 17:00:02 +0200 [thread overview]
Message-ID: <m34rrlfd3h.fsf@drkitkat.Hispafuentes.com> (raw)
--
Hi all
We are trying to compile a kernel with MTD support but we have
some problems to get it. We have probed with several kernel sources
(2.4.3, 2.4.6, 2.4.7) and with the same sources replacing the mtd
files with the cvs directory files from infredead.org. In both cases
we have the same results: We only can get a kernel image if we don't
enable NAND device support. The problem is that we really need it. Do
you know why?
Also we have seen that we _must_ set a value for 'physical start
address of flash mapping' But we have read in 'mtd-jffs-HOWTO.txt':
' If you leave the address blank (or just don't enable the advanced
options), the code will *auto probe*. This works quite well (at
least for me). Try it first.'
What's the problem then?
We have used gcc 2.96 and egcs 2.91.66 with a Red Hat 7.0 (kernel
2.2.17-8)
Any comment or solution will be welcome. Thanks
J
///
(@ @)
------------------------oOO----(_)----OOo-------------------------
- No comas todo lo que puedes, no gastes todo lo que tienes,
no creas todo lo que oigas, no digas todo lo que sabes.
- Proverbio chino.
------------------------------------------------------------------
¤º°°º¤ø,¸¸,ø¤º°°º¤ø,¸¸,ø¤º°`°º¤ø,¸
Juan Ramón Jiménez García
Hispafuentes
Tfno 91 4575330
jjimenez@aucland.com
juan@hispafuentes.com
¤º°°º¤ø,¸¸,ø¤º°°º¤ø,¸¸,ø¤º°`°º¤ø,¸
next reply other threads:[~2001-08-06 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 15:00 Juan Ramon Jimenez [this message]
2001-08-07 10:26 ` Problems with NAND support David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-08-07 15:13 James, Laura
2001-08-07 16:01 ` David Woodhouse
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=m34rrlfd3h.fsf@drkitkat.Hispafuentes.com \
--to=juan@hispafuentes.com \
--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