lkml.org 
[lkml]   [2003]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: porting driver to 2.6, still unknown relocs... :(
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:48    [W:0.067 / U:2.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site