<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>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.
<br>
</p>
<p><br>
</p>
<p>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. <br>
</p>
<p><br>
</p>
<p>After I have configured the kernel with "<span style="font-family: "Courier New",monospace;">make menuconfig</span>" I make the kernel image with "<span style="font-family: "Courier New",monospace;">make bzImage</span>". Next I try to make the modules with
"<span style="font-family: "Courier New",monospace;">make modules</span>" and I am presented with this error:
<br>
</p>
<p><br>
</p>
<p></p>
<div><span style="font-family: "Courier New",monospace;">In file included from include/linux/printk.h:275:0,</span><br>
<span style="font-family: "Courier New",monospace;"> from include/linux/kernel.h:13,</span><br>
<span style="font-family: "Courier New",monospace;"> from drivers/media/usb/as102/as102_usb_drv.c:16:</span><br>
<span style="font-family: "Courier New",monospace;">drivers/media/usb/as102/as102_usb_drv.c: In function ‘as102_usb_xfer_cmd’:</span><br>
<span style="font-family: "Courier New",monospace;">include/linux/dynamic_debug.h:86:3: error: incompatible type for argument 2 of ‘__dynamic_dev_dbg’</span><br>
<span style="font-family: "Courier New",monospace;"> __dynamic_dev_dbg(&descriptor, dev, fmt, \</span><br>
<span style="font-family: "Courier New",monospace;"> ^</span><br>
<span style="font-family: "Courier New",monospace;">include/linux/device.h:1115:2: note: in expansion of macro ‘dynamic_dev_dbg’</span><br>
<span style="font-family: "Courier New",monospace;"> dynamic_dev_dbg(dev, format, ##__VA_ARGS__); \</span><br>
<span style="font-family: "Courier New",monospace;"> ^</span><br>
<span style="font-family: "Courier New",monospace;">drivers/media/usb/as102/as102_usb_drv.c:117:3: note: in expansion of macro ‘dev_dbg’</span><br>
<span style="font-family: "Courier New",monospace;"> dev_dbg(bus_adap->usb_dev->dev,</span><br>
<span style="font-family: "Courier New",monospace;"> ^</span><br>
<span style="font-family: "Courier New",monospace;">include/linux/dynamic_debug.h:53:6: note: expected ‘const struct device *’ but argument is of type ‘struct device’</span><br>
<span style="font-family: "Courier New",monospace;"> void __dynamic_dev_dbg(struct _ddebug *descriptor, const struct device *dev,</span><br>
<span style="font-family: "Courier New",monospace;"> ^</span><br>
<span style="font-family: "Courier New",monospace;">include/linux/dynamic_debug.h:86:3: error: incompatible type for argument 2 of ‘__dynamic_dev_dbg’</span><br>
<span style="font-family: "Courier New",monospace;"> __dynamic_dev_dbg(&descriptor, dev, fmt, \</span><br>
<span style="font-family: "Courier New",monospace;"> ^</span><br>
<span style="font-family: "Courier New",monospace;">include/linux/device.h:1115:2: note: in expansion of macro ‘dynamic_dev_dbg’</span><br>
<span style="font-family: "Courier New",monospace;"> dynamic_dev_dbg(dev, format, ##__VA_ARGS__); \</span><br>
<span style="font-family: "Courier New",monospace;"> ^</span><br>
<span style="font-family: "Courier New",monospace;">drivers/media/usb/as102/as102_usb_drv.c:135:3: note: in expansion of macro ‘dev_dbg’</span><br>
<span style="font-family: "Courier New",monospace;"> dev_dbg(bus_adap->usb_dev->dev,</span><br>
<span style="font-family: "Courier New",monospace;"> ^</span><br>
<span style="font-family: "Courier New",monospace;">include/linux/dynamic_debug.h:53:6: note: expected ‘const struct device *’ but argument is of type ‘struct device’</span><br>
<span style="font-family: "Courier New",monospace;"> void __dynamic_dev_dbg(struct _ddebug *descriptor, const struct device *dev,</span><br>
<span style="font-family: "Courier New",monospace;"> ^</span><br>
<span style="font-family: "Courier New",monospace;">scripts/Makefile.build:258: recipe for target 'drivers/media/usb/as102/as102_usb_drv.o' failed</span><br>
<span style="font-family: "Courier New",monospace;">make[4]: *** [drivers/media/usb/as102/as102_usb_drv.o] Error 1</span><br>
<span style="font-family: "Courier New",monospace;">scripts/Makefile.build:403: recipe for target 'drivers/media/usb/as102' failed</span><br>
<span style="font-family: "Courier New",monospace;">make[3]: *** [drivers/media/usb/as102] Error 2</span><br>
<span style="font-family: "Courier New",monospace;">scripts/Makefile.build:403: recipe for target 'drivers/media/usb' failed</span><br>
<span style="font-family: "Courier New",monospace;">make[2]: *** [drivers/media/usb] Error 2</span><br>
<span style="font-family: "Courier New",monospace;">scripts/Makefile.build:403: recipe for target 'drivers/media' failed</span><br>
<span style="font-family: "Courier New",monospace;">make[1]: *** [drivers/media] Error 2</span><br>
<span style="font-family: "Courier New",monospace;">Makefile:946: recipe for target 'drivers' failed</span><br>
<span style="font-family: "Courier New",monospace;">make: *** [drivers] Error 2</span><br>
</div>
<br>
<p></p>
<p>Have I made some mistake? Thanks for any help you are able to offer! - Nick <br>
</p>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> litmus-dev-bounces@lists.litmus-rt.org <litmus-dev-bounces@lists.litmus-rt.org> on behalf of Björn Brandenburg <bbb@mpi-sws.org><br>
<b>Sent:</b> Friday, September 9, 2016 6:04 AM<br>
<b>To:</b> litmus-dev@lists.litmus-rt.org<br>
<b>Subject:</b> Re: [LITMUS^RT] Kernel Instillation</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
> On 08 Sep 2016, at 22:17, NICHOLAS ALLAN KLEPP <nickbk@uga.edu> wrote:<br>
> <br>
> 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 <br>
<br>
Hi Nick,<br>
<br>
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.<br>
<br>
Best,<br>
Björn<br>
<br>
<br>
<br>
_______________________________________________<br>
litmus-dev mailing list<br>
litmus-dev@lists.litmus-rt.org<br>
<a id="LPlnk418606" href="https://lists.litmus-rt.org/listinfo/litmus-dev">https://lists.litmus-rt.org/listinfo/litmus-dev</a><br>
</div>
</span></font></div>
</div>
</body>
</html>