From: Jonathan Larmour <jlarmour@redhat.com>
To: Jesus Molina <chus@Glue.umd.edu>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] compiling safl.c
Date: Wed, 24 Jan 2001 15:11:00 -0000 [thread overview]
Message-ID: <3A6F610F.C57F5B27@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0101241625560.25604-100000@y.glue.umd.edu>
Jesus Molina wrote:
>
> Hello,
>
> I am working with a strongARM ebsa285 board. kernel version
> 2.4.0-test10.
> I have problems compiling the flash drivers. These are the
> problems.
>
> Trying to compile safl.c the pointed modversions.h was a "fake" saying
> #error Modules should never use kernel-headers system headers
> #error but headers from an appropriate kernel-source file.
> I chanded the -f option of teh Makefile to a copy of modversions.h in the
> sources.
>
> Also when compiling vm_offset was not found. It seems that in 2.4.0, The
> vm_offset member of the vm_area_struct definition (<linux/mm.h>) seems to
> have been replaced with vm_pgoff. I replaced this, and finally i get my .o
> driver, but with a lot of warnings. and an unresolved symbol safl-scan, so
> I cannot install the module. When compiling, the exact error is:
>
> In function 'init-module':
> safl.c:200: warning: impllicit declaration of function 'safl_scan'
>
> Anybody knows why this symbol is unresolved?
Yes, this module has not been updated for kernel 2.4.0 :-). Try
conditionalizing the init_module function in salf.c to only be present for
2.3 and up, i.e.
#ifdef LINUX_VERSION_CODE < 0x23000
int
init_module(void)
{
if (safl_debug)
printk(KERN_INFO "%s", version);
return safl_scan();
}
#else
module_init( safl_scan() )
#endif
If you do get it working, please try and send us all the changes you made!
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Un cheval, pas du glue. Pas du cheval, beaucoup du glue. || Opinions==mine
prev parent reply other threads:[~2001-01-24 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 13:34 Jesus Molina
2001-01-24 15:11 ` Jonathan Larmour [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=3A6F610F.C57F5B27@redhat.com \
--to=jlarmour@redhat.com \
--cc=chus@Glue.umd.edu \
--cc=ecos-discuss@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).