From: splee@plexio.com (Stephen Lee)
To: linux-mtd@lists.infradead.org
Subject: mtd devices inaccessible
Date: 31 Mar 2003 08:31:24 -0800 [thread overview]
Message-ID: <1049128283.23625.196.camel@ralph.plexio.private> (raw)
In-Reply-To: <3E88683E.65177484@thales-e-transactions.com>
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"?
Stephen
On Mon, 2003-03-31 at 08:09, Eric DEJONC wrote:
> Well, good advice, the menu seems to have been updated,
> But mtdlink.o is still required at the end of compilation:
> arm-linux-ld:cannot open drivers/mtd/mtdlink.o
> Is this the mtd driver or can I remove it from the makefile?
>
>
>
> Stephen Lee a ?crit :
>
> > On Mon, 2003-03-31 at 06:27, Eric DEJONC wrote:
> > > I'm sorry to ask so many question but,
> > > I hadn't made a clean, that's why I got a stange error, but now, I can't
> > > compile the new kernel:
> > > missing mtdlink.o
> > > I had to modify the makefile of the drivers/mtd and remove the
> > > ifeq($below25),y) but I have a 2.5.6.2 kernel.
> > >
> > If you haven't done so, copy .config somewhere safe, run "make
> > mrproper", copy .config back and then rerun "make menuconfig" and the
> > rest of the steps to compile the kernel.
> >
> > Stephen
> >
> > ______________________________________________________
> > Linux MTD discussion mailing list
> > http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2003-03-31 16:31 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 [this message]
2003-03-31 16:56 ` Jörn Engel
2003-04-01 8:08 ` Eric DEJONC
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=1049128283.23625.196.camel@ralph.plexio.private \
--to=splee@plexio.com \
--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