[LITMUS^RT] Kernel Instillation

[NICHOLAS ALLAN KLEPP]

Forgive my questions if they are elementary or naive. I am a bit out of my depth with Linux Kernel instillation, but I very much desire to learn.


I have cloned into the github source repo. I have not tried to patch against my previously downloaded 4.1.32 Linux kernel source code, as I believe the Litmus source is a complete kernel source code if cloned from the source repo? Please correct me if I am mistaken.


After I have configured the kernel with "make menuconfig" I make the kernel image with "make bzImage". Next I try to make the modules with "make modules" and I am presented with this error:


In file included from include/linux/printk.h:275:0,
                 from include/linux/kernel.h:13,
                 from drivers/media/usb/as102/as102_usb_drv.c:16:
drivers/media/usb/as102/as102_usb_drv.c: In function 'as102_usb_xfer_cmd':
include/linux/dynamic_debug.h:86:3: error: incompatible type for argument 2 of '__dynamic_dev_dbg'
   __dynamic_dev_dbg(&descriptor, dev, fmt, \
   ^
include/linux/device.h:1115:2: note: in expansion of macro 'dynamic_dev_dbg'
  dynamic_dev_dbg(dev, format, ##__VA_ARGS__); \
  ^
drivers/media/usb/as102/as102_usb_drv.c:117:3: note: in expansion of macro 'dev_dbg'
   dev_dbg(bus_adap->usb_dev->dev,
   ^
include/linux/dynamic_debug.h:53:6: note: expected 'const struct device *' but argument is of type 'struct device'
 void __dynamic_dev_dbg(struct _ddebug *descriptor, const struct device *dev,
      ^
include/linux/dynamic_debug.h:86:3: error: incompatible type for argument 2 of '__dynamic_dev_dbg'
   __dynamic_dev_dbg(&descriptor, dev, fmt, \
   ^
include/linux/device.h:1115:2: note: in expansion of macro 'dynamic_dev_dbg'
  dynamic_dev_dbg(dev, format, ##__VA_ARGS__); \
  ^
drivers/media/usb/as102/as102_usb_drv.c:135:3: note: in expansion of macro 'dev_dbg'
   dev_dbg(bus_adap->usb_dev->dev,
   ^
include/linux/dynamic_debug.h:53:6: note: expected 'const struct device *' but argument is of type 'struct device'
 void __dynamic_dev_dbg(struct _ddebug *descriptor, const struct device *dev,
      ^
scripts/Makefile.build:258: recipe for target 'drivers/media/usb/as102/as102_usb_drv.o' failed
make[4]: *** [drivers/media/usb/as102/as102_usb_drv.o] Error 1
scripts/Makefile.build:403: recipe for target 'drivers/media/usb/as102' failed
make[3]: *** [drivers/media/usb/as102] Error 2
scripts/Makefile.build:403: recipe for target 'drivers/media/usb' failed
make[2]: *** [drivers/media/usb] Error 2
scripts/Makefile.build:403: recipe for target 'drivers/media' failed
make[1]: *** [drivers/media] Error 2
Makefile:946: recipe for target 'drivers' failed
make: *** [drivers] Error 2


Have I made some mistake? Thanks for any help you are able to offer! - Nick

________________________________
From: litmus-dev-bounces at lists.litmus-rt.org <litmus-dev-bounces at lists.litmus-rt.org> on behalf of Björn Brandenburg <bbb at mpi-sws.org>
Sent: Friday, September 9, 2016 6:04 AM
To: litmus-dev at lists.litmus-rt.org
Subject: Re: [LITMUS^RT] Kernel Instillation


> On 08 Sep 2016, at 22:17, NICHOLAS ALLAN KLEPP <nickbk at uga.edu> wrote:
>
> Hello! Could you please explain the meaning of "plan to use Litmus^RT for development" as it is used in the instillation Wiki? If I would like to write a scheduling module should I work from the source repository or is it sufficient to simply patch as per the instillation Wiki? Thanks! - Nick

Hi Nick,

yes, your should clone the repos; writing a new plugin is  exactly what's meant by "development." If you want to hack the kernel or liblitmus: clone the git repos. If you just want to compile what we've released, it's fine to use the tarballs.

Best,
Björn



_______________________________________________
litmus-dev mailing list
litmus-dev at lists.litmus-rt.org
https://lists.litmus-rt.org/listinfo/litmus-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.litmus-rt.org/pipermail/litmus-dev/attachments/20160909/addcf218/attachment.html>