Some random comments:
- He's right about the Silicon vendors. Often they give you ugly and obsolete code. Usually
with major missing device drivers and completely lacking power management support. Ignore any
claims of "Linux support" from your silicon vendor. Instead, download the latest version from
kernel.org and look at the config options to know what the real state of things is.
- I disagree about following *any* lists. Why do embedded folks need to monitor lists any more
than desktop folks? Linux mostly "just works". When you find a problem, glance at the diffs
from a few versions forward, and hit google. If that turns up nothing, it's likely your fault.
- The main reason to "keep up" with the current kernel is device drivers. For embedded
systems, there are only a handful of drivers to worry about.
- Yes, sometimes you are faced with the 80K lines problem. I've had to backport drivers after
a networking subsystem API change. It's not the end of the world, and in the end I only had to
change 3 files (besides my driver).
- Embedded Linux rocks! I worked on a half-dozen custom ARM boards, and it usually took less
than a week bring up a board enough to start custom development.