0e535bf82f1cc4baa415b02dc0bc168cc19ab709 — Bryan Brattlof 3 years ago add2110
task 11: add task readme
2 files changed, 33 insertions(+), 0 deletions(-)

M readme.rst
A tasks/11/readme
M readme.rst => readme.rst +2 -0
@@ 32,3 32,5 @@ Here are the links to each task's readme:
9. Working with sysfs: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/09/readme>`__

10. Submit a Patch: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/10/readme>`__

11. A Driver Patch: `task <https://git.bryanbrattlof.com/eudyptula-challenge/tree/tasks/11/readme>`__

A tasks/11/readme => tasks/11/readme +31 -0
@@ 0,0 1,31 @@
Task 11

You made a successful patch to the kernel source tree, that's a great

But, let's not rest, time to get back to code.

Remember that mess of kobject and sysfs code back in task 09?  Let's
move one level up the tree and start to mess with devices and not raw

For this task:

  - Write a patch against any driver that you are currently using on
    your machine.  So first you have to figure out which drivers you are
    using, and where the source code in the kernel tree is for that

  - In that driver, add a sysfs file to show up in the /sys/devices/
    tree for the device that is called "id".  As you might expect, this
    file follows the same rules as task 09 as for what you can read and
    write to it.

  - The file is to show up only for devices that are controlled by a
    single driver, not for all devices of a single type (like all USB
    devices.  But all USB maibox LEDs would be acceptable, if you happen
    to have the device that that driver controls.)

Submit both the patch, in proper kernel commit form, and "proof" of it
working properly on your machine.
\ No newline at end of file