Slimlogic Planet

Lucid on Omapzoom2

2010-04-19T10:15:40Z

So Ive been doing some work getting a Ubuntu Lucid beta image running on the zoom2 machine. This is basically the same image as what runs on a beagle slightly modded for zoom2 (serial is different port). Running the Netbook Remix version. I have two external keyboards and a mouse plugged in via usb hub and of course the debug board for networking. This is a photo so you can see it is really running

I used the kernel image that we use for Ångström images as Ubuntu doesn’t have a zoom2 kernel yet.

And this is a screen shot taken on the zoom2 (you’ll just have to believe me).

Omap3 Zoom2 Ångström

2010-02-11T20:28:58Z

I thought it was about time to give an update on Ångström support of the Omap3 Zoom2 device.

Thanks to TIs donation I have been able to work on support for this device. I have also been able due to the power of OE build on the Ångström communities support of omap3 chips in general. Anyway a Gnome rootfs is running nicely on the device.

Here is the login screen.

And after logging in the desktop running.

This as you can see is with the zoom2 running free of its debug board. This does mean with current OE recipes there is no networking but we are hoping to have that fixed soon now!

Multithreaded ALSA capture code with overrun debug

2010-02-03T14:09:47Z

I’ve been working on some ASoC multi channel capture drivers lately and was in need of a nice analysis tool to show PCM data throughput and PCM buffering information when writing to slow-ish asynchronous memory cards.

SoC memory card controllers tend to write data in asynchronous bursts and usually compete for SoC CPU IO resources with the audio subsystem. This competition for SoC IO resources between the audio and memory card subsystems can often lead to problems for audio. The two most common audio problems are :-

Audio Controller FIFO overruns.
Audio DMA buffer overruns.

Audio FIFO overruns are caused when the DMA controller cannot empty the audio FIFO before the next incoming audio PCM sample is shifted into the already full FIFO. This ultimately causes the FIFO to lose some audio PCM data and potentially also lose left+right channel alignment. FIFO overruns can be minimised by using the largest FIFO possible and by setting the FIFO DMA IRQ watermark to a value that can tolerate high latency. This should be done by the driver and may depend on number of channels capture and rate.

Audio DMA buffer overruns can be caused when any userspace process reading (capturing) the PCM audio data from the ALSA driver does not manage to completely read the data (from the DMA circular buffer) before it is overwritten by new new data (by the DMA). DMA buffer overruns can be mostly eliminated by making sure our capture program can read from the ALSA driver without any hinderance. This can be achieved by having separate reader and writer threads.

I’ve posted some example ALSA multi threaded capture code here. It’s by no means complete and is a little rough around the edges but should be helpful to anyone debuging overrun or buffering issues. It can be built as follows:-

gcc capture.c -lasound -o capture

The program will capture audio data from the default ALSA device until it receives a CTRL-C signal where it dumps the buffering usage data.

ARM Cortex A9 Angstrom Console Image and Tool Chain

2010-01-22T18:13:17Z

I’ve now managed to successfully build an Angstrom Linux console image and cross gcc tool chain for the ARM Cortex-A9 CPU found on some newer SoC boards. Although unfortunately I’ve not yet had a chance to test this image yet as I’m waiting on the delivery of my new Cortex A9 hardware.

The angstrom-2008.1.conf binutils, gcc and glibc versions used are
PREFERRED_VERSION_glibc ?= "2.10.1" PREFERRED_VERSION_glibc-initial ?= "2.10.1" ANGSTROM_GCC_VERSION_armv7a ?= "4.4.2" ANGSTROM_BINUTILS_VERSION_armv7a ?= "2.20"

Whilst the CPU tuning for Cortex A9 is
# Instead of using -mfpu=vfp[2] we can use -mfpu=neon to make use of gcc intrinsics[1] and vectorize loops with -ftree-vectorize[3] # [1] http://gcc.gnu.org/onlinedocs/gcc/ARM-NEON-Intrinsics.html # [2] http://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html # [3] https://support.codesourcery.com/GNUToolchain/kbentry29

TARGET_CC_ARCH = "-march=armv7-a -mtune=cortex-a9 -mfpu=neon -mfloat-abi=softfp"
FEED_ARCH = "armv7a"
PACKAGE_EXTRA_ARCHS += "armv4 armv4t armv5te armv6 armv7 armv7a"
BASE_PACKAGE_ARCH = "armv7a"

All the Openembedded files required to build this too chain and image are available via git in the SlimLogic OE omap4 branch.

