On Thu, 2006-02-03 at 22:44 +0100, Adrian Bunk wrote:
> > >
> > > We do not have to export symbols we don't want to export to modules but
> > > needed by CONFIG_UNIX.
> >
> > Sorry, I must just be dense, or something.
> >
> > Is not the only difference between a modular driver and a built in
> > driver supposed to be the initialization and cleanup functions?
> >
> > I don't see why you would have to expose any additional symbols, over
> > and above the existing required symbols, to load your module.
>
> Every kernel symbol a module uses must be explicitely exported with
> EXPORT_SYMBOL.
>
Yes, I understand that I need to export symbols to define the interface
to my driver. whether its a module or compiled in. This is how other
systems interact with my driver, right?
> CONFIG_UNIX uses symbols that are neither used by any other in-kernel
> modules nor should be exported.
>
Are you saying that AF_UNIX has to export symbols for its own private
functions in order to call them? I guess I don't understand this. Why
not just call them. They're in scope within the driver code, aren't
they?
> > James C. Georgas <[email protected]>
>
> cu
> Adrian
>
--
James C. Georgas <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
