From: David Woodhouse <dwmw2@infradead.org>
To: Juan Gonzo <kayemmess@yahoo.ca>
Cc: MTD Mailing List <mtd@infradead.org>
Subject: Re: using MTD with 2.2.14
Date: Fri, 30 Jun 2000 08:47:50 +0100 [thread overview]
Message-ID: <29179.962351270@cygnus.co.uk> (raw)
In-Reply-To: <20000629222128.18411.qmail@web5304.mail.yahoo.com>
kayemmess@yahoo.ca said:
> Our group has a target board consisting of an ARM processor and Intel
> Strataflash with an embedded Linux OS running kernel 2.2.14.
I also have a target board consisting of an ARM processor and Intel
Strataflash with an embedded Linux OS running kernel 2.2.14.
> ...should switch to 2.2.16. Currently this ins't possible for our
> project, so will MTD (JFFS) work properly for me with 2.2.14?
I'd be surprised if it doesn't - my current code isn't being tested on
anything _but_ 2.2.14/StrongARM.
> If I apply 'mtd-patch-2.2.16', I can enable these with 'make
> oldconfig', but am I not supposed to use this patch since it is for
> 2.2.16?
That's fine - you can use that and it _should_ apply cleanly.
> undefined reference to `put_module_symbol'
> But these functions are in the 2.2.16 patch, aren't
> they? What am I doing wrong?
They're definitely in the patch. Did it fail to apply them for some reason?
The {get,put}_module_symbol() patch is also available separately as
mtd/patches/put_module_symbol-2.2.1x.patch. Try applying that and see what
happens.
It's easy enough to do it by hand. Add __MOD_INC_USE_COUNT(mp) in the right
place in the existing get_module_symbol() routine, and add the new
put_module_symbol() routine from the patch. Then add the prototype to
module.h and an export entry to ksyms.c
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2000-06-30 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-29 22:21 using MTD with 2.2.14 Juan Gonzo
2000-06-30 7:47 ` David Woodhouse [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=29179.962351270@cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=kayemmess@yahoo.ca \
--cc=mtd@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