The repository URL is git://git.slimlogic.co.uk/oe.git for anyone interested in adding it as a remote.

OpenEmbedded/Ångstöm New Package Workflow (eggdbus)

2010-01-22T00:23:32Z

This article is to detail the typical workflow I use when I am adding a new application recipe to OpenEmbedded from scratch. In this case it will be the gobject dbus binding called eggdbus.

During this article reference to the OE wiki especially the styleguide for new recipes is highly recommended.

The first step is to locate the software we are going to add and the version number of that software. In this case it the software is called eggdbus and it is version 0.6. Also at this stage check the license of the software in this case GPLv2.

Create a directory in the metadata to hold the new software.

mkdir recipes/eggdbus

Use an editor to create the recipe file for the new application. The general form of the filename is application_version.bb so in this case edit.

vi recipes/eggdbus/eggdbus_0.6.bb

Fill the beginning of the recipe with the informational fields.

DESCRIPTION = "gobject dbus binding" HOMEPAGE = "http://cgit.freedesktop.org/~david/eggdbus" LICENSE = "GPLv2"

The next step is to locate the download URL for the new recipe. In this case eggdbus is hosted in a sourceforge project so the download URL is.

http://cgit.freedesktop.org/~david/eggdbus/snapshot/eggdbus-0.6.tar.bz2

OpenEmbedded creates a variable ${PV} from the filename of the recipe. It is recommended to use this in the SRC_URI as it saves typing when later upgrading to later versions of the software. It also creates a ${PN} variable from the package name.

SRC_URI = "http://cgit.freedesktop.org/~david/${PN}/snapshot/${PN}-${PV}.tar.bz2"

At this stage there is enough recipe to attempt a download and check that there are no mistakes so far.

bitbake eggdbus

This build is expected to fail as the OE metadata does not yet have the MD5/SHA256 checksums for the download yet.

NOTE: Missing checksum ERROR: eggdbus-0.6: http://cgit.freedesktop.org/~david/eggdbus/snapshot/eggdbus-0.6.tar.bz2 has no checksum defined, cannot check archive integrity ERROR: Error in executing: /home/dp/openembedded/org.openembedded.dev/recipes/eggdbus/eggdbus_0.6.bb ERROR: Exception: Message:1 ERROR: Printing the environment of the function ERROR: Error in executing: /home/dp/openembedded/org.openembedded.dev/recipes/eggdbus/eggdbus_0.6.bb ERROR: Exception: Message:1 ERROR: Printing the environment of the function ERROR: Build of /home/dp/openembedded/org.openembedded.dev/recipes/eggdbus/eggdbus_0.6.bb do_fetch failed

OE helpfully generates the checksums it expected to see so these can be added to the meta data easilly. The cat just appends the new checksum to the end of the file. The next python command then calls a script to sort the checksums into the recommended format.

cat tmp/checksums.ini >>~/oe/org.openembedded.dev/conf/checksums.ini python contrib/source-checker/oe-checksums-sorter.py -i conf/checksums.ini

To check this worked then re-issue the bitbake command.

bitbake eggdbus

In this case the command will succeed but builds no useful package. Depending on the application it will probably fail. This is not a problem at this stage as it is still work in progress and debugging these failures is what gives the information for the rest of the recipe.

At this stage the contents of the tarball file can be checked. The eggdbus tarball unpacks to a directory which is called eggdbus-0.6 which is what OE has already selected by default so we dont need to overide the default ${S} setting.

Eggdbus is an autotools using library so we tell OE to use its built in autotools support. If it is a well written autoconf then OE generates configure/compile/install tasks which work without modification.

inherit autotools

We can now try a build again to see if it will just build(tm).

In this case it doesnt because of gtk-doc.make. We currently dont really support this in OE anyway so we shall attempt to patch out this part.

cd tmp/work/armv7a-angstrom-linux-gnueabi/eggdbus-0.6-r0/eggdbus-0.6/ quilt new gtk-doc.patch quilt add docs/eggdbus/Makefile.am docs/tests/Makefile.am

Edit the two Makefile.am and remove the reference to gtk-doc.make. Then generate the patch.

quilt refresh

The patches/gtk-doc.patch is now our patch. We need to copy it into our OE repo and add it to the SRC_URI.

mkdir recipes/eggdbus/files/ mv patches/gtk-doc.patch recipes/eggdbus/files/

And edit the eggdbus_0.6.bb to add the new patch to the SRC_URI.

