mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: LGW <large@lilymarleen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: porting driver to 2.6, still unknown relocs... :(
Date: Wed, 27 Aug 2003 08:50:00 -0700	[thread overview]
Message-ID: <20030827085000.3726a502.rddunlap@osdl.org> (raw)
In-Reply-To: <3F4CCF85.1020502@lilymarleen.de>

On Wed, 27 Aug 2003 17:34:29 +0200 LGW <large@lilymarleen.de> wrote:

| Randy.Dunlap wrote:
| 
| >On Wed, 27 Aug 2003 15:38:26 +0200 LGW <large@lilymarleen.de> wrote:
| >
| >| Now I wonder, what would be an relocation type 0? The printk should also 
| >| print the type in clear text I think, but it just prints 0. 0 also does 
| >| not look very much like a valid value at all, or does it?

In 2.6.0, include/asm-i386/elf.h lists the ELF relocation types.
Type 0 is "R_386_NONE".  Apparently something is being generated
with "no relocation needed" if I interpret this correctly (?).

| >Maybe g++ generates something different?
| >Are parts of your driver in c++?
| >
| I think the g++ is the problem, but I'm not sure what it is.
| 
| The driver is mostly a wrapper around a generic driver released by the 
| manufacturer, and that's written in C++. But it worked like this for the 
| 2.4.x kernel series, so I think it has something todo with the new 
| module loader code. Possibly ld misses something when linking the object 
| specific stuff like constructors?

Maybe.  It probably wasn't meant to support C++.

Is the generic driver source code available?

| I don't think there are any other errors in the module (like 
| incompatible MODULE_stuff or missing statements), as it has been copied 
| from a patched alsa-0.9.6, and I diff'd the other drivers, not finding 
| much differences (if any).
| 
| Any ld parameters I could try? I already tried -Ur, but that lead to 
| nothing :(

--
~Randy

  reply	other threads:[~2003-08-27 15:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 13:38 LGW
2003-08-27 15:13 ` Randy.Dunlap
2003-08-27 15:34   ` LGW
2003-08-27 15:50     ` Randy.Dunlap [this message]
2003-08-27 15:59     ` Alan Cox
2003-08-27 16:15       ` LGW
2003-08-27 16:29         ` Randy.Dunlap
2003-08-27 17:25           ` porting driver to 2.6, partly solved LGW
2003-08-27 17:07       ` porting driver to 2.6, still unknown relocs... :( Stephen Hemminger
2003-08-27 17:23         ` Richard B. Johnson
2003-08-27 17:33           ` LGW

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=20030827085000.3726a502.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=large@lilymarleen.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®