public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Eric DEJONC" <eric.dejonc@thales-e-transactions.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Stephen Lee <splee@plexio.com>
Cc: mtd <linux-mtd@lists.infradead.org>
Subject: Re: mtd devices inaccessible
Date: Tue, 01 Apr 2003 10:08:55 +0200	[thread overview]
Message-ID: <3E894916.926ACDC3@thales-e-transactions.com> (raw)
In-Reply-To: 20030331165610.GB19168@wohnheim.fh-wedel.de

Hi,
I think i have found the problem, the 2.5.59 kernel has been patched for mtd
suppoirt on trizeps. May be that's why I could'nt get mtd device work
properly on a 2.5.6.2 kernel.

Best regards,
Eric

Jörn Engel a écrit :

> On Mon, 31 March 2003 08:31:24 -0800, Stephen Lee wrote:
> >
> > I presume you meant a 2.5.62 kernel below. Could it be a bug in the mtd
> > subsystem with that developmental kernel? Are you using the MTD cvs
> > patches and if yes, do you really need them? Did you run "make dep"
> > before "make bzImage"?
>
> make dep is unnecessary with 2.5.recent.
>
> Jörn
>
> --
> Premature optimization is the root of all evil.
> -- Donald Knuth
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2003-04-02  8:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 14:27 mtd devices inaccessible Eric DEJONC
2003-03-31 15:24 ` Stephen Lee
2003-03-31 16:09   ` Eric DEJONC
2003-03-31 16:31     ` Stephen Lee
2003-03-31 16:56       ` Jörn Engel
2003-04-01  8:08         ` Eric DEJONC [this message]
2003-03-31 16:55     ` Jörn Engel

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=3E894916.926ACDC3@thales-e-transactions.com \
    --to=eric.dejonc@thales-e-transactions.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=splee@plexio.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