From: David Woodhouse <dwmw2@infradead.org>
To: Livio Plos <livioplos@bigfoot.com>
Cc: mtd@infradead.org
Subject: Re: howto
Date: Thu, 04 Jan 2001 17:57:54 +0000 [thread overview]
Message-ID: <10818.978631074@redhat.com> (raw)
In-Reply-To: <3.0.6.32.20010104184851.0082a4e0@popmail.libero.it>
livioplos@bigfoot.com said:
> I'm trying to build a system with flash chips instead of an hard disk
> or a disk on module and this seems to be the most advanced project to
> help me doing this.
> Neverthless, it is not easy to begin understanding how to move
> between sources, configuration, modules...
Documentation is moving up the TODO list very slowly, as I get the code
closer to a state where I'm happy with it.
> Can I boot totally from flash without any other storage support?
Yes, as long as you have the flash mapped where the CPU startup vector
points, or the board's firmware has support for starting the Linux kernel
from flash (RedBoot does).
> Is there any howto or high level docs to configure and compile?
Drop the latest code from CVS on top of your 2.4 kernel tree. Enable all the
CFI stuff, enable CONFIG_MTD_PHYSMAP and set the address, size and bus width
for your flash mapping appropriately. Boot it and see what happens.
If you want to partition the flash, as most people do, you'll want to copy
one of the other 'map' drivers (eg. pnc2000.c) and change the numbers
accordingly.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-01-04 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 17:48 howto Livio Plos
2001-01-04 17:57 ` David Woodhouse [this message]
2001-01-04 19:31 ` mtdchar.c and vmalloc Alice Hennessy
2001-01-05 10:31 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 22:15 howto Michael Stumpf
2001-01-11 18:58 ` howto Bjorn Wesen
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=10818.978631074@redhat.com \
--to=dwmw2@infradead.org \
--cc=livioplos@bigfoot.com \
--cc=mtd@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