• Cross-toolchains
  • Built, tested, validated and deployed cross-toolchains for each target
    • Environment: Linux – GNU compilation tools (gcc, binutils, glibc, uClibc…) – crosstool-NG – ARM, MIPS, x86 and SuperH CPUs
• Development infrastructure
  • Specified the Version Control System
  • Deployed and maintained a farm of build servers, geographically distributed in France and other countries
  • Developped, and maintained a build-system
  • Ported industrials SDKs to this infra-structure
  • Animated training sessions for use of the platform
  • The whole platform has been in use by 180+ developpers
    • Environment: Linux – subversion – scripts shell – Makefiles, autotools…

• Project hand-over
  • Acquired knowledge about the existing project
  • Upgraded software components
    • Environment: Linux – GNU compilation tools (gcc, binutils, glibc, uClibc…) – crosstool-NG – shell scripts – ARM CPU
• New service prototype
  • Specified the software architecture
  • Implemented the solution
    • Environment: Linux – GNU compilation tools (gcc, binutils, glibc, uClibc…) – crosstool-NG – shell scripts – gstreamer – ARM CPU
• Generic Hardware for Prototyping
  • Reviewed and suggested hardware components (CPU, RAM…)
  • Integrated an existing team
    • Environment: Linux – ARM CPU (with DSP + GPU) – USB – PCI

In this new position, I kept the activities of my previous position:

• Development environment:
  • Built and maintained the cross-toolchains
  • Specified parts of a platform for collaborative developments
  • Developped tools for this collaborative platform
    • Environment : Linux – GNU compilation tools (gcc, binutils, glibc, uClibc…) – subversion – shell scripts – MIPS CPU

• Integration, configuration, upgrades for software components
  • Defined critical parts of the distribution
  • Ported free and non-free drivers to Linux-2.6, from 2.4 and earlier 2.6
  • Integrated user-land FLOSS tools and libraries
  • Tested feasability in virtual machines
    • Environment : Linux – FLOSS tools – VMs (QEMU, UML) – MIPS CPU

• Migration of CPEs in the field
  • Reviewed the existing infrastructure
  • Wrote migration procedures
  • Specified the migration for the low-level software components
    • Environment : Linux – RedBoot – MIPS CPU – flash memory

• Support to the development teams
  • Listened to the needs of the development teams (in France and abroad)
  • Monitored performenace issues, analysed results
  • Specified and/or applied fixes and/or workarounds
  • Specified evolutions for the architecture of the distribution
    • Environment : Linux – ethernet – 802.11 – ADSL – PLT – MIPS CPU

• Development environment:
  • Built and maintained the cross-toolchains
  • Specified parts of a platform for collaborative developments
  • Developped tools for this collaborative platform
    • Environment : Linux – GNU compilation tools (gcc, binutils, glibc, uClibc…) – subversion – shell scripts – ARM Xscale CPU (IXP4xx)

• Integration, configuration, upgrades for software components
  • uClinux kernels (2.4.x series), Linux kernels (2.6 series)
  • Port of free and proprietary kernel drivers
  • Integration of many user-land libraries and utilities
    • Environment : Linux – FLOSS tools – Embedded targets – VMs (QEMU, UML)

• Port of the distribution to a new platform
  • Port of the Linux 2.6.17 Linux kernel
  • Port of the kernel drivers
  • Adaptation of the distribution
  • Tigh colaboration with the board manufacturer
    • Environment : Linux – FLOSS tools – ARM Xscale IXP465 – JTAG - PCI, USB and CardBus buses

• Migration process from the existing distribution to our own
  • Study of the existing distribution architecture
  • Process for the migration
  • Low-level software migration
    • Environment : Linux – RedBoot – MIPS CPU – flash memories

• Support to the development teams
  • Performance measurements, results analysis
  • Implement fixes (either corretive, or stop-gaps until a correct fix is done)
  • Enhance the distribution architecture
  • Constant interaction with the development teams
    • Environment : Linux – ethernet – 802.11 – ADSL – PLT

