public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Hollis Blanchard <hollisb@us.ibm.com>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: cross-depmod?
Date: Mon, 09 Aug 2004 09:05:11 +1000	[thread overview]
Message-ID: <1091963200.27202.10.camel@bach> (raw)
In-Reply-To: <20040806154211.GB7331@mars.ravnborg.org>

On Sat, 2004-08-07 at 01:42, Sam Ravnborg wrote:
> I assume the problem arises from the fact that depmod are only capable of
> reading elf files for the host it is compiled for.
> OK, took a look at depmod.
> It handles both 32 and 64 bit but assumes same endian.
> 
> Rusty: Would it make sense to extend module-init-tools to support
> endian as specified in elf file?

Frankly, yes.

In my opinion, it makes even more sense for modprobe to do the work
itself, and cache the info in /lib/modules/`uname
-r`/modules.{dep,alias,symtab}.

I was always planning on doing this after we got rid of the modules.map
files, but that never happened due to reluctance from other people to
transition, and I didn't fight them.

Cheers,
Rusty.
-- 
Anyone who quotes me in their signature is an idiot -- Rusty Russell


  reply	other threads:[~2004-08-08 23:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 21:51 cross-depmod? Hollis Blanchard
2004-08-06  8:40 ` cross-depmod? David Vrabel
2004-08-06 13:45   ` cross-depmod? Geert Uytterhoeven
2004-08-06 15:17     ` cross-depmod? Sam Ravnborg
2004-08-06 15:42 ` cross-depmod? Sam Ravnborg
2004-08-08 23:05   ` Rusty Russell [this message]
2004-08-09  6:15     ` cross-depmod? Greg KH

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=1091963200.27202.10.camel@bach \
    --to=rusty@rustcorp.com.au \
    --cc=hollisb@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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