**** BEGIN LOGGING AT Tue Apr 12 02:59:58 2016 Apr 12 07:25:27 ZeekHuge, sorry left IRC open on work machine as ran out the door last night after a meeting. Apr 12 07:25:34 ZeekHuge, wasn't actually here! Apr 12 07:27:09 chanakya_vc, Sometimes the simplest approach to compiling a driver is just to integrate it with the kernel tree itself. Those build systems are really straight forward to use and lots of examples to follow. Apr 12 07:29:51 chanakya_vc (and anyone else doing kernel drivers) There are a whole load of static analysis tools that can pick up on syntax errors and likely bugs. Some of them are very much aware of how the kernel does things. Apr 12 07:30:24 The standard 3 are sparse (which is a kind of a full c preprocessor with a lot of extra warnings - think of it as like a super fussy gcc) Apr 12 07:30:46 Once you have it installed, if building a driver in the kernel tree then run: Apr 12 07:30:56 touch drivers/misc/whateveryourdriveriscalled.c Apr 12 07:31:03 to make sure your driver is rebuilt and Apr 12 07:31:05 make C=1 Apr 12 07:32:24 The next most commonly applied is probably coccicheck which is a set of semantic rules built on coccinelle - installing it can be a little more interesting as it is written in ml so has some unusual dependencies. Apr 12 07:33:35 make C=1 CHECK=./scripts/coccicheck Apr 12 07:34:41 Third one is Dan Carpenters smatch which tends to find another set of problems and with a bit of work can do stuff like finding symantic issues across whole chunks of the kernel rather than in individual files. Apr 12 07:36:27 One big recent thing that happened in the kernel world is that the 0-day autobuilders will scrape patches posted to certain lists and run a battery of semantic and build tests against them hitting hundreds of platforms / configurations and architectures. Apr 12 07:37:47 Amazingly helpful and means much better test coverage on the build side anyway. Even after review and basic build tests I get issues found by this in maybe one in 20 IIO patches. Apr 12 07:37:59 Anyhow, hope chanakya_vc reads the logs ;) Apr 12 08:36:47 jic23: its ok :) I was studying and the just fell asleep. Exams are near and I am not much prepared yet. Apr 12 08:36:59 exams = 26th this month. Apr 12 10:03:04 ZeekHuge, good luck with the exams! Apr 12 18:21:47 jic23b, So these static tools can help rectify syntax errors and also help with sticking to coding style? Apr 12 18:22:19 jic23b, Could you point me to a source where I can read a bit more about this? Apr 12 18:35:52 Err. Google will probably do as well as me for links. Apr 12 18:39:21 morning Apr 12 19:30:36 jic23b, Okay. :) Apr 12 19:37:58 Thank you jic23b :) Apr 12 19:38:44 Hey ds2 ! Sorry, I was studying yesterday and then fell asleep, so couldnt reply. Apr 12 19:43:36 ds2: Ohk so does that mean I am missing ld.so on my BBB ? Apr 12 19:45:20 ds2: coz there is where the shared libraries get loaded. Isnt it ? Apr 12 19:46:16 ZeekHuge, Hey! You had once told me an alternative to TI ccs to compile code for PRU.Could you share the link that again? Apr 12 19:46:51 * ZeekHuge will lay low and will be slow at replying back, as he has to study for his exams. Apr 12 19:47:02 wait a sec. Apr 12 19:47:31 its in the README of PRU-framework on github. Apr 12 19:47:38 chanakya_vc: ^^ Apr 12 19:48:03 Okay will go through it .Thanks a lot! Apr 12 20:22:59 chanakya_vc: There's gnupru, a GCC compiler for the PRU Apr 12 20:28:03 Abhishek_, So I would have to install that on the BBB right?Would it be correct to call it a cross-compiler for PRU? Apr 12 20:28:33 yep, if you may so Apr 12 20:30:30 I'd recommend sticking with TI PRU C compiler for the moment, although feel free to try gnupru out as well Apr 12 20:30:31 Abhishek_, Okay.I am searching other ways than TI ccs to use for compiling code for PRU.CCS is a bit annoying to use :) Apr 12 20:30:41 chanakya_vc: Makefiles :) Apr 12 20:33:18 Okay. :) Apr 12 20:34:47 Working on the blinky code.I am actually thinking of posting an experiment in hackaday,where I can actually show the speed difference between ARM and PRU while running the same code for blinking LED's Apr 12 20:36:20 Abhishek_, I have done it using PRUspeak and it was awesome to see it on an oscilloscope.I have not tried assembly so will be doing it this time. **** ENDING LOGGING AT Wed Apr 13 02:59:58 2016