Difference between revisions of "Embedded linux status"

From eLinux.org
Jump to: navigation, search
(Septemeber 2013)
(September 2013)
Line 57: Line 57:
 
==== general ====
 
==== general ====
 
* Valve launches SteamOS
 
* Valve launches SteamOS
 +
* Good boot time presentation: http://www.slideshare.net/righiandr/linux-boottime-23817352
 +
 
==== graphics ====
 
==== graphics ====
 
* Nvidia helps with Nouveau effort: http://lwn.net/Articles/568038/
 
* Nvidia helps with Nouveau effort: http://lwn.net/Articles/568038/

Revision as of 21:15, 30 September 2013

Here is an outline for a presentation on the status of embedded Linux:

This is essentially Tim Bird's private collection of interesting notes about the status of embedded Linux. It tends to get updated right before a Linux conference.

NEWS: Tim Bird's Status of Embedded Linux (PDF) (February 2012) presentation from ELC 2012 is now available.

Process for adding information

Anyone can add information to this page. I used to maintain the information at the Technology Watch List, but the table format there is a bit constrictive. (It would be nice if MediaWiki had a table editor!!)

Since I have to form this stuff into a "State of Embedded Linux" presentation several times a year, keeping the information in wiki outline format is convenient for me. It's easier to put directly into a presentation.

Please place information in bullet form, with a link to a supporting article, in the appropriate sub-section below.

Page History

I'll let MediaWiki store historical versions of this page. If you want to see what the hot issues were from a last year or a few years ago, please see look at the page history. (Although, updates of this page have historically been a bit spotty).

Presentation History

Here's my presentation history:

Uncategorized info

This is where I put stuff I haven't had time to analyze or sort into the appropriate category:

September 2013

general

graphics

device tree pain

Linus quote about undiscoverable busses: https://lkml.org/lkml/2013/9/10/366

"Ok. I still really despise the absolute incredible sh*t that is non-discoverable buses, and I hope that ARM SoC hardware designers all die in some incredibly painful accident. DT only does so much.

So if you see any, send them my love, and possibly puncture the brake-lines on their car and put a little surprise in their coffee, ok?"

what's coming next

  • transactional memory
  • non-volatile main memory
  • mirasol (color reflective displays)
    • qualcomm watch
  • wearables
    • watches from everyone (Samsung, Sony, Qualcomm)
  • modular pieces (mix-and-match)
    • Example: Sony QX cameras

cpu announcements

  • quark
  • SOC standings:
    • Intel, Qualcomm, MediaTek, NVidia, Samsung, Broadcom
    • GPUs: Mali (Intel, from ARM), Adreno (qcom, Radeon from ATI), PowerVR (Imagination), Intel's own GPU, Videocore (broadcom, from Alphamosaic)

July 2013

February 2012

  • lttng 2.0 was in mainline for about 2 weeks
    • CTF exists, as well as babeltrace
    • babeltrace (library for trace conversion) exists, but has no serious converters yet
    • TMF (eclipse viewer) support for CTF coming real soon (if not already) (was predicted to be January 2012)
    • TMF support for LTTng 2.0 planned for q2 2012

May 2011

Quote:

LinuxFR : What is your opinion about Android ? Are you mostly happy they made cellphones very usable or sad because it's really a kernel fork ?

Linus Torvalds : I think forks are good things, they don't make me sad. A lot of Linux development has come out of forks, and it's the only way to keep developers honest - the threat that somebody else can do a better job and satisfy the market better by being different. The whole point of open source to me is really the very real ability to fork (but also the ability for all sides to then merge the forked content back, if it turns out that the fork was doing the right things!)

So I think the android fork forced the mainline developers to seriously look at some of the issues that android had. I think we've solved them in mainline, and I hope (and do think) that android will eventually end up merging to mainline. But it will probably take time and further effort.

I think the more serious long-term issue we have in the kernel is the wild and crazy embedded platform code (and mostly ARM - not because ARM is in any way fundamentally crazier, but because ARM is clearly the most successful embedded platform by far). The embedded world has always tended to eschew standardized platforms: they've been resource constrained etc, so they've done very tailored chip and board solutions, and felt that they couldn't afford a lot of platform abstraction.

That causes a big maintenance headache, because then all those crazy platforms look slightly different to the kernel, and we have all that silly code just to support all those variations of what is really just the same thing deep down, just differently hooked up and with often arbitrary small differences.

But that's something that happens both within and outside of Android, it's in no way android-specific.

LinuxFR : What about the technical differences between Android and mainline ? Do you think the "wakelock" controversy is solvable ?

