A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | AD | AE | AF | AG | AH | AI | AJ | AK | AL | AM | AN | AO | AP | AQ | AR | AS | AT | AU | AV | AW | AX | AY | AZ | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Timestamp | How did the course meet your learning objectives? | How was the duration of the course? | Comments and suggestions | Comments and suggestions | How useful were the training materials? | Comments and suggestions | Will you recommend this document to others? | Comments and suggestions | If you have Linux / Android project opportunities, will you use this document again in the future? | Comments and suggestions | How important are printed materials? | Comments and suggestions | Did instructor oral explanations add value to the lecture materials? | Comments | How much value did the instructor add to lecture materials? | Suggestions and comments | Was the instructor helpful with practical labs? | Comments and suggestions | How do you rate the training equipment (mainly computers)? | Comments and suggestions | How well was the course organized (program, registration, schedule...)? | Comments and suggestions | How much did you learn? | Comments and suggestions | How useful should this course be in your daily job? | Comments and suggestions | Would you recommend this course to others? | Comments and suggestions | Overall rating | Comments and suggestions | Further training needs? | Comments | How did the course meet your learning objectives? | What part(s) of the course did you like most? | Comments | What part(s) of the course did you like least? | What reasons prompted you to choose Bootlin? | How did you first learn about Bootlin? | Interested in other types of embedded Linux engineering services? | Comments and expectations | Comments and suggestions | How do you rate training conditions (room size, equipment, environment)? | How useful were the training labs? | Comments and suggestions | Comments and suggestions | How difficult were the training labs? | Was enough time dedicated to practical labs? | Comments and suggestions | How knowledgeable was the instructor? | Please tell us why you need or don't need paper printed materials | How far do you come from? |
2 | 9/14/2018 15:37:36 | 2 | 5 | 3 | 5 | 5 | 4 | 4 | 1 | 6 | 5 | 5 | Not applicable - My management made the decision | Bootlin chosen by my management | Linux board support package development, Development of real-time systems, Build environment support, Root filesystem development | 5 | 3 | 3 | 5 | |||||||||||||||||||||||||||||||||
3 | 9/14/2018 15:42:27 | 3 | Learning more about the driver patches we used | 5 | 4 | 4 | 5 | 4 | 5 | 3 | 6 | 4 | Kernel training | 4 | layer and recipe creation and improvement | The beginning with a lot of material issues (SII training PCs) | Not applicable - My management made the decision | Bootlin chosen by my management | Not interested | 5 | 3 | 4 | The image building time is a problem for the timing | 5 | Good, but the numeric version is more usefull (copy paste) | |||||||||||||||||||||||||||
4 | 9/14/2018 15:43:39 | 3 | 4 | usage of raspberry pi should be more relevant nowadays than expensive beagleboard, in addition trainee can bring their own | 1 | 4 | Suggest to warn that there are some "wanted" failures during labs, then add tips to help resolve. | 5 | 3 | Suggest to ask for well prepared PC and enough powerful for compiling. | 5 | 5 | 6 | 5 | Linux kernel and driver development training | 5 | To see immediately the "impact" of my work on a hadware element. | Not applicable - My management made the decision | Bootlin chosen by my management | Linux board support package development, Development of real-time systems | 5 | 3 | 3 | 5 | can annotate pdf directly, paper not useful for copy/paste | |||||||||||||||||||||||||||
5 | 9/14/2018 15:45:09 | 3 | 5 | 4 | 5 | 4 | 3 | Passer moins de temps sur la mauvaise pratique | 5 | 3 | NA - cours pris par anticipation | 6 | 3 | 5 | Pratical Labs | Temps de compilation | Not applicable - My management made the decision | Bootlin chosen by my management | On-site engineering | 5 | 3 | 2 | 5 | |||||||||||||||||||||||||||||
6 | 9/14/2018 15:47:22 | 4 | Friday afternoon was a bit long imo mainly because of the several builds (machine change) | Complete with lot of specific usecase | 5 | 4 | 5 | 5 | 5 | 4 | 1 | Working on Windows :( with proprietary OS/archs | 6 | optimise arm335x build time with prebuilt archive ? | 4 | Buildroots, linux kernel modules etc... | 5 | writing tasks part | ninvaders controls & latency é.è | Not applicable - My management made the decision | Bootlin chosen by my management | N/A | 4 | 3 | 2 | 5 | Not usefull; you can send the .pdf files | |||||||||||||||||||||||||
7 | 9/14/2018 15:47:23 | 3 | 5 | 4 | 5 | 5 | 4 | Our company did not provided enough powerful PC to endure some parts of training labs | 4 | 1 | Not used currently, but could be useful in case our company gets a project in the field of the training | 7 | 5 | Kernel driver programming | 5 | Not applicable - My management made the decision | Technical resources on the Bootlin website | our business unit doesn't have embedded linux needs at the moment, but could be interested in build environment support | 5 | 2 | 2 | 5 | ||||||||||||||||||||||||||||||
8 | 9/14/2018 15:47:50 | 1 | 2 | not enough boards for everybody | 5 | 4 | translating the slides most of the time but still adding a few tips now and then so it was ok | 4 | 2 | most of the time was about learning how to malpractice and there was not enough time to do things the right way | 5 | 3 | don't really know yet | 5 | 5 | 4 | labs | dense pack of slides | Not applicable - My management made the decision | Bootlin chosen by my management | Not interested | 4 | 4 | 2 | 4 | very useful to keep trace | ||||||||||||||||||||||||||
9 | 9/14/2018 15:54:12 | 3 | veille techno | 4 | 2 | 5 | 5 | 4 | 4 | 2 | veille techno, non utilisé (pour l'instant) mais utile pour les concepts généraux (build d'os, gestion de boot, ...) | 6 | 2 | non applicable pour l'instant sur nos projets, donc pas de pratique réguliere, perte potentielles des connaissances sur la durée ... | 5 | Labs, la mise en pratique | les temps de compils / soucis liés aux réseau de l'entreprise (ports git bloqués etc) | Not applicable - My management made the decision | Bootlin chosen by my management | Not interested | non intéressé par d'autres services car non linux sur notre CeS pour le moment | 4 | 3 | 3 | 5 |