From: LGW <large@lilymarleen.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: porting driver to 2.6, still unknown relocs... :(
Date: Wed, 27 Aug 2003 18:15:51 +0200 [thread overview]
Message-ID: <3F4CD937.10204@lilymarleen.de> (raw)
In-Reply-To: <1061999977.22825.71.camel@dhcp23.swansea.linux.org.uk>
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?
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:
http://space.virgilio.it/g_pochini@virgilio.it/ea.html (site with the
patches for alsa)
http://space.virgilio.it/g_pochini@virgilio.it/eagd-0.6.0.tar.bz2 (the
original generic driver code)
thanks,
Lars
next prev parent reply other threads:[~2003-08-27 16:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 13:38 porting driver to 2.6, still unknown relocs... :( LGW
2003-08-27 15:13 ` Randy.Dunlap
2003-08-27 15:34 ` LGW
2003-08-27 15:50 ` Randy.Dunlap
2003-08-27 15:59 ` Alan Cox
2003-08-27 16:15 ` LGW [this message]
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=3F4CD937.10204@lilymarleen.de \
--to=large@lilymarleen.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.