public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: m.neiger@synergie-inf.com, manningc2@actrix.gen.nz,
	"'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: 16 NANDS
Date: Wed, 08 Jan 2003 23:03:11 +0100	[thread overview]
Message-ID: <200301082303.11643.tglx@linutronix.de> (raw)
In-Reply-To: <515CABE7496FD111AA3300201829FCBE3552E0@archie.gsi.synergie-inf.com>

On Wednesday 08 January 2003 22:23, Marc Neiger wrote:
> Hi Thomas,
>
> > I have the framework ready to support different buswidths.
>
> It's dangerous talking to you, guys, one gets easily caught in the
> maelstrom ;-)
>
> I'll gladly put my share back into the GPLd world, however my timeframe for
> the current project is very tight; everything, board, embedded linux and
> application should be working in less than 2 months.....
> Moreover, although I, and my colleagues, are experienced programmers, both
> in embedded and win32, I booted my first Linux about 6 weeks ago....
>
> The project shall be using a customly developped board using AMD Alchemy
> AU1000 (MIPS4Kc) processor. The board is planned to support both 8 and
> 16bits NAND flash, an EPLD shall, among other task, take care of data bus
> bits reordering (8 and 16 bits NANDS are pin out compatible except for the
> bit order). After reading some msg on this list, we already doubt about the
> ease of mounting a root JFFS2 filesystem.
It's really no big deal to mount a root fs with JFFS2 on NAND FLASH (8 bit 
buswidth). It works right out of the box, if you take the preliminaries into 
concern (see http://www.linux-mtd.infradead.org/tech/nand.html)
It is used in production systems.

> I'll have a look at the framework, then if I have some "time" and I feel
> comfortable with your code, I'll try to finish it, and we'll test it on our
> first board version. Otherwise, and it seems more likely, after the project
> is delivered and we have some experience on Linux, including kernel
> development since we are to write a driver for this very specific hardware,
> I'll get more seriously hands on the code but without having a very short
> deadline in front of me.
If your deadline is so tight and your capacities are so restricted, you could 
consider to sponsor one of the volunteer experts. This would speed up 
development rapidly. :)

> I already do much non computer related volunteer work and can not afford to
> take on my "free" time anymore.
See above. :)

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2003-01-08 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 21:23 16 NANDS Marc Neiger
2003-01-08 22:03 ` Thomas Gleixner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 22:42 Marc Neiger
2003-01-06 23:03 ` Charles Manning
2003-01-07 19:04   ` Thomas Gleixner
2003-01-08  8:14     ` David Woodhouse
2003-01-08 20:23       ` Thomas Gleixner
2003-01-03 10:27 Marc Neiger
2003-01-06 21:15 ` Charles Manning

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=200301082303.11643.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=m.neiger@synergie-inf.com \
    --cc=manningc2@actrix.gen.nz \
    /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