Here it is https://github.com/martinezjavier/ldd3 Regards On Oct 24, 2017 9:58 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello Daniel,
24.10.2017, 14:50, "Daniel." <danielhilst@gmail.com>:
There is a repo at github with all the samples don't?
I think that no, I not seen before on github.
Regards
Ozgur
On Oct 24, 2017 9:06 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello Ryan,
24.10.2017, 13:58, "Liam Ryan" <liamryandev@gmail.com>:
I'm currently working through the Linux Device Drivers 3rd edition (https://lwn.net/Kernel/LDD3/) and much of the code is outdated.
Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x
I'm wondering about the Creative Commons license on the LDD3 book. I believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?
I think you can update and re-publish the example code and don't break the original comment lines. At least I think this.
Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.
Thanks, Liam
Regards
Ozgur
You're welcome! On Oct 24, 2017 10:38 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello,
24.10.2017, 15:31, "Daniel." <danielhilst@gmail.com>:
Here it is https://github.com/martinezjavier/ldd3
Regards
oh, it's very good, nice. Thank you
Ozgur
On Oct 24, 2017 9:58 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello Daniel,
24.10.2017, 14:50, "Daniel." <danielhilst@gmail.com>:
There is a repo at github with all the samples don't?
I think that no, I not seen before on github.
Regards
Ozgur
On Oct 24, 2017 9:06 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello Ryan,
24.10.2017, 13:58, "Liam Ryan" <liamryandev@gmail.com>:
I'm currently working through the Linux Device Drivers 3rd edition (https://lwn.net/Kernel/LDD3/) and much of the code is outdated.
Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x
I'm wondering about the Creative Commons license on the LDD3 book. I believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?
I think you can update and re-publish the example code and don't break the original comment lines. At least I think this.
Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.
Thanks, Liam
Regards
Ozgur
On Tue, Oct 24, 2017 at 10:49:34AM -0200, Daniel. wrote:
You're welcome!
On Oct 24, 2017 10:38 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello,
24.10.2017, 15:31, "Daniel." <danielhilst@gmail.com>:
Here it is https://github.com/martinezjavier/ldd3
Thanks I had found this repo which is a great reference for when I get stuck in my own attempt to update the old code, however I believe this repo is also outdated. For instance it calls aio_complete on line 405 of main.c of scullc which I found has since been removed ( or I made a huge error :) ). Leaving that aside I'm referring to updating the book itself rather than the code as the text makes reference to the code as written in 2005. I'll ask the question on the debian-legal list as recommended, I think the threads diverged at some point. Regards, Liam
Regards
oh, it's very good, nice. Thank you
Ozgur
On Oct 24, 2017 9:58 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello Daniel,
24.10.2017, 14:50, "Daniel." <danielhilst@gmail.com>:
There is a repo at github with all the samples don't?
I think that no, I not seen before on github.
Regards
Ozgur
On Oct 24, 2017 9:06 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello Ryan,
24.10.2017, 13:58, "Liam Ryan" <liamryandev@gmail.com>:
I'm currently working through the Linux Device Drivers 3rd edition (https://lwn.net/Kernel/LDD3/) and much of the code is outdated.
Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x
I'm wondering about the Creative Commons license on the LDD3 book. I believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?
I think you can update and re-publish the example code and don't break the original comment lines. At least I think this.
Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.
Thanks, Liam
Regards
Ozgur
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Tue, Oct 24, 2017 at 02:03:59PM +0100, Liam Ryan wrote:
On Tue, Oct 24, 2017 at 10:49:34AM -0200, Daniel. wrote:
You're welcome!
On Oct 24, 2017 10:38 AM, "Ozgur" <okaratas@yandex.com> wrote:
Hello,
24.10.2017, 15:31, "Daniel." <danielhilst@gmail.com>:
Here it is https://github.com/martinezjavier/ldd3
Thanks I had found this repo which is a great reference for when I get stuck in my own attempt to update the old code, however I believe this repo is also outdated. For instance it calls aio_complete on line 405 of main.c of scullc which I found has since been removed ( or I made a huge error :) ).
This is the repo I worked off of https://github.com/duxing2007/ldd3-examples-3.x
Leaving that aside I'm referring to updating the book itself rather than the code as the text makes reference to the code as written in 2005.
Isn't that the same thing? You need updated code to update the book. Not to throw water on your enthusiasm but that book is amazingly well written, there are [throw away] comments in that book that have taught me loads about subtle concepts of kernel development. I would be very hesitant removing any text from that book if one is not _very_ experienced. There is a wealth of knowledge in it and the few functions that are out of date do little to reduce it's educational value IMO. Sure, it would be nice to have a few of the newer kernel features included but again this is not a job for just anyone. Those guys that wrote that book are seriously experienced. Hope this helps, Tobin.
participants (4)
-
Daniel. -
Liam Ryan -
Ozgur -
Tobin C. Harding