Linus Torvalds : I think it is technically largely solved (ie "details to be fixed, but nothing fundamentally scary"), but practically once you have an interface and existing code, it just is a fair amount of work to change. And there perhaps isn't quite enough motivation to make those changes very quickly. So it will take time, and probably several releases (both mainline and adroid) to actually happen.

LinuxFR : Can you explain why you're not happy with the ARM patches sent to you during merge windows ? Is there an obvious solution for this fragmentation problem ?

Linus Torvalds : Obvious solution? No. The problem is the wild variety of hardware, and then in many cases the Linux ARM platform code (not the ARM CPU support, but the support for certain chips with all the glue issues around the CPU core) has been mostly ugly "copy-and-paste" from some previous ARM platform support file, with some minimal editing to make it match the new one.

And it just results in this unmaintainable mess. It becomes painful when somebody then fixes some core infrastructure, and you end up with a hundred different ARM files all using that infrastructure. That happened with the IRQ chip driver cleanups Thomas did recently (well, has been doing over along time, the recent part is really just the final removal of some nasty old interfaces).

It results in other maintainability issues too - patches being big just means that people won't look at them as carefully etc etc. So it's just a bad situation. Many of the cases should be solvable by having better generic solutions and then plugging in just some per-platform numbers for those solutions.

April 2011


Other

  • CONFIG_PM being eliminated - improved PM configuration
  • ftrace using -mfentry (feb 9, 2011 lkml, steven rostedt)


April 2010


Previous to April 2010

  • SystemTap 1.0 now includes support for cross-compilation.
  • Patches for dynamic printks
  • writing to /dev/kmsg to generate a printk (not new, but I just discovered it)
  • LZO kernel compression is in 2.6.33
  • Arjan van de Ven's timer-slack code - http://lwn.net/Articles/369361/

Kernel

Kernel Versions

Bootup Time

  • U-boot bootgraph.pl support (see e-mail from Andrew Murray)
  • Android has problems
    • many people are addressing it with Snapshot boot
  • readahead is getting lots of attention
    • See Tim's presentation on Android boot time with readahead
  • snapshot boot (see above)
    • See ELC 2010? and ABS 2011 presentation on snapshot booting
  • embedded bootchart
    • busybox bootchart
    • bootchart in Android init
    • bootchart2 project
      • C collector, python visualizer
  • filesystem speedups
    • CELF funding UBI logging
    • CELF funding read-only block filesystems on flash (MTD)
  • XIP
    • Almost removed from kernel
      • versions in kernel were broken, use of XIP on out-of-tree platforms doesn't help keep XIP in the tree

Bootloader

Memory Management

  • anything new happening?

Power Management

  • suspend blockers? (aka wakelocks)
  • device PM

then and now

2003 - wanted:

  • operating points
  • frequency scaling
  • tickless idle
  • device pm

2011 - have:

  • tickless idle
  • device pm
  •  ???

System Size

  • CELF reviving Linux-tiny project
  • bloatwatch is still running, but who looks at it?
  • Xi Wang's talk at ELC about optimizing memory usage throughout system (kernel, libs, application)
  • OOM killer - dealing with memory pressure:
    • [RESEARCH: OOM killer news]
    • Android has its own thing
    • cgroup memory notifications

then and now

2003 - wanted (shrink kernel to ???k) 2011 - current size = ?

  • see bloatwatch
  • growth is in user space
  • compare with platform size growth over same period

Security

  • virtualization for Android
    • Samsung using vmware for Android (to separate personal and business use of phone)
  • Android and attacks
    • Android has different security
    • has there been a root exploit from a java app?

then and now

2003 - wanted trusted root (TPM), guard against exploits 2011 - have??

File Systems

  • YAFFS2
    • Mainline effort by Charles Manning
  • LogFS
    • Joern disappeared again
  • Squashfs
    • Now supports LZMA2 in mainline
    • CELF funding SquashFS on MTD work
  • Arnd Bergmann's work on optimizing Linux FS for cheap flash media
    • See ELC presentation and Linaro page
  • Tim Bird's treadahead work
    • See ABS presentation

Legal Issues (licensing and patents)

  • mobile patent wars
    • Google buys Motorola for patent portfolio
    • Apple blocks Samsung tablet introduction in Europe

