From: Marcus Mikolaiczyk <m.mikolaiczyk@rac.de>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: Patching only NAND specific stuff possible?
Date: Thu, 12 May 2005 07:13:57 +0200 [thread overview]
Message-ID: <4282E615.9010502@rac.de> (raw)
In-Reply-To: <1115848017.22180.112.camel@tglx>
>>Considering the four Layers (jffs2,mtd,nand,hardware-drivers) it should
>>be possible onloy to 'update' the nand and hardware-drivers stuff.
>>Any objections to this?
>
>
> No, as long as you do not ask questions, why it doesnt work. :)
> The current nand driver needs the current mtd layer and JFFS2 from the
> last century will not work with those.
Thanks for this info. The NAND is a large page one with some extented
commands for large page devices. I have an older driver on the system so
the way is to upgrade this one to an appropriate one supporting the
large page nand with it's commands.
Marcus
prev parent reply other threads:[~2005-05-12 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 8:25 Patching only NAND specific stuff possible? Marcus Mikolaiczyk
2005-05-11 21:46 ` Thomas Gleixner
2005-05-12 5:13 ` Marcus Mikolaiczyk [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=4282E615.9010502@rac.de \
--to=m.mikolaiczyk@rac.de \
--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