[lkml]   [2003]   [Aug]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: porting driver to 2.6, still unknown relocs... :(
On Wed, 27 Aug 2003 18:15:51 +0200 LGW <> wrote:

| Alan Cox wrote:
| >On Mer, 2003-08-27 at 16:34, LGW wrote:
| >
| >
| >>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?
| >>
| >>
| >
| >The new module loader is kernel side, it may well not know some of the
| >C++ specific relocation types.
| >
| To you think it's possible to remove those relocations completely, so
| that the whole C++ stuff is linked "without" any more open relocations?

Hopefully Rusty will see this and make some comments on it.

You could try using objdump to look for the item(s) that have this
relocation type (0). That might help to see what is causing it.

Or you could modify the module loader to ignore relocation type 0...
and see what happens.

| After all, those are only "helper functions" that could be linked
| "statically", or am I mistaken?
| I don't have such deep knowledge of the C++ linking process, so I can't
| answer that question myself.
| The Generic Driver is not public available I think, but you could get it
| here:
| (site with the
| patches for alsa)
| (the
| original generic driver code)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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