Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: ???? <guangxing@ict.ac.cn>
Cc: linux-mips@linux-mips.org, angela <jhyang@ict.ac.cn>, xie@ict.ac.cn
Subject: Re: Some  Question about the kernel module on MIPS64
Date: Thu, 11 Sep 2003 16:26:11 +0200	[thread overview]
Message-ID: <20030911142611.GC15365@linux-mips.org> (raw)
In-Reply-To: <20030911021338Z8225363-1272+5279@linux-mips.org>

On Thu, Sep 11, 2003 at 10:13:58AM +0800, ???? wrote:

>    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.

There is currently no module support for mips64.

>    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.

True.

> 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!!

The problem isn't the kernel but modutils which don't support kernel
modules for 64-bit kernels.

  Ralf

  parent reply	other threads:[~2003-09-11 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11  2:13 Some Question about the kernel module on MIPS64 广星
2003-09-11  2:13 ` 广星
2003-09-11 14:26 ` Ralf Baechle [this message]
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=20030911142611.GC15365@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=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