Thanks for the comments. Just to explain myself a bit.
-- Conferences ---
As we're consolidating ARM contributions, we're also pushing at various bits of kernel infrastructure, the memory management stuff, for example. To do the right thing (i.e., end up with the right code in the kernel) we need agreement from a wide range of open source communities (kernel, multimedia, video etc). Going to many, many kernel conferences is not terribly efficient.
I think that this is a scaling problem for the Linux kernel engineers; what forums make sense to attend in order to agree designs, code, directions? Whilst presentations are good for bootstrapping knowledge, I'm more interested in technical decisions being made. Linux plumbers is one such conference, but only happens once a year. Whilst Vancouver was good, it could have been better.
--- Embedded ---
For me, traditional embedded is low memory, tight timings. Disk controller fits pretty well. Thinking of ARM as embedded is limiting, as it is no longer just embedded. Thinking of ARM as just another architecture is also misleading, because the drivers and business models are fundamentally different.