|Timestamp||How did the course meet your learning objectives?||How was the duration of the course?||Comments and suggestions||Comments and suggestions||How useful was the lecture document?||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 knowledgeable was the instructor?||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||An extra session?||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 prompted you to choose Free Electrons?||How did you first learn about Free Electrons?||Interested in other types of embedded Linux / Android 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 far do you come from?|
|10/25/2013 18:20:38||2||4 days was a bit short||5||Lecture and labs should be split into two separated documents: always switching pages was a bit painful.||3||Very nice and open to questions, he admit when it doesn't know responses (maybe too often the case), which is good.||3||He was often rephrasing the slide, I assume that's because the slides was quite fresh.||5||1||Unity sucks...||5||5||2||6||some typo nunchuk -> nunchuck.||2||Assimilate what has been done so far in the training before another one !||4||Not applicable - My management made the decision||Free Electrons chosen by my management||Board Support Package development: make Linux / Android support your new hardware, Boot time reduction, Build environment deployment and support, Root filesystem design and development, Technical support||Thank you Free-Electrons !||Always available to help !||5||3||Not really easy/useful to implement something you was just spoken about.||Same thing||3||3||Same thing||From less than 100 km / 60 miles|
|10/28/2013 10:21:19||2||But we booked for only 4 days instead of 5(typical/recommended duration)||3||It was useful, but i could have been more useful by showing/comparing by example in parallel of the lecture||3||He
was quite good, but I think he didn't known very well slides and
exercise. Due to the fact that some question where not answered on the
moment(during lecture), and correction sheet was needed to debug groups.|
But he managed to give us afterward answer to our question he couldn't answer on the moment.
|3||I think it was good, the instructor added personal experience, personal facts, and historical events that made the kernel development like that, also he really encouraged us to propose our patches.||3||* Beagle board is a great example for installing Linux.|
* The nunchuk add interest and fun to the lab
=> To bad to not have a little App so as to use the input file at the end of the lab(would add a bit of fun for people that finish the lab early)
* Slides of the lecture and from the labs have hidden characters that made it not copy paste'able in code... You should add a summary of command line/ code snippets in a plain text file, that would save use a lot of useless recopying time.
* Room size was okay, and environment too.
Ubuntu facilitate installation of tools, but unity is really painful and should be avoided for futur trainning
|3||Schedule was good, perhaps we could have stay a bit longer the afternoon, but I guess for the other points I didn't managed it myself.||5||I learned a lot and I loved it.||4||As I'm design engineer the last part of the training ('scheduling') was quite interesting and can be useful for kernel deep comprehension and mechanism that are involved above the processor.||6||Great support, great labs, great instructor, great subject, great example||2||No need, only training and practice on my own is now required to enhance.||4||Definitively, Labs were the most interesting parts,||Not really one in particular, but some lectures were difficult to follows, a second windows with code example should be used to practically explain lecture.||Availability for on-site sessions, Open training materials that can be checked in advance, Access to full feedback from participants to previous sessions||Course recommended by previous participants||Boot time reduction, Power management, Investigating and fixing bugs||Yes for basics questions but I think he didn't mastered it,||3||5||Labs where very good, but when didn't have enough times to do it, and go deep in the comprehension of it.||Labs where just the right difficulty, increasing until the end of the training. A little problem for slow groups was the fact that labs have dependency on previous labs, and if those are not fully completed and understood that next lab is a bit foggy. But it's when it's hard that we learn things (the last one was quite complete)||3||2||Would have preferred more times on lab than on lectures||From less than 100 km / 60 miles|
|10/28/2013 18:03:20||3||4||4||4||4||5||5||5||2||This course will not be very useful in a sense that I am not developing drivers in my daily job however understanding how the Linux kernel works helps to understand what features we should improve in a CPU design.||6||4||4||Writing a driver for the Nintendo Nunchuk.||Not applicable - My management made the decision||Course recommended by previous participants||Not interested||5||5||2||3||From less than 100 km / 60 miles|
|10/28/2013 18:08:16||3||5||5||4||5||5||5||4||3||6||4||5||Not applicable - My management made the decision||Free Electrons chosen by my management||On-site development, support and consulting services||5||5||4||3||From a foreign country|
|10/29/2013 8:49:31||3||4||5||5||5||4||5||5||2||6||4||4||Not applicable - My management made the decision||Free Electrons chosen by my management||Not interested||I just suggest to separate lecture and labs into two different documents, which would make doc search during labs easier||5||5||I found them well balanced for my beginner level.||3||3||From less than 100 km / 60 miles|
|10/29/2013 13:50:14||3||I was expecting more kernel code deep dive and less driver specific stuff. The training was intersteing but in my day to day life it won't help me a lot||4||3||The instructor was ok about drivers and general kernel question but as the training was for ARM guys I was expecting more knowledge of the matches between kernel tasks and ARM architecture (instructions generated for example).||4||4||5||5||4||A lot but on a very restricted domain (kernel drivers) I would have expect more general lecture around what kernel does exactly.||2||5||5||Boot sequence description, link with ARM ASM code, indications of what to optimize in hardware to help the OS||2||Memory management||how to submit patches to Linus Torvald||Not applicable - My management made the decision||Course recommended by previous participants||Not interested||5||5||very useful on the specific topic of kernel drivers but not really useful for my day to day work||Some parts were just copying text from labs instructions to our editor, some others were a bit too difficult (special tip around making private data visible for example)||3||3||From less than 100 km / 60 miles|
|11/4/2013 9:54:23||3||Very condensed training, which is was I appreciated. I did not have the feeling to loose my time.||My objective was mostly to learn about Linux internals, not really the drivers. I think it was fully met, as showing the drivers helps to go deeply inside the kernel core while still being able to do labs, and so have a dynamic training.||5||And open source (Freely available from the web)||5||5||5||5||5||The
original training was on 5 days. Because we have enough initial
knowledge (using linux, CPU hardware...), shortening it on 4 days was
the best to do.|
We already sent feedback to the trainer that it would be even more useful for us to add some modules about more linux internal parts: memory management, scheduling, etc.
|4||I learned quite a lot especially about Linux sources: where to find the code, how to look for a specific function, how it is organized.||4||It was known that it would not be immediately useful. Anyway, I will certainly use it to compile a new kernel when required, or to look at specific functions.||7||1||It's enough for the moment.||5||Some modules in the last day were not very useful: Linux on ARM, debugging Linux and could be replaced by internals of Linux. Anyway the instructor went very quickly on these modules.||Open training materials that can be checked in advance, Access to full feedback from participants to previous sessions, Not applicable - My management made the decision||Course recommended by previous participants||Not interested||5||5||They permit making a very dynamic training. We would sleep very quickly without the labs.||Interesting, short, and permit to put the lectures into practice.||3||3||From less than 100 km / 60 miles|
|11/5/2013 10:23:11||4||4||5||4||5||5||5||3||4||6||5||I'd like something more involved regarding kernel internals and driver development.||4||Not applicable - My management made the decision||Free Electrons chosen by my management||Not interested||5||4||1||5||From less than 100 km / 60 miles|
|11/5/2013 10:23:35||4||3||Need more practical and explained examples.||3||3||4||4||4||4||1||5||4||3||Basic introduction to drivers||Frameworks||Not applicable - My management made the decision||Free Electrons chosen by my management||Board Support Package development: make Linux / Android support your new hardware, Real-time: implementation and bug fixing||5||4||Training
labs probably too much directed. Labs a bit less directed but with more
time to do them. This would be better to fully understand what we are
Currently we are able to complete most of the trainings without having fully understood what's going on.
|3||4||From less than 100 km / 60 miles|
|11/5/2013 10:41:01||3||5||Excellent material.||4||3||4||5||4||4||3||5||3||Very good material, excellent labs, a lot of fun and profit.||4||Trainer, Open training materials that can be checked in advance, Language||Course recommended by previous participants||Not interested||4||5||3||3||From less than 100 km / 60 miles|
objective was to learn more about the HW implications induced by an
Operating System (in this case Linux), while he course was more focused
on developping drivers alongside the Linux kernel.|
So there is no direct implication of the course to my day to day job.
Now, I really _liked_ attending this course, I did learn a lot.
|5||4||Extremelly knowledgeable on driver development.|
Maybe lacked a bit of knowledged on the kernel itself, but since it was not the gal of the course...
|4||Very good, even if the course was in english.||4||5||5||5||2||6||4||A session on the kernel itself, on the run time environment, on the memory management, scheduler, etc...||3||Not applicable - My management made the decision||Free etc...||Power management||5||4||With the same caveat: useful for learning on driver dev, not on the kernel or on OS in general.||3||4||Maybe a bit too much time compared to going into more details on "why" things were implemented that way.||From less than 100 km / 60 miles|