• Defect manager
  • Preliminary analysis
  • Dispatch, and follow-ups
  • Direct connection with the final client
    • Environment : ClearQuest – ClearCase – Rose – UNIX

• Specifications of major evolution in existing simulators
  • Specifications of the external interfaces
  • Port of the software previously develop on the validation test-bench
  • Integration with operational modules
  • Adaptation of the existing off-line software to be on-line and real-time
  • Port to a new hardware target
  • Transfer of the project knowledge to my succesor
    • Environment : ClearQuest – Objecteering – VxWorks, UNIX, WinNT – PowerPC CPU

• Port of simulator for 'missing' modules
  • UML modeling for the new simulation model
  • Specifications of the new simulator
  • Design of a new GUI
  • Tests, integration and validation at the client's site
  • Documentation
    • Environment : Objecteering – IlogViews – VxWorks – NT

• Minor evolutions for an exisiting simulator
  • Estimation for each evolution (feasibility and costs)
  • Specification of each evolution
  • Implementation and tests, then integration and validation at the client's site
    • Environment : Teamware – ClearQuest – Objecteering – IlogViews – VxWorks – NT

• Port to Linux of a driver for a digital telephony board
  • Self-training to RT-Linux
  • Drafting of the training materials
  • Study of the existing driver, and feasibility of the port
  • Direct contact with the board manufacturer
    • Environment : Linux – RT-Linux

• Coding of a test-software
  • Corrections and changes to the system specifications
  • Design and coding of a major feature (battery charging) and minor sub-systems
  • Hardening of the software
    • Environment : C167 Assembly – cross-compiler from Keith – ICE probe – CAN bus – Real-time XEC kernel

• Testing infrastructure
  • Definition of unitiary and non-regression tests
  • Design and implementation of tests on PC
  • Design and implementation of an automaton language
  • On-target and in-situ tests
  • Design of a GUI to display results
    • Environment : C++ – Visual Basic – NT – Visual Studio

• Configuration management
  • Review of different tools
  • Daily management of the VCS
    • Environment : PVCS – NT

• ELC-E – Embedded Linux Conference Europe
  • 2009, speaker: Building Our Own Toolchains For Our Embedded Projects: Why, and How To
  • 2010, speaker: Crosstool-NG, A Cross-Toolchain Generator
• FOSDEM – Free and Open Source Delveloppers' European Meeting
  • 2010, speaker: Introducing crosstool-NG, a (cross-)toolchain generator (off the cuff speach, not in the program)
  • 2010, co-speaker: Cross Build Systems: Present & Future, with: Robert Schwebel (Pengutronix), Peter Korsgaard (Buildroot)
• LSM – Libre Software Meeting
  • 2012, speaker: Introduction to cross-compilation

Support materials for these presentations are available.

• Re-write of a cross-toolchain generator
  • Main developper, maintainer
  • Repository of patches, collection of sample toolchains
  • Many components and components' versions
  • crosstool-NG website

• A packaging of the kconfig language
  • Centralised effort of keeping an up-to-date, out of the Linux source tree, packaging of the kconfig infrastructure
  • Packaging of the kconfig parser and the five usual frontends
  • Using the GNU atutools (autoconf, automake, libtool…)
  • Maintainer
  • kconfig-frontends website

• I've been for a time considered the maintainer of the modprobe applet:
  • BusyBox website

• A Fuse-based, in-Ram File System
  • In-RAM virutal file system
  • Design, coding
  • frfs website

• Targets: PDA/ARM, NAS/ARM, Gateway/MIPS, Tablets/x86
• Build and optimisation of cross-compilation toolchains
• Linux kernel ad-hoc configuration
• Reverse engineering (touch screen)

• Driving license (A/B: cars and motorcycles)
• Rock-climbing, mountain bike, skiing, other mountain-realted sports
• Improvisational theater, public performances
• Celtic music and choregaphy, public performances