On Fri, Aug 02, 2013 at 09:56:17AM +0800, Chen Wang wrote: > On Thu, 2013-08-01 at 10:34 -0400, Alan Stern wrote: > > On Thu, 1 Aug 2013, Oliver Neukum wrote: > > > > > On Thu, 2013-08-01 at 17:13 +0800, Chen Wang wrote: > > > > hello, > > > > I'm reading code of usb core and driver model/sysfs. I believe they are > > > > designed with OOP. > > > > > > Yes, much of the code is OO. However, we usually > > > don't overwrite methods. > > > > > > > So, do we have any UML design diagrams for better > > > > > > No. The code was designed without diagrams. > > > > > > > understanding? I can't image newbies can ramp up quickly in front of > > > > such tons of codes without a high-level design guidance, though I > > > > believe I can understand them finally after days ;). > > > > > > You can write a USB driver without understanding driver > > > core. The driver core is needed only to understand > > > probing and power management in usbcore. > > > > On the other hand, patches to improve the documentation are always > > welcome. :-) > My draft idea is some UML diagrams (in high-level) may help > understanding the arch. Actually I am trying to write some by myself > when I am reading the code. Not sure if kernel would accept a graph (in > what format?) due to seems kernel documentation are all in plain text. I doubt UML is really needed to understand the driver core, as it's probably more work to try to read them, than to read the code itself. And very few people actually touch the driver core, so its use would be quite limited. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
