public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Oliver Korpilla <okorpil@fh-landshut.de>
To: Oliver Korpilla <okorpil@fh-landshut.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: (interleaved chips) cfi_cmdset_0002 -> Kernel Panic
Date: Thu, 22 Apr 2004 18:09:55 +0200	[thread overview]
Message-ID: <4087EE53.2000608@fh-landshut.de> (raw)
In-Reply-To: <4087DC65.7010703@fh-landshut.de>

Hello

I patched a revision of MTD with version 1.93 (as suggested elsewhere) 
of this file (cfi_cmdset_0002.c) against the kernel. Configured fine, 
built fine (kernel.org 2.4.25), but did not autodetect the interleaved 
chip (as the newest snapshot fails to do as well).

So I guess if reverting would be an option, I still do not know where to 
revert to.

Any ideas?

Thanks in advance,
Oliver Korpilla

  reply	other threads:[~2004-04-22 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 14:53 (interleaved chips) cfi_cmdset_0002 -> Kernel Panic Oliver Korpilla
2004-04-22 16:09 ` Oliver Korpilla [this message]
2004-04-22 19:09   ` dkey
2004-04-22 19:17     ` Oliver Korpilla

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=4087EE53.2000608@fh-landshut.de \
    --to=okorpil@fh-landshut.de \
    --cc=linux-mtd@lists.infradead.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