From: 广星 <guangxing@ict.ac.cn>
To: linux-mips@linux-mips.org <linux-mips@linux-mips.org>
Cc: angela <jhyang@ict.ac.cn>, 谢博士 <xie@ict.ac.cn>
Subject: Some Question about the kernel module on MIPS64
Date: Thu, 11 Sep 2003 10:13:58 +0800 [thread overview]
Message-ID: <20030911021338Z8225363-1272+5279@linux-mips.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1602 bytes --]
Hi, everyone!
I am a newbie on doing some development on MIPS(of course it is the linux make me can touch it without any hesitation).There are two questions as follow hoping your enthusiastic answers.
1) I want to know if the linux for mips64 support the customer's kernel module .if yes, is there any modutils i can use?And how can i get it.
2) I have written a simplest simplest kernel module for linux for mips64 (only the init()and cleanup() we can see,and we do nothing.) and with the crossing compiling tool it is ok.One thing confused me is that it can be "insmod" in the linux for mips32, but when we try to "insmod" in the linux for mips64, we get the following error:
[root@(none) root]# insmod try.o
init_module: Invalid module header size.
A new version of the modutils is likely needed.
try.o: init_module: Invalid argument
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
Of course we do the above works in the same hardware platform .
Is there any thing I should pay attention to when I compile the Kernel Module or the linux for mips64? Eagering your help!!
Thank you you in advance!
祝
开心!
Far and away the best prize that life offers is the chance to work hard at work worth doing. 广星
guangxing@ict.ac.cn
2003-09-11
\\\|///
\\ - - //
( @ @ )
--------oOOo-(_)-oOOo---------
广星祝您愉快健康
0ooo
-------- oooO--( )----------
( ) ) /
\ ( (_/
\_)
[-- Attachment #1.2: Type: text/html, Size: 5311 bytes --]
[-- Attachment #2: greenmail01.gif --]
[-- Type: image/gif, Size: 3011 bytes --]
[-- Attachment #3: greenmail02.gif --]
[-- Type: image/gif, Size: 759 bytes --]
[-- Attachment #4: greenmail03.gif --]
[-- Type: image/gif, Size: 1131 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: 广星 <guangxing@ict.ac.cn>
To: linux-mips@linux-mips.orglinux-mips@linux-mips.org
Cc: angela <jhyang@ict.ac.cn>, 谢博士 <xie@ict.ac.cn>
Subject: Some Question about the kernel module on MIPS64
Date: Thu, 11 Sep 2003 10:13:58 +0800 [thread overview]
Message-ID: <20030911021338Z8225363-1272+5279@linux-mips.org> (raw)
Message-ID: <20030911021358.Ges6DLKfqW4RVJpXJbERw4I7ZEd71sRU8BqdpaOZUQk@z> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1602 bytes --]
Hi, everyone!
I am a newbie on doing some development on MIPS(of course it is the linux make me can touch it without any hesitation).There are two questions as follow hoping your enthusiastic answers.
1) I want to know if the linux for mips64 support the customer's kernel module .if yes, is there any modutils i can use?And how can i get it.
2) I have written a simplest simplest kernel module for linux for mips64 (only the init()and cleanup() we can see,and we do nothing.) and with the crossing compiling tool it is ok.One thing confused me is that it can be "insmod" in the linux for mips32, but when we try to "insmod" in the linux for mips64, we get the following error:
[root@(none) root]# insmod try.o
init_module: Invalid module header size.
A new version of the modutils is likely needed.
try.o: init_module: Invalid argument
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
Of course we do the above works in the same hardware platform .
Is there any thing I should pay attention to when I compile the Kernel Module or the linux for mips64? Eagering your help!!
Thank you you in advance!
祝
开心!
Far and away the best prize that life offers is the chance to work hard at work worth doing. 广星
guangxing@ict.ac.cn
2003-09-11
\\\|///
\\ - - //
( @ @ )
--------oOOo-(_)-oOOo---------
广星祝您愉快健康
0ooo
-------- oooO--( )----------
( ) ) /
\ ( (_/
\_)
[-- Attachment #1.2: Type: text/html, Size: 5311 bytes --]
[-- Attachment #2: greenmail01.gif --]
[-- Type: image/gif, Size: 3011 bytes --]
[-- Attachment #3: greenmail02.gif --]
[-- Type: image/gif, Size: 759 bytes --]
[-- Attachment #4: greenmail03.gif --]
[-- Type: image/gif, Size: 1131 bytes --]
next reply other threads:[~2003-09-11 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 2:13 广星 [this message]
2003-09-11 2:13 ` Some Question about the kernel module on MIPS64 广星
2003-09-11 14:26 ` Ralf Baechle
2003-09-11 14:36 ` Keith Owens
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=20030911021338Z8225363-1272+5279@linux-mips.org \
--to=guangxing@ict.ac.cn \
--cc=jhyang@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
--cc=xie@ict.ac.cn \
/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