public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Vishal <vishal@laser5.co.jp>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: help: bootloader for loading kernel from mtdblock device on flash........
Date: Tue, 04 Feb 2003 18:30:59 +0900	[thread overview]
Message-ID: <3E3F8853.708@laser5.co.jp> (raw)
In-Reply-To: 200302040835.14667.tglx@linutronix.de

Thomas Gleixner wrote:

>On Tuesday 04 February 2003 04:21, Vishal wrote:
>
>>Its for an ARM7 core.
>>I have the block driver for the JFFS on NAND Flash ready. I have the
>>basic bootloader code. I was wondering whether i can do the proceed in
>>the following way :
>>1. take the read/verify  code from the JFFS block driver for NAND flash,
>>and put it in my bootloader code
>>2. The driver code that i copy will have a lot of kernel API calls...so
>>i need to incorporate those also into my driver.
>>3. finally use this functionality achieved to read a kernel.bin file
>>from the /dev/mtdblock device and load it.
>> or is there  any other workaroud?
>>
>Yep. copy your compressed kernel image in chunks of blocksize to your 
>NAND-FLASH. Reserve enough spare in the case you have bad blocks. 
>Provide a bad block aware read function and modify the decompressor in the 
>kernel to read the image via this function from NAND. 
>Then you don't need JFFS2 inside the bootloader. 
>Then your NAND-CHIP has to have min. 2 Partitions 
>1 for the kernel Image and 1 for the root-fs. You do not mount the partition, 
>where your kernel image is stored.
>
>

hmm....correct me if i am wrong but what you are saying is i have a char 
device /dev/mtd1 (right??) on which i store the kernel image. this 
partition will never be mounted. The kernel image is stored on this 
device in chunks of blocksize.
   Now while reading from this device on bootup, i read from the char 
device, and generate blocks of the known size in memory, carry out error 
checking and correction on each block. and when the whole of the kernel 
has been read, i run it...right?
Pardon me if i am wrong.

regards,
Vishal

  reply	other threads:[~2003-02-04  9:28 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 [this message]
2003-02-04 10:38         ` Thomas Gleixner
2003-02-04 11:01           ` Vishal
2003-02-04 11:51             ` Thomas Gleixner

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=3E3F8853.708@laser5.co.jp \
    --to=vishal@laser5.co.jp \
    --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