SRC_URI = "http://cgit.freedesktop.org/~david/${PN}/snapshot/${PN}-${PV}.tar.bz2 \ file://gtk-doc.patch;patch=1 \ "

Now we attempt to build again.

bitbake eggdbus -c clean bitbake eggdbus

This time the build fails inside the code stage, if the error is examined it will show that the build is trying to run a built program on the host. This obvously won’t work in cross compile situations so the program needs to be compiled for host.

This means a native version of the package is created. This used to mean a seperate .bb file but thanks to BBCLASSEXTEND it can be done in one file. This also means SRC_URI must be altered to use ${BPN} (Base Package Name) which is a version with -native/-sdk stipped from the end if present. So the following is changed/added to .bb file.

SRC_URI = "http://cgit.freedesktop.org/~david/${BPN}/snapshot/${BPN}-${PV}.tar.bz2 \ file://gtk-doc.patch;patch=1 \ "

BBCLASSEXTEND = "native"

On attempting to build this new native file it failed because it tries to use docbook to generate man pages. We dont really need them so disable them.

EXTRA_OECONF = " --disable-man-pages --disable-gtk-doc-html "

Now a rebuilt of eggdbus-native succeeds and host versions of the tools needed are available in the staging directory. Now some more changes are needed to the source. In the Makefile.am the programs we just built are referenced using the source directory but the ones in staging should be used so another patch to the Makefile.am files is produced. This patch should apply to the native version so more changes to recipe are needed.

BASE_SRC_URI = "http://cgit.freedesktop.org/~david/${BPN}/snapshot/${BPN}-${PV}.tar.bz2 \ file://gtk-doc.patch;patch=1 \ " SRC_URI = "${BASE_SRC_URI} \ file://marshal.patch;patch=1 \ " SRC_URI_virtclass-native = "${BASE_SRC_URI}"


Now the eggdbus recipe is built.


bitbake eggdbus -c clean

bitbake eggdbus


This time the build succeeds, but one thing that isnt done yet is to tell OE what this recipe depends on. The trick used to do this is to examine the control file in the .ipk and see what is depended on.
For this recipe it is quite clear and dependencies on dbus glib. So a final change to the recipe to add dependencies.


DEPENDS = "dbus glib-2.0"


All these steps give up a complete recipe that reads as follows.


DESCRIPTION = "gobject dbus binding"

HOMEPAGE = "http://cgit.freedesktop.org/~david/eggdbus"

LICENSE = "GPLv2"




DEPENDS = "dbus glib-2.0"




BASE_SRC_URI = "http://cgit.freedesktop.org/~david/${BPN}/snapshot/${BPN}-${PV}.tar.bz2 \

          file://gtk-doc.patch;patch=1 \

          "




SRC_URI = "${BASE_SRC_URI} \

           file://marshal.patch;patch=1 \

          "




SRC_URI_virtclass-native = "${BASE_SRC_URI}"




inherit autotools




EXTRA_OECONF = " --disable-man-pages --disable-gtk-doc-html "




BBCLASSEXTEND = "native"



test blog post
2010-01-20T20:55:53Z
test


Test Post
2010-01-15T20:27:12Z
Testing RSS


OpenEmbedded/Ångstöm New Package Workflow (eyeOS)
2009-12-10T18:57:29Z
This article is to detail the typical workflow I use when I am adding a new application recipe to OpenEmbedded from scratch. In this case it will be the open source cloud computing application called eyeos.
During this article reference to the OE wiki especially the styleguide for new recipes is highly recommended.

 Styleguide
 Commit Policy
 Versioning Policy

The first step is to locate the software we are going to add and the version number of that software. In this case it the software is called eyeos and it is version 1.8.7.1. Also at this stage check the license of the software in this case AGPL3.
Create a directory in the metadata to hold the new software.
mkdir recipes/eyeos
Use an editor to create the recipe file for the new application. The general form of the filename is application_version.bb so in this case edit.
vi recipes/eyeos/eyeos_1.8.7.1.bb
Fill the beginning of the recipe with the informational fields.
DESCRIPTION = "The Open Source Clouds Web Desktop"

HOMEPAGE = "http://eyeos.org/"

LICENSE = "AGPL3"



