public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Herman Oosthuysen" <Herman@WirelessNetworksInc.com>
To: "Steve Kranz" <skranz@ridgerun.com>,
	"David Woodhouse" <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>, <skranz@ridgerun.com>
Subject: Re: MTD/mtdblock.c uclinux 2.0.38?
Date: Wed, 11 Jul 2001 14:36:04 -0600	[thread overview]
Message-ID: <00e001c10a49$1b9933c0$1501a8c0@Herman> (raw)
In-Reply-To: 3B4CA966.D9B15BF8@ridgerun.com

Hmm, I found the same problems, so I bought a copy of Intel's VFM for $99 to
use instead.  It took 3 weeks to get the source code from Intel, but I now
finally have it.  It is only for use with Intel chips, though it is royalty
free.

----- Original Message -----
From: Steve Kranz <skranz@ridgerun.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: <linux-mtd@lists.infradead.org>; <skranz@ridgerun.com>
Sent: Wednesday, July 11, 2001 1:30 PM
Subject: Re: MTD/mtdblock.c uclinux 2.0.38?


> > uclinux 2.0.38 & MTD?
> > Should work. Probably doesn't. Give me individual
> > instances of places I broke the 2.0 compile, preferably
> > with patches, and we'll deal with it.
>
> Shown below are the problems I encountered when
> attempting to build the latest MTD tree for uclinux
> 2.0.38. For the moment I have suspended efforts to get
> this working under 2.0.38 and would be very interested
> if someone could provide a MTD version or patch that
> will work with that kernel. If so, please let me
> know. Thank you!  :-)
>
> Steve Kranz
> skranz@ridgerun.com
>
> ---------------------------
> My choosen config settings:
> ---------------------------
> CONFIG_MTD=y
> CONFIG_MTD_DEBUG=y
> CONFIG_MTD_DEBUG_VERBOSE=3
> CONFIG_MTD_CHAR=y
> CONFIG_NFTL=y
> CONFIG_NFTL_RW=y
> CONFIG_MTD_NAND=y
>
> ----------------
> Missing Headers:
> ----------------
> MTD depends on these headers which don't exist
> within the uclinux tree.
> linux/slab.h
> linux/spinlock.h
> linux/kmod.h
>
> ---------------
> Other Problems:
> ---------------
> include/linux/mtd/map.h line 65, generates error:
> "field `list' has incomplete type"
>
> Attempts to compile the MTD
> statements __MOD_INC_USE_COUNT() and __MOD_DEC_USE_COUNT()
> found in various locations with the MTD tree
> generate these compile errors:
> "structure has no member named `uc'"
> "structure has no member named `flags'"
>
> --------------
> Version Notes:
> --------------
> I downloaded via cvs.infradead.org on
> July 9, 2001. I placed it into my 2.0.38
> uclinux tree and then applied the MTD
> supplied patch mtd-uClinux-2.0.38.1pre7.patch.
>
>
> -----------
>
> David Woodhouse wrote:
>
> > skranz@ridgerun.com said:
> > > 1. Anybody know if instruction exist for installing MTD and nftl into
> > > an uclinux 2.0.38 tree?
> >
> > Should work. Probably doesn't. Give me individual instances of places I
> > broke the 2.0 compile, preferably with patches, and we'll deal with it.
> >
> > > 2. I'm interested in getting the SmartMedia slot of this arm7 board
> > > working for both read and write -- and I'd like the SmartMedia card to
> > > be readable/writable by a Windows machine too. Am I correct that this
> > > interoperability constraint will prevent me from using JFFS? I'm
> > > assuming that a vfat fs with MTD/nftl will do the trick for me. Yes,
> > > no?
> >
> > You need to implement the SmartMedia translation layer format. It looks
like
> > there's enough information on the Samsung web site to do that.
> >
> > > 3. I've been glancing at MTD code and didn't think I saw any logic to
> > > deal with the bad (unusable) blocks of a NAND flash device. Did I just
> > > miss it?
> >
> > Done in the SmartMedia translation layer, not in the underlying device
> > driver.
> >
> > --
> > dwmw2
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2001-07-11 20:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09 13:42 MTD/mtdblock.c uclinux 2.0.38? Steve Kranz
2001-07-11  9:11 ` David Woodhouse
2001-07-11 19:30   ` Steve Kranz
2001-07-11 20:36     ` Herman Oosthuysen [this message]
2001-07-11 22:28     ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2001-07-16 23:00 Mike Voytovich
2001-07-17  7:06 ` David Woodhouse
2001-07-17 23:02 Mike Voytovich
2001-07-18  6:16 ` David Woodhouse
2001-07-18  6:50 Mike Voytovich

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='00e001c10a49$1b9933c0$1501a8c0@Herman' \
    --to=herman@wirelessnetworksinc.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=skranz@ridgerun.com \
    /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