From: Zhang Haitao <zhanght@netpower.com.cn>
To: David Kesselring <dkesselr@mmc.atmel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: kernel modules
Date: Tue, 21 Oct 2003 05:00:33 +0800 [thread overview]
Message-ID: <3F944CF1.2010608@netpower.com.cn> (raw)
In-Reply-To: <20031020183922.GD15997@linux-mips.org>
On Mon, Oct 20, Ralf Baechle wrote:
>
>
> You're _not_ using the same options as the kernel's Makefile does for
> building modules.
>
> Ralf
>
Hi, modules compiled using these parameters are working on my 2.4.21 SMP
kernel:
CFLAGS="-I .../include/asm/gcc -D__KERNEL__ -I.../include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
-fno-strict-aliasing -fno-common -G 0 -mno-abicalls -fno-pic -mcpu=XX
-mips2 -Wa,--trap -pipe -DMODULE -mlong-calls"
XX = your chip style
Zhang Haitao
next prev parent reply other threads:[~2003-10-20 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 14:32 kernel modules David Kesselring
2003-10-20 15:48 ` David Daney
2003-10-20 18:13 ` David Daney
2003-10-20 18:39 ` Ralf Baechle
2003-10-20 21:00 ` Zhang Haitao [this message]
2003-10-21 12:34 ` David Kesselring
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=3F944CF1.2010608@netpower.com.cn \
--to=zhanght@netpower.com.cn \
--cc=dkesselr@mmc.atmel.com \
--cc=linux-mips@linux-mips.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