At Thu, 10 Jan 2002 17:35:00 -0800,
Mike Smith wrote:
In order to deal with this problem, I have changed the module build
process so that symbols global to the module are converted to local
symbols when the module is linked into the .kld/,ko file. In order
to allow modules that intentionally
Hidetoshi Shimokawa wrote:
At Thu, 10 Jan 2002 17:35:00 -0800,
Mike Smith wrote:
In order to deal with this problem, I have changed the module build
process so that symbols global to the module are converted to local
symbols when the module is linked into the .kld/,ko file. In order
to
At Tue, 19 Feb 2002 21:41:11 -0800,
Peter Wemm wrote:
e.g.
kldload module1
kldload module2
module2 cannnot resolv symbols in module1.
-stable doesn't have this problem.
module2 cannot resolve symbols in module1 unless there is a declared
dependency. This is intentional,
Mike Smith wrote:
In the book Writing Linux DEvice Drivers, there is a neat bit
on how Linux does this. Effectively, they export all symbols
within the module load if there is no explicit symbol table
export call, and they export only the symbols that are requested,
if there is.
I
On Thu, 10 Jan 2002 20:17:10 PST, Terry Lambert wrote:
The way this works is that they substitute the symbol list at
the module load time, after the load, but before the relocation.
This is actually nicer, in that it leaves the symol list control
in the source file, rather than hiding it
* Mike Smith [EMAIL PROTECTED] [020110 17:36] wrote:
Questions and comments welcome.
Looks really cool, nice job.
-Alfred
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Mike Smith wrote:
In order to deal with this problem, I have changed the module build
process so that symbols global to the module are converted to local
symbols when the module is linked into the .kld/,ko file. In order
to allow modules that intentionally export symbols to continue to do
In the book Writing Linux DEvice Drivers, there is a neat bit
on how Linux does this. Effectively, they export all symbols
within the module load if there is no explicit symbol table
export call, and they export only the symbols that are requested,
if there is.
I considered this approach,
