LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Antliff <David_Antliff@stratexnet.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Common Flash Interface v1.4 and MTD support in Linux-2.4.4 kernel
Date: Wed, 08 Feb 2006 11:46:05 +1300	[thread overview]
Message-ID: <1139352365.6285.6.camel@theoden.middle_earth> (raw)
In-Reply-To: <20060207210421.57015352659@atlas.denx.de>

On Tue, 2006-02-07 at 22:04 +0100, Wolfgang Denk wrote:
> In message <1139309578.32218.7.camel@yoda.jdub.homelinux.org> you wrote:
> >
> > > What would you suggest? Yes, I am happy for a 'quick fix' but if there
> > > isn't one or it's too risky I am willing to invest the time in doing it
> > > right.
> > 
> > 'quick fix' is to pull the changes from cfi_cmdset_0001.c in MTD CVS
> > back into your kernel.  But I'm not sure how quick that will be given
> > that your kernel is very very old.
> 
> It's not quick at all, and the  ancient  2.4.4  MTD  code  has  other
> problems  at  all.  Swithing to a newer kernel version is very likely
> less trouble.

Josh & Wolfgang, I appreciate your replies - thank you. 

FYI, we have decided to investigate writing a simple block device driver
for this device to get our development back on track with an eventual
goal of upgrading the kernel when time and resources permit. 

MTD is not crucial to our project, it just made a previous task easier
and this current one harder! :)

Thanks again,

David Antliff

  reply	other threads:[~2006-02-07 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07  3:33 Common Flash Interface v1.4 and MTD support in Linux-2.4.4 kernel David Antliff
2006-02-07 10:52 ` Josh Boyer
2006-02-07 21:04   ` Wolfgang Denk
2006-02-07 22:46     ` David Antliff [this message]
2006-02-09 11:04   ` David Woodhouse

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=1139352365.6285.6.camel@theoden.middle_earth \
    --to=david_antliff@stratexnet.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wd@denx.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