So a “hardware driver” in U-Boot is just a piece of code that implements a set of functions that are linked into the global name space. To cope with these increased numbers a second instructor was brought in, together with seven other personnel who were particularly qualified in the subject. At this point, it’s quite clear that there’s a somewhat tangled set of header files that define CONFIG_* compilation variables (and others). After three months training in theory and tactics there was further special training in the working of the gyro-compass, underwater sound location and escape apparatus. This tutorial was written with respect to U-Boot version v2013.07, but the principles apply for a wide range of versions. For example, supporting board-specific features or adding a few routines that give the end-user signs that the device has indeed powered on, and that something is happening while the boot process takes place. In Germany Spindler was actively establishing a training program, and in conjunction with the Navy Arms Superintendent he managed to start a series of theoretical lectures on the U-boat for senior ensigns. Fürbringer was felt to be suitably experienced to set this up and so under the command of Kolbe he gave a six-day course in May 1932 to 49 ensigns at the TNS on the subject of submarines. Papenburg had already been transferred to have control of U-boat building. The typical way to add a completely new functionality to U-Boot is writing driver code, writing the command front-end for it, and enable them both with CONFIG flags. This was changed in 1932 following establishment of the building plan for 16 submarines for the Navy by 1938. as follows: The included config files contains other #define (and possibly #undef) statements, most of which for variables with a CONFIG_* prefix. Writing a small custom driver and command support is by far more elegant and reusable, if the hardware’s setup can be deferred to the command execution stage. %%EOF 211 0 obj <> endobj U-boat Flotilla Weddigen was set up in Kiel on 27.9.35 with U-7 to 12, (leaving U-1 to 6 for training.) Darüber hinaus sind die Einheiten der U-Boot-Klasse 212 A ein Technologiesprung im konventionellen U-Boot-Bau. The immediate instinct when encountering a large chunk of software sources is to look for the first place to inject a small hack, and hardcode the necessary functionality. h�b```f``�d`b``1e�e@ ^V �8 ���Q��:��E?�����ݛv�^Ϸ�;� ?��1kcε.%!� �5����Zr�TM�Ёp6돵j4B��JC�\]+Z#C;�Cf*10��d�jN�\�:��͏Sؤ�.�e��|�V��V�l���cޥ�m�$r5z�x������I{1�.�x�q��D�3���3��qTs�M"�{���íB�v�1m�%�J�f{�K]�f;�����������P^������T�hP�`(o`o`�``�`,�� 1����A �`�h`(��` K�� ��` l 9v�JJ��L�|@� �������pB���ː���3�>�Wl�z�X��M�E��`0�� ��F����4#wq�'~�� � �ƪ� Schottky, who lectured on the course in early 1929, took over the U-boat Office from Spindler in 1929, and he made efforts to implement simulator training on the UZ Boats and on the Roeder designed "F" and "T" devices (early simulators). For example, a CONFIG that enables the compilation of a certain driver may also cause a snippet of initialization code to opt in with #ifdef. Naval Command considered that on political grounds only retired personnel should be involved, together with highly experienced civilian staff.

The first crew at this school comprised eight officers, and 70-80 NCO's and seamen, all of whom assembled in Kiel in Summer 1933.