From: Thomas Gleixner <tglx@linutronix.de>
To: Vishal <vishal@laser5.co.jp>
Cc: linux-mtd@lists.infradead.org
Subject: Re: help: bootloader for loading kernel from mtdblock device on flash........
Date: Tue, 04 Feb 2003 12:51:49 +0100 [thread overview]
Message-ID: <200302041251.50037.tglx@linutronix.de> (raw)
In-Reply-To: <3E3F9DA6.60607@laser5.co.jp>
On Tuesday 04 February 2003 12:01, Vishal wrote:
> let me explain the problem in more detail here
> the thing is that currently i have a boot loader code which reads from a
> char device /dev/mtd/ on NAND where only the kernel image is placed. Bad
> blocks on the /dev/mtd device can cause problems loading the kernel
> which is why i was asked to move the kernel to /dev/mtdblock (which is
> runs a JFFS), and change the boot loader accordingly.
> Thats the reson why i was thinking in terms of using a char driver.
> As per your suggestion of using YAFFS, what kind of effort would it
> require to get going on this system where JFFS had been completely
> cutomised? will it require any changes for the kind of flash(samsung
> K9F2808U0B) we are using?
No changes, just create well sized partitions.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2003-02-04 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 11:24 help: bootloader for loading kernel from mtdblock device on flash Vishal
2003-02-03 12:47 ` Holger Schurig
2003-02-03 17:52 ` Charles Manning
2003-02-03 19:04 ` Thomas Gleixner
2003-02-04 3:21 ` Vishal
2003-02-04 7:35 ` Thomas Gleixner
2003-02-04 9:30 ` Vishal
2003-02-04 10:38 ` Thomas Gleixner
2003-02-04 11:01 ` Vishal
2003-02-04 11:51 ` Thomas Gleixner [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=200302041251.50037.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=vishal@laser5.co.jp \
/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