**** BEGIN LOGGING AT Tue Dec 12 03:00:01 2017
Dec 12 03:39:09 <mohit> hello, everyone
Dec 12 08:33:38 <zeekhuge> maciejjo: The project moves forward with the aim to "get merged into the mainline", and that thought, is what usually helps in deciding the license and other stuff. I have limited knowledge of these licenses, but I think MIT-license will stop it from getting into the mainline.
Dec 12 08:33:39 <zeekhuge> its Just my opinion, lets wait for other mentors to comment.
Dec 12 10:07:38 <maciejjo> zeekhuge: thanks for input, but where exactly should be PRU part merged? I understand that kernel driver must be GPL so it can be merged to kernel tree, but I am not sure to what project could the PRU part go
Dec 12 21:11:33 <nerdboy> the firmware wouldn't have to go into the kernel tree
Dec 12 21:11:47 <nerdboy> maybe shouldn't even
Dec 12 21:12:17 <nerdboy> your kernel doc can certainly point to it
Dec 12 21:12:59 * nerdboy submitted a u-boot readme patch with (free) vendor tool stuff
Dec 12 21:14:14 <nerdboy> how does TI license their pru stuff?  i think the bb firmware is patched into mainline
Dec 12 21:14:59 <nerdboy> afaik whatever firmware is in ti dev kernel is not in mainline
Dec 12 21:15:15 <nerdboy> but i could be wrong...
Dec 13 02:18:20 <moto-timo> http://gitorious.ti.com/ti-linux-kernel/ti-linux-kernel/trees/master
Dec 13 02:18:56 <moto-timo> http://gitorious.ti.com/pru-software-support-package
Dec 13 02:19:13 <moto-timo> but the pru repo does not seem to have any license info
**** ENDING LOGGING AT Wed Dec 13 03:00:01 2017