public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: mtd <linux-mtd@lists.infradead.org>
Subject: Re: [uClinux-dev] uCdimm 68VZ328  JFFS2 Questions
Date: Tue, 03 Jun 2003 11:48:05 +1000	[thread overview]
Message-ID: <3EDBFE55.2040903@snapgear.com> (raw)
In-Reply-To: <Law14-OE536PDT89CLh0002e430@hotmail.com>

Hi Vikram,

Vikram Mehta wrote:
> 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
> 
[snip]
> 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.

 From your description I can tell you are referring the the uClinux-dist
user/mtd-utils/Makefile, which is different to what is contained in
the  MTD cvs Makefile.

The reason it is compiled with gcc in a complete uClinux build is
to generate the filesystem builer tools for running as part of the
build. So to build mkfs.jffs, mkfs.jffs2, etc. These will be needed
on the host to construct a filesystem ready for loading onto the
real target.


> 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

If you are building uClinux-dist use what it contains.

If you are using the MTD tools on there own use the MTD CVS
code.


> 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 uClinux-dist build system this is the list of device
nodes that will be created in the target filesystem. Format is
simple:

    <node-name>,<b=block/c=char>,<major>,<minor>

They are never created as nodes on the host system, only in the
target root filesystem (be in ROMfs, JFFS, JFFS2, EXT2, whatever).

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
SnapGear Pty Ltd                            PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

      reply	other threads:[~2003-06-03  1:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03  0:25 uCdimm 68VZ328 JFFS2 Questions Vikram Mehta
2003-06-03  1:48 ` Greg Ungerer [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=3EDBFE55.2040903@snapgear.com \
    --to=gerg@snapgear.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