Hello everyone, I am now officially soliciting bids for the contract projects listed at: http://elinux.org/Project_Proposals_for_2013 You can find detailed instructions for bidding

Good questions. I hadn't heard of isolcpus. I'll have to ask the Sony team interested in this if they're aware of it, and if they need this feature at runtime. -- Tim

Wow! That's really impressing. Can you provide any details? Is that from power on to Qt driving the gui with an image up? Are you doing XIP? I haven't seen times under 500 ms. unless people are

Thanks - wiki page at: http://elinux.org/Setup_LTSI_Testing/Validation_infrastructure -- Tim

Thanks for this proposal. Just to clarify - are you describing getting the Android framework up quickly, or doing a side-load of AV functionality in order to get to a specific feature (video

I'm intresseteing in it we could use this too on barebox Best Regards, J.

That is exactly the issue here what means boot time. here I get board with a full system + QT UI in 300ms running from cold start. You must specify what means boot time because boot time can be up

<plagnioj@...> wrote: Hmm, 30 seconds can be a long time ;-) For user interaction, the typical guideline is: upon any user activity, the system should respond within 500 ms, either by

what is the booting target? I've done in the past on non optimised android < 30s from cold start to UI on arm926ejs with base Android < 30s on more complex and full feature Android on Cortex-A9 (5

; Summary: Setup LTSI Testing/Validation infrastructure ; Proposer: Artemi Ivanov / Hisao Munakata == Description == It has been discussed recently: how LTSI project could attract new contributors,

; Summary: Android boot time improvements ; Proposer: Artemi Ivanov == Description == Android boot time could be dramatically improved by leveraging checkpoints/snapshots approaches (might be

Hi Tim, Why not use the isolcpus on the kernel command line? It doesn't depend on cgroups. Do you really need to configure this at runtime? Lucas De Marchi

; Summary: Add support for CONFIG_NUMA to ARM ; Proposer: Tim Bird, Sony Mobile == Description == ARM does not currently support CONFIG_NUMA. In some embedded products, it is useful to treat

OK - this is not right. For my research on the current driver, I was looking at the wrong git tree. The driver in mainline has been worked on much more recently than this, by the fine folks at

; Summary: Add device-tree support to the pn544 NFC driver ; Proposer: Tim Bird, Sony Mobile == Description == The NXP PN544 NFC chipset is used in a very large number of Linux-based devices. The

(For the benefit of Christopher and Dmitry, who are CC'ed and might not know what this is all about - the CE Workgroup of the Linux Foundation periodically funds contract work for items of interest to

FYI - Sony has patches to support 4KB mappings for the kernel, for ARM, which they've been using internally. These might be useful for this feature.

; Summary: Support asymetric RSA in Crypto API ; Proposer: Tim Bird, Sony Mobile == Description == The current AF_ALG interface to user space only supports hash and symmetric algorithms. Some user

; Summary: Kernel module binary compatibility with debug features ; Proposer: Tim Bird, Sony Mobile == Description == Sometimes, the workflow for embedded systems include obtaining kernel modules

; Summary: Overwrite detection for kernel text and read-only data ; Proposer: Tim Bird, Sony Mobile == Description == In embedded systems, drivers or other subsystems can easily