The next step is to locate the download URL for the new recipe. In this case eyeos is hosted in a sourceforge project so the download URL is.
http://sourceforge.net/projects/eyeos/files/eyeos/1.8.7.1/eyeOS_1.8.7.1.zip/download
OpenEmbedded actually has sourceforge mirror handling build in. So when the SRC_URI is constructed for the reciped a shortcut can be taken. OpenEmbedded also creates a variable ${PV} from the filename of the recipe. It is recommended to use this in the SRC_URI as it saves typing when later upgrading to later versions of the software. It also creates a ${PN} variable from the package name. But in this case this is not used as it differs in case in the URL.
SRC_URI = "${SOURCEFORGE_MIRROR}/eyeos/eyeOS_${PV}.zip"
At this stage there is enough recipe to attempt a download and check that there are no mistakes so far.
bitbake eyeos
This build is expected to fail as the OE metadata does not yet have the MD5/SHA256 checksums for the download yet.
NOTE: Missing checksum

ERROR: eyeos-1.8.7.1: http://downloads.sourceforge.net/eyeos/eyeOS_1.8.7.1.zip has no checksum defined, cannot check archive integrity

ERROR: Error in executing: /home/graeme/openembedded/org.openembedded.dev/recipes/eyeos/eyeos_1.8.7.1.bb

ERROR: Exception: Message:1

ERROR: Printing the environment of the function

ERROR: Error in executing: /home/graeme/openembedded/org.openembedded.dev/recipes/eyeos/eyeos_1.8.7.1.bb

ERROR: Exception: Message:1

ERROR: Printing the environment of the function

ERROR: Build of /home/graeme/openembedded/org.openembedded.dev/recipes/eyeos/eyeos_1.8.7.1.bb do_fetch failed

ERROR: Task 2 (/home/graeme/openembedded/org.openembedded.dev/recipes/eyeos/eyeos_1.8.7.1.bb, do_fetch) failed

NOTE: Tasks Summary: Attempted 445 tasks of which 444 didn't need to be rerun and 1 failed.

ERROR: '/home/graeme/openembedded/org.openembedded.dev/recipes/eyeos/eyeos_1.8.7.1.bb' failed
OE helpfully generates the checksums it expected to see so these can be added to the meta data easilly. The cat just appends the new checksum to the end of the file. The next python command then calls a script to sort the checksums into the recommended format.
cat tmp/checksums.ini >>~/oe/org.openembedded.dev/conf/checksums.ini

python contrib/source-checker/oe-checksums-sorter.py -i conf/checksums.ini


To check this worked then re-issue the bitbake command.
bitbake eyeos
In this case the command will succeed but builds no useful package. Depending on the application it will probably fail. This is not a problem at this stage as it is still work in progress and debugging these failures is what gives the information for the rest of the recipe.
At this stage the contents of the zip file can be checked. The eyeos zip unpacks to a directory which is called eyeOS which is different from OEs guessed at directory of eyeos-1.8.7.1 so the recipe needs updated to tell OE the real directory.
S = "${WORKDIR}/eyeOS"
Being a web application eyeOS doesnt have Makefile or autotools based installation so the compile/install stages will have to be hand written for this recipe.
The eyeOS installation is really simple from the OE point of view.
do_install() {

    install -d ${D}/www/pages/eyeos

    cp -r ${S}/* ${D}/www/pages/eyeos

}
There are two final things to do now before the recipe is finished. OE needs to be told which directories to package. It has some built in defaults like /bin /usr/bin /lib /usr/lib but our eyeOS install is outside these areas. We also need to tell OE that there is no CPU dependant code in the packages this recipe generates.
PACKAGE_ARCH = "all"

FILES_${PN} += "/www/pages/eyeos"
All these steps give up a complete recipe that reads as follows.
DESCRIPTION = "The Open Source Clouds Web Desktop"

HOMEPAGE = "http://eyeos.org/"

LICENSE = "AGPL3"




SRC_URI = "${SOURCEFORGE_MIRROR}/eyeos/eyeOS_${PV}.zip"




S = "${WORKDIR}/eyeOS"




do_install() {

    install -d ${D}/www/pages/eyeos

    cp -r ${S}/* ${D}/www/pages/eyeos

}




PACKAGE_ARCH = "all"

FILES_${PN} += "/www/pages/eyeos"


So the final stage the final packages can be built fromt the recipe. First a clean to make sure anything worked on is gone then a build.
bitbake eyeos -c clean

bitbake eyeos


The package produced from this recipe is now ready to be installed on target for testing.


OpenEmbedded/Ångström Kernel Workflow
2009-12-10T01:35:14Z
This article is to detail the workflow I personally use when I am doing kernel development for devices supported by OE. I find OE very useful for this as I can use it to build the toolchain and ultimately to control my patch tree until I am ready to send the patches upstream.
So I select a kernel which I wish to develop with, in my case this is in
recipes/elphel/linux-elphel_git.bb
So I first make sure I am starting from clean
bitbake linux-elphel -c clean
Then take the kernel as far as the configuration stage, this makes sure all patches in the metadata are applied and that the defconfig has been copied to .config and make oldconfig has been run.
bitbake linux-elphel -c configure
Now I switch to another window where I shall be actually editing the code. I change to the temporary working directory of the kernel I am working with. This path below will change depending on kernel version or name. Kernels are always found in the machine workdir so tmp/-angstrom-linux-gnueabi/
cd tmp/work/elphel-10373-angstrom-linux-gnueabi/linux-elphel-2.6.31+2.6.32-rc8+r4+gitr2a97b06f43c616abb203f4c0eb40518c44c8d7fe-r28/
At this point I normally elect to use quilt to temporarily manage my patches so.
quilt new new-feature.patch
And to add files to this patch, I make sure to do this before I make any edits as the diff ends up being the diff from when this is first called to the current state.
quilt add driver/camera/random.c
Then load the file into my favourite editor.
vi driver/camera/random.c
I make the changes I require then it is time to create a patch from these changes so I then do.
quilt refresh
The above steps created a patches/ directory inside this is one or more patches and a file called series. series is a list of all the patches in the order they should be applied (quilt takes care of this).
So now I want to actually build this code to make sure it compiles so I switch back to my original terminal and issue.
bitbake linux-elphel -c compile
If this stage fails I continue editing the files to correct the errors remebering to refresh the patches as I go. The above command can be issued repeatedly until is succeeds. When it does I then wish to make the kernel image used on the the board I am playing with so.
bitbake linux-elphel -c deploy
I take the uImage file from tmp/deploy/images/ and send it to the board for booting however it is done in my setup. For this kernel I will write it into flash on the Elphel camera.
It is almost certain that this first attempt as create the new feature will have some problems. In this case I return to the terminal where I was editing the code and fix it (still not forgetting to refresh the patches). To force the compile stage to happen again I issue the command.
bitbake linux-elphel -c compile -f
The -f means force and forces bitbake to return to that stage. When the compile is successful I can again issue the following command to deploy the image again.
bitbake linux-elphel -c deploy
I repeat this cycle as needed until I have my new feature working as I wish.
When I am happy with the changes that have been made to the kernel I will have a patch file in patches/new-feature.patch that is suitable for adding directly to the OpenEmbedded meta data or which can be applied to a git tree ready for sending upstream.
I shall leave the git instructions to the git manual. For the case where I want to apply it to the OE meta data then I edit the original bitbake recipe, adding the patch to the SRC_URI in the form
file://new-feature.patch;patch=1
For example a finished line.
SRC_URI = "git://elphel.git.sourceforge.net/gitroot/elphel/linuxdavinci;branch=elphel-10373;protocol=git \

           file://new-feature.patch;patch=1 \

           file://defconfig"
I copy the patch into a suitable directory in the metadata. More information on how the build system searches directories for patches can be found on the OE wiki and the bitbake manual. In this case.
recipes/linux-elphel/new-feature.patch
Now I test everything is ok with a clean rebuild so.
bitbake linux-elphel -c clean

bitbake linux-elphel


This should successfully complete the build and I should have a kernel with my new feature. If at a later date I find my new feature does not quite work as expected I can use a variation of the same process to update it. Instead of issuing the quilt new/add commands I just start editing the files in the patch again and a quilt refresh will refresh the last patch applied to the source which is most likely my new feature. If it is not or I have done this process multiple times I can use quilt pop and push to move between patches.




Kernel Plumbers Conference 2009
2009-08-27T19:00:50Z
SlimLogic will be in attendance at this years Linux kernel plumbers conference in Portland, Oregon, September 23rd – 25th, 2009. See you there at the embedded and audio tracks.


Updated: Seven new Voltage regulator drivers for Linux
2009-08-27T18:23:29Z
Updated: New regulator drivers for the Freescale MC13783, Motorola PCAP2, Wolfson WM831x, Texas Instruments TPS65023 and TPS6507x, Marvell 88PM8607 and ST-Ericsson AB3100 have been accepted into the Linux voltage regulator development tree and will be heading for the mainline kernel in the next merge window. This should approximately take place in the next month and mean the drivers will be included in Linux 2.6.32.


Linux Voltage Regulator for 2.6.30
2009-04-16T11:37:55Z
The changes for 2.6.30 include a new twl4030 regulator driver, improved regulator init_data

handling, refcount fixes, some new voltage API functions and numerous minor fixes. Full change log:-
Adrian Hunter (1):

      regulator: twl4030 VAUX3 supports 3.0V
Andrew Morton (1):

      regulator: minor cleanup of virtual consumer
David Brownell (10):

      regulator: minor cleanup of virtual consumer

      regulator: add get_status()

      regulator: enumerate voltages (v2)

      regulator: get_status() grows kerneldoc

      regulator: twl4030 regulators

      regulator: twl4030 voltage enumeration (v2)

      MMC: regulator utilities

      twl4030-regulator: list more VAUX4 voltages

      regulator: refcount fixes

      twl4030-regulator: expose VPLL2
Jonathan Cameron (1):

      Regulator: Push lock out of _notifier_call_chain + add voltage change event.
Liam Girdwood (1):

      regulator: email – update email address and regulator webpage.
Mark Brown (16):

      regulator: Pass regulator init data as explict argument when registering

      regulator: Allow init data to be supplied for bq24022

      regulator: Allow init_data to be passed to fixed voltage regulators

      regulator: Make fixed voltage regulators visible in Kconfig

      regulator: Mark attributes table for virtual regulator static

      regulator: Hoist struct regulator_dev out of core to fix notifiers

      regulator: Suggest use of datasheet supply or pin names for consumers

      regulator: Allow regulators to set the initial operating mode

      regulator: Fix get_mode() for WM835x DCDCs

      regulator: Implement list_voltage() for WM8400 DCDCs and LDOs

      regulator: Don’t warn on omitted voltage constraints

      regulator: Implement list_voltage for WM835x LDOs and DCDCs

      regulator: Allow boot_on regulators to be disabled by clients

      regulator: Don’t warn if we failed to get a regulator

      regulator: Don’t increment use_count for boot_on regulators

      regulator: Support disabling of unused regulators by machines
Mike Rapoport (1):

      regulator: add unset_regulator_supplies to fix regulator_unregister
Randy Dunlap (1):

      regulator: fix header file missing kernel-doc
 Documentation/ABI/testing/sysfs-class-regulator |   57 +++-

 MAINTAINERS                                     |    2 +-

 drivers/mfd/twl4030-core.c                      |    2 -

 drivers/mmc/core/core.c                         |  100 +++++

 drivers/regulator/Kconfig                       |   13 +-

 drivers/regulator/Makefile                      |    1 +

 drivers/regulator/bq24022.c                     |    3 +-

 drivers/regulator/core.c                        |  386 ++++++++++++++----

 drivers/regulator/da903x.c                      |    3 +-

 drivers/regulator/fixed.c                       |    3 +-

 drivers/regulator/pcf50633-regulator.c          |    3 +-

 drivers/regulator/twl4030-regulator.c           |  500 +++++++++++++++++++++++

 drivers/regulator/virtual.c                     |   14 +-

 drivers/regulator/wm8350-regulator.c            |   57 +++-

 drivers/regulator/wm8400-regulator.c            |   36 ++-

 include/linux/i2c/twl4030.h                     |   47 +++

 include/linux/mmc/host.h                        |    5 +

 include/linux/regulator/bq24022.h               |    3 +

 include/linux/regulator/consumer.h              |    6 +-

 include/linux/regulator/driver.h                |   81 ++++-

 include/linux/regulator/fixed.h                 |    3 +

 include/linux/regulator/machine.h               |   12 +-

 22 files changed, 1220 insertions(+), 117 deletions(-)

 create mode 100644 drivers/regulator/twl4030-regulator.c


Android
2009-04-16T09:28:03Z

SlimLogic are now an official Android^TM developer and will be working on unique technologies to enhance Android for developers, device manufacturers and users. SlimLogic will bring together it’s years of experience in device software development and device life cycle expertise to bring Android to many new platforms and users.
The Android trademark and logo are Copyright Google Inc. Portions of this page are reproduced from work created and shared by Google and used according to terms described in the Creative Commons 2.5 Attribution License. 


FOSDEM 2009
2009-02-01T15:30:10Z
FOSDEM is a free an non commercial open source software conference held in Brussels Belgium on the 7th and 8th February 2009.
SlimLogic will be in attendance and will be presenting a paper on embedded power management techniques using the Linux kernel voltage regulator subsystem. Come along and see us….