+ all written in usermode
+ no new proc files
+ configuration based on text file so easy to adapt to the non-omap proletarians
+ gui alignment still needs work
+ sample config files for PD and VDD in the patch but lots of
registers and domains still need to be added
+ same code does power and voltage domains
+ diff attached
+ screenshots attached
--
- evt
(Eric van Tassell)
twitter: evt_texelsoft
linked-in: linkedin.com/in/evttxl
Hi all,
I need some help in choosing right version of rootfs for my environment.
I have a development board with ST SoC with Cortex-A9 dual core and VFPv3-D16. Kernel version available to me is 2.6.37.
I am using Debian 6 arm-hf port, but would like to try Linaro rootfs.
1. What is the version of linaro filesytem I should pick (optimum for -mfpu=vfp and -mfloat-abi=hard) ?
2. I don't have a hwpack, is it possible to use vexpress or similar rootfs.
Regards,
Suresh
I have created an git repo for the kernel config fragments we produced a
while ago, this is at git://git.linaro.org/kernel/configs.git
The config-core-tracking branch in this repo is intended to be added to
the linux-linaro-core-tracking branch and so be available in all Linaro
kernels. This currently provides three config fragment files:
linaro/configs/linaro-base.conf
Config options common to all Linaro kernels
linaro/configs/ubuntu.conf
Config options for all Ubuntu kernels
linaro/configs/android.conf
Config options for all Android kernels
In addition to these, a board specific config fragment is required to
produce a final kernel config. This may be made available by a Landing
Team's kernel tree (I have done this for vexpress [1]) or; for
experimental purposes, or to support legacy platforms, I have a separate
config-boards-tracking branch of the new configs.git. (Currently this
contains the Origen and iMX5 fragments produced a while ago.)
To create an Ubuntu kernel config from these fragments for a device
called $BOARD, you need to run a command like:
ARCH=arm scripts/kconfig/merge_config.sh \
linaro/configs/linaro-base.conf linaro/configs/ubuntu.conf \
linaro/configs/$BOARD.conf
For Android, s/ubuntu/android/ in the above.
At some point soonish, I hope to come up with a mechanism whereby
Android builds have the option to dynamically generate their kernel
config as above. John Rigby is planning on adding a similar option to
the Ubuntu packaging jobs.
Hopefully this work will enable:
- easier management of system wide config settings required by working
group output or Linaro policy
- place board specific configuration in the hands of the people
maintaining that boards kernel
- more consistent kernel builds, so teams can test in the same
environment as Linaro's final releases
I intend to maintain git://git.linaro.org/kernel/configs.git and will
keep separate non 'tracking' branches for older kernel versions (I
currently have branches for 3.4).
--
Tixy
[1] http://git.linaro.org/gitweb?p=landing-teams/working/arm/kernel.git;a=short…
Hey Andrey, Zach,
So I'm back from my vacation, and have found that the Android team
has released a -compat tree for their 3.4 kernel. Basically this tree
re-adds some items like earlysuspend and classic wakelocks in order to
provide better compatibility with old (and by old, I really mean
current as far as we see - so ICS and earlier) Android userland.
Since we're still shipping ICS, and have no access to whatever the
Android 5.0 userland will be, it seems merging in the -compat tree would
make sense.
However, I know Tixy and others have already tried to address the lack
of earlysuspend in the android-3.3+ kernels, so I wanted to double check
that this wouldn't cause additional pain (since those adjustments might
need to be reverted).
So I just wanted to check first with folks to make sure there are no
objections to merging in the -compat changes, and that the timing of
merging in these changes isn't problematic (I can happily hold off till
this months release is done, so we don't risk any last minute gotchas).
thanks
-john
Greetings,
So far I wasn't updating the linux-linaro tree since the 12.04 release.
(The generic topic updates were being done to the
linux-linaro-core-tracking tree)
Now it is time to move the focus to the linux-linaro tree. For one week
it will use the mainline tip as the base. Then, on next Thursday the
most recent -rc will be selected as the base, and won't be changed until
12.05 is released. Most probably it will be v3.4-rc7.
The 12.05 linux-linaro tree will get the ARM and Samsung LTs topics plus
the 7 generic topics currently included into the
linux-linaro-core-tracking tree:
ufs (ufs-for-linux-linaro)
emmc (emmc-for-linux-linaro)
thermal_exynos4_imx6 (thermal_exynos4_imx6_work)
linaro-android-3.4
armlt-gator (tracking-armlt-gator)
umm-wip (umm-3.4rc4-wip)
linaro-configs-3.4
If you don't see your generic topic in this list, but you think it
should be there, please let me know ASAP. If you have a new topic to
add, please send me the request before the next Thursday, May 17; the
sooner, the better. The requirements for a topic can be found here:
https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess#A…
The landing teams - please update your topic branches if needed:
ARM:
tracking-armlt-hdlcd tracking-armlt-mmc
tracking-armlt-arm-arch-fixes tracking-armlt-misc-fixes
tracking-armlt-ubuntu-config tracking-armlt-android-config
Samsung:
topic/base topic/core topic/bl topic/dt topic/fb topic/pd
topic/s2ram topic/asv_cpufreq topic/led topic/dummy_reg
topic/gadget topic/touch topic/wlan topic/audio topic/hdmi
topic/mali topic/cma_v24 topic/android_config
Thanks,
Andrey
Hi,
Thank you for your work on the dev boards. Recently i had been working
with Android. Your work saved a lot of time for me.
I request you to also consider support the raspberry pi board. Which is
quite useful for many people. Enduses as well as devs..
Thank you
Are we going to start using the config fragments we created a while ago?
(Or did we not reach consensus on that?)
If we could get them into a 'final' git location and start using them
for Ubuntu packaging, I can arrange for a mechanism to enable Android
builds to use them.
I have attached a couple of patches for the config fragments (3.5
removed the PERF_COUNTERS config).
--
Tixy