Graphics

  • OpenGL ES
  • whither fbdev?
  • 2D - Android doesn't have a native 2D API (or it's changing?)
    • [RESEARCH - did Android drop it's native 2D API? (skia?)]
  • GoogleTV 1.0 (logitech and Sony) use Sodaville, which is an Atom with a SGX535 core



  • Intel work on graphics in kernel:
    • See Kieth Packard's video from September 2010: [Meego Graphics under the hood: http://www.youtube.com/watch?v=YRYTCQqrFcA] OSCON 2010
    • Working on grphics KMS and DRI in the kernel
      • good for faster booting
      • good for less flicker on transitions
      • higher performance 3d graphics
      • better memory management
        • kernel can pull memory back from graphics processor on low-memory conditions
          • [RESEARCH - status of memory allocation discussions at ELC?]
      • per CRTC pixmaps
        • allows for zero-copy rotations
        • support for larger screens
      • support for multiple screens
      • wayland (non-X-windows)
        • moving away from X on Meego
        • support for multiple APIs
      • EGL
      • OpenGL 2.1 supported now, OpenGL 3.0 support coming soon
        • geometry shaders, tesselation
      • architecture:
user space: Open GL   (compiler for shaders)
             mesa
             i915 driver
-------------------------------
graphics interface (is not opengl, but a device-specific abstraction)
-------------------------------
kernel space: DRI
              i915 driver

kernel space driver is a small driver Combination of DRI and GPU-specific driver is called the Graphics Execution Manager (GEM)



    • ABS Khronos standards talk? (no slides available)

Audio

Multimedia

  • GStreamer - held first ever GStreamer conference in October (co-located with ELC Europe)
  • Khronos is working on their stuff

Embedded-specific features

infrared remote control support

Middleware

  •  ???

Tools

Debuggers

build systems

  • OpenEmbedded/Poky (Yocto is umbrella project)
    • Appears to be gaining momentum - lots of companies (including Sony) using it now
    • lots of new interesting features: graphical tool, can build an image for self-hosting a build, new compatibility badging program for meta-data
    • Will provide LTSI kernels as part of offering


Tracing

  • Common Trace format
    • 2011 - lttng is shipped by most major distros (including yocto)
    • 2011 - would be nice to get in Android?

Toolchains

eclipse stuff

  • Yocto uses CDT remote launch, org.eclipse.cdt.launch.remote and TCF file/shells to transfer binaries and launch applications
    • CDT = (C Development Toolkit)
    • See: http://www.yoctoproject.org/projects/eclipse-ide-plug
    • support communication with emulator or real device, via Yocto Eclipse TCF
    • emulated devices use NFS rootfs so host and target access same filesystem
    • debugging is via cross-gdb (gdbserver and gdb client on host)

emulators

Contract Work

  • eMMC tuning guide - should be published in January
    • Is coming along nicely
    • has explanations about benchmarking, analysis of different tunable items in the filesystem stack
    • has lots of results testing the following filesystems: ext3/4, BTRFS, F2FS, with different I/O schedulers (including the new ROW I/O Scheduler)
    • has specific suggestions for what options are most effective to tune your filesystem, based on the characteristics of your flash device

Distributions

  • Poky or Angstrom (OpenEmbedded/Yocto Project)

Distribution tools

Mobile Phone distros

Android

  • Tablets
    • Some nice tablets based on 3.0 are coming out (will move to Android 3.1 over summer)
  • phone activations? (350,000 per day, as of April 8, 2011)
  • GoogleTV
    • Every device will have 3.1 and adb, which means every device can be used for development
    • will have market
    • good talks at Google I/O about app and web development for TVs

Unbuntu TV

CPU support

Chip vendor news

  • Texas Instruments leaves mobile and tablet market
    • November 2012, announces layoffs of 1700, drops future OMAP lines

Miscellaneous

  • unlockable bootloaders
    • Announced by Motorola and Sony/Ericsson
    • can unlock bootloader to install custom firmward
    • wipes the phone to remove DRM-protected content
    • Motorola says you can re-lock by going back to a vendor-supplied image
  • version update support
    • Announced at Google I/O
    • multiple partners agree to provide version updates at regular intervals

Industry organizations or projects

  • LiMo - anything happening?
  • CELF => CEWG under Linux Foundation
    • CELF projects
  • Linux Foundation
    • Lots of stuff going on in embedded:
      • Yocto
      • Meego
      • CE Working Group
  • Linaro - 1 year in
    • see David Rusling's presentation from ELC

Trends

  • movement to eclipse (both Yocto and Android support eclipse plugins for tools)
  • movement to emulators
  • application portability
    • Android apps will be able to run just about anywhere
    • Will an IOS emulator appear, or will apple strangle any attempts
  • application stores
    • multiple app stores will create competition (good)
  • more open platforms
    • Google TV
  • lots of stuff that no one expects will appear
  • development trends:
    • new tools??

Resources

  • lwn.net
  • elinux.org
  • stackoverflow.com
  • kernelnewbies
  • linuxfordevices.com