public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Vikram Mehta" <vm6580@hotmail.com>
To: "mtd" <linux-mtd@lists.infradead.org>
Cc: uclinux-dev@uclinux.org
Subject: uCdimm 68VZ328  JFFS2 Questions
Date: Mon, 2 Jun 2003 17:25:43 -0700	[thread overview]
Message-ID: <Law14-OE536PDT89CLh0002e430@hotmail.com> (raw)

Hi folks,

A few questions
1.) I am using uCdimm 68VZ328 with AM29DL323GB flash chip
NOw I am on CYGWIN and am using Patrice KADIONIK guide HOW TO USE MTD/JFFS2
UNDER µClinux

I don't know If my chip is 2 MB or 4MB and nothing else abt it.

My questions are

1.) by following his guide ... I am making two partions.. as he does .... do
I risk erasing the bootloader. Wha precautions can I take not to ersae the
bootloader. Any ideas.

2.) Earlier one was  a silly but important  question, The makefile in
mtd-utils compliles files with 2 compilers... Onewith m68k-elf-gcc and other
with gcc. Now on my machine ( I guess due to bein gon CYGWIN) gcc build
doesnot work for all files and I get linker errors. So I hv removed gcc
build parts from the makefile. How does that affect the working of the
tools, kernels etc.

3.) Mr David Woodhouse was kind enough to answer me saying that MTD CVS
utils/makefile doenot contain any gcc build options. So Can someone send me
this makefile... I tried using the CVS but couldnot ..... I am trying but
still

4.) Can someone tell me from where can I read in detail about the
significance of changes Mentioned in  vendors/.../Makefile
DEVICES = \
tty,c,5,0 console,c,5,1 cua0,c,5,64 cua1,c,5,65 \

mtd0,c,90,0 mtd1,c,90,2 mdt2,c,90,4 mtd3,c,90,6 \

mtd4,c,90,8 mtd5,c,90,10 mtd6,c,90,12 mtd7,c,90,14 \

mtdblock0,b,31,0 mtdblock1,b,31,1 mtdblock2,b,31,2 mtdblock3,b,31,3 \

In the guide..
Thanx and Regrds

Vikram

             reply	other threads:[~2003-06-02 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03  0:25 Vikram Mehta [this message]
2003-06-03  1:48 ` [uClinux-dev] uCdimm 68VZ328 JFFS2 Questions Greg Ungerer

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=Law14-OE536PDT89CLh0002e430@hotmail.com \
    --to=vm6580@hotmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=uclinux-dev@uclinux.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