|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||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 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?|
|11/6/2015 0:58:22||5||5||5||5||5||3||3||4||4||5||3||4||I liked the lab sections the most and learnt a lot from the hands-in experience.||Not applicable - My management made the decision||Free Electrons chosen by my management||Development of real-time systems, Build environment support, Root filesystem development, Bug fixing||3||5||4||3||From less than 100 km / 60 miles|
|11/6/2015 1:00:01||3||4||5||4||5||3||4||3||4||5||5||4||Not applicable - My management made the decision||Free Electrons chosen by my management||Not interested||5||5||3||3||From less than 100 km / 60 miles|
|11/6/2015 1:04:16||3||4||5||4||5||3||3||first day is too packed. Third day is too loose.||3||4||5||it'd be useful if the instructor can walk through some real code sections when giving examples.||3||networking?||4||Not applicable - My management made the decision||Internet search engines||Development of real-time systems, Technology and architecture consulting||3||5||3||3||From less than 100 km / 60 miles|
|11/7/2015 0:50:38||3||To our usecase, I think the duration was perfect. Five days would have been too long.||5||5||Usually trainers come with long of theoretical background with no practical knowledge (Eg., school). On the other hand, Engineers tend to have too much practical knowledge but not enough theoretical foundation. Maxime provided the right balance of theoretical and practical knowledge.||4||5||5||4||Again for our use case, it was good to have the labs on the 4th day with lectures on 3rd day. Even though this made the lectures a bit confusing, it was lot more useful when we were doing the labs. Each step was clear as how to why it needed to be done in a certain way.||5||4||6||Some additional info on packet flow/network stack/network drivers would be interesting.||4||4||Driver registration|
|Power management||Availability for on-site sessions, Open training materials that can be checked in advance, Cost||Free Electrons chosen by my management||Root filesystem development, Technology and architecture consulting||5||4||3||4||From less than 100 km / 60 miles|
|11/7/2015 1:15:08||3||I explain below when talking about labs.||4||5||4||3||4||4||3||3||5||I think the key point for these courses is to gain practical experience so it might be better to address labs after covering (deeply) some topic instead of going further with the theory, even if that means not covering so much theory.||3||3||Explanations of different frameworks and how they all can fit together. Device Tree. Porting to another arch.||Introductory topics already known.||Not applicable - My management made the decision||Technical resources on the Free Electrons website||Not interested||I think labs should be more guided and interactive, going through every lab to analyze it and solve it in group instead of letting everyone to go by themselves and ask when needed.||4||4||They would have been more useful making sure everyone understood the labs completely. Discussing in group would add more value to the labs, sharing everyone's knowledge.||3||2||One thing is to understand some theory, other is to be able to code all the necessary stuff to make a driver work and understand the internals. That would need more time that allotted.||From less than 100 km / 60 miles|
|11/8/2015 0:20:10||3||It is hard to judge this without actually applying the knowledge to figure out what needn't have been covered or what else should have been covered. It seemed quite comprehensive.|
I know that it is tricky to balance basic operating system concepts and how they are implemented in the Linux kernel. I felt like the biggest weakness was not being clear when one or the other was being described. Within Linux, how things are connected in real life (like what fields in device trees must be the same to connect the device tree to the driver code) were unclear to me.
|4||I often found myself reading ahead and referring back to it.||4||The instructor seemed to know the material very well.||4||The instructor's experience and comfort level with the material was very clear.||2||3||4||3||3||5||3||3||Not applicable - My management made the decision||Internet search engines||Not at the moment||I felt the labs were often more of a "do it yourself" and we could ask the instructor for help if we needed it. Problems encountered by one group were not communicated to other groups.||3||4||They took the information from the lectures and made them applicable. I felt that switching between lecture and lab more frequently would have been more useful (apply what we just learned instead of what we learned yesterday).||"Too difficult" isn't quite the right term. I often felt like it gave very explicit instructions at one point and at another would instruct us to do something very generic that wasn't covered in the lab document or the lectures.||4||2||I felt like we got through about 2/3 of the labs in the time alotted.||From less than 100 km / 60 miles|
|11/9/2015 22:09:34||3||5||4||3||4||5||5||5||5||5||1||5||Not applicable - My management made the decision||through co-workers||Not interested||5||5||3||3||From less than 100 km / 60 miles|
|11/10/2015 1:09:20||4||I've been working on linux kernel long enough to know "basic mechanics" and "programming patterns" used in the kernel.|
I was mostly interested in learning "Device tree", I2C API/operations, and how the two interact. That section of the class fully met my expectations.
Labs were good - plenty of "figure this out" and then getting the details "fixed" by reviewing the few bits that I'd done incorrectly with the instructor.
|5||5||A+++++ would hire again!!!!|
;) (for those of you who spend too much time on ebay)
|5||5||On Google premises....frigging awesome! :)||4||Lenovo Keyboard. That's all I'm going to say.|
Beaglebone and clone nunchuk were fine.
|4||4||5||6||3||Not at the moment - maybe in the future again as new needs come up.||4||Not applicable - My management made the decision||Technical resources on the Free Electrons website||Not interested||Mostly left people alone to work on the code and then was able to identify specific issues people were having fairly quickly and set them off in the right direction again.|
This happened twice for me:
1) kernel config wasn't quite correct - somehow picked up the wrong one.
(common error was running "make oldconfig" without specify "ARCH=arm ...". We guessed this was the case and when I rebuilt (after "make mrproper" and rebuilding the .config as per instructions, everything worked as expected.
2) added pinctl for nunchuk device to wrong section (one level too deep)
|5||3||Uh...sorry, I'm confusing "training labs" with "practical labs". I didn't notice there were two types of labs.||Sorry - confusing "training" and "practical" labs now.||3||3||From less than 100 km / 60 miles|