coming shortly: series of simple kernel questions i should know the answers to
the lead-in: for the purposes of updating a pile of my existing kernel tutorials and courseware (and writing new material), i'm digging into the source to document numerous concepts from beginning to end, and i'm not surprised when i trip over all sorts of things that are fairly simple but i don't immediately know the answer to. so for the next while, i'm going to ask all sorts of questions to clarify numerous things, then i'll write up the final results and post them for public consumption at my web site so other people can take advantage of this. and i figured it would be useful to ask those questions on this list, as this list is full of clever people who probably know the answers. a lot of the early questions will be based on clarifying details of the driver model, as the current documentation under Documentation/driver-model/ is somewhat out of date so i desperately need to put together something far more current. first question(s) coming shortly ... rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
On Wed, Apr 01, 2015 at 07:21:38AM -0400, Robert P. J. Day wrote:
a lot of the early questions will be based on clarifying details of the driver model, as the current documentation under Documentation/driver-model/ is somewhat out of date so i desperately need to put together something far more current.
I'll gladly accept patches to fix up the in-kernel documentation for the driver-model. A number of things have changed in this area over the past years, especially in the power managment area. But really, almost no "normal" developer has to mess with the kernel at this layer, it's rare that someone writes a new bus or subsystem. Ok, well, we add about one new one every kernel release, so there would be 6 new developers a year that could benifit from better documentation, not a huge number :) thanks, greg k-h
On Wed, 1 Apr 2015, Greg KH wrote:
On Wed, Apr 01, 2015 at 07:21:38AM -0400, Robert P. J. Day wrote:
a lot of the early questions will be based on clarifying details of the driver model, as the current documentation under Documentation/driver-model/ is somewhat out of date so i desperately need to put together something far more current.
I'll gladly accept patches to fix up the in-kernel documentation for the driver-model. A number of things have changed in this area over the past years, especially in the power managment area.
But really, almost no "normal" developer has to mess with the kernel at this layer, it's rare that someone writes a new bus or subsystem.
Ok, well, we add about one new one every kernel release, so there would be 6 new developers a year that could benifit from better documentation, not a huge number :)
you might be surprised at how simple some of my questions are going to be. :-) and, yes, i'll see what i can contribute to the in-kernel documentation -- under Documentation/driver-model, certainly, the "class.txt" file looks pretty badly out of date. or is any of that content even being kept up to date given the DocBook content? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================
On Wed, Apr 01, 2015 at 07:38:22AM -0400, Robert P. J. Day wrote:
On Wed, 1 Apr 2015, Greg KH wrote:
On Wed, Apr 01, 2015 at 07:21:38AM -0400, Robert P. J. Day wrote:
a lot of the early questions will be based on clarifying details of the driver model, as the current documentation under Documentation/driver-model/ is somewhat out of date so i desperately need to put together something far more current.
I'll gladly accept patches to fix up the in-kernel documentation for the driver-model. A number of things have changed in this area over the past years, especially in the power managment area.
But really, almost no "normal" developer has to mess with the kernel at this layer, it's rare that someone writes a new bus or subsystem.
Ok, well, we add about one new one every kernel release, so there would be 6 new developers a year that could benifit from better documentation, not a huge number :)
you might be surprised at how simple some of my questions are going to be. :-) and, yes, i'll see what i can contribute to the in-kernel documentation -- under Documentation/driver-model, certainly, the "class.txt" file looks pretty badly out of date. or is any of that content even being kept up to date given the DocBook content?
I don't remember, sorry, haven't looked at it in years. greg k-h
participants (2)
-
Greg KH -
Robert P. J. Day