Re: Building separate files for a kernel module

AFAIK if foo is GPL, you can't link bar to it except if it's GPL to. Doing so would be license breaking. If foo is not GPL, you are tainting your kernel and would be hard to get help with a tainted kernel. 2018-04-09 14:19 GMT-03:00 Martin Galvan : > 2018-04-05 12:02

Re: Building separate files for a kernel module

except if it's GPL too* 2018-04-18 12:57 GMT-03:00 Daniel. : > AFAIK if foo is GPL, you can't link bar to it except if it's GPL to. Doing > so would be license breaking. If foo is not GPL, you are tainting your > kernel and would be hard to get help with a tainted kernel.

Re: Building separate files for a kernel module

2018-04-05 12:02 GMT-03:00 Greg KH : > On Thu, Apr 05, 2018 at 11:49:36AM -0300, Martin Galvan wrote: >> I want my module to be DKMS-enabled, but since the 'bar' binaries >> don't use anything Linux-specific I don't want to distribute the >> sources for it. > > Hahaha, good luck,

Re: Building separate files for a kernel module

On Thu, Apr 05, 2018 at 11:49:36AM -0300, Martin Galvan wrote: > 2018-04-05 2:26 GMT-03:00 : > > On Wed, 04 Apr 2018 18:29:21 -0300, Martin Galvan said: > > > >> PS: Yes, I'm aware I could just add $(bar-objs) to mydriver-y and > >> avoid building bar.a, but I really need

Re: Building separate files for a kernel module

2018-04-05 2:26 GMT-03:00 : > On Wed, 04 Apr 2018 18:29:21 -0300, Martin Galvan said: > >> PS: Yes, I'm aware I could just add $(bar-objs) to mydriver-y and >> avoid building bar.a, but I really need to have those files as a >> separate library. > > What's driving the

Re: Building separate files for a kernel module

On Wed, 04 Apr 2018 18:29:21 -0300, Martin Galvan said: > PS: Yes, I'm aware I could just add $(bar-objs) to mydriver-y and > avoid building bar.a, but I really need to have those files as a > separate library. What's driving the requirement for a separate library?

Building separate files for a kernel module

Hi all, I'm trying to build a kernel module by statically linking object files with a library. My source tree looks like this: source/ ├── bar/ | ├── bar1.c | └── bar2.c └── foo.c The relevant parts of my Makefile look like this: mydriver-y := foo.o bar.a obj-m += mydriver.o bar-objs :=