On Wed, 16 Apr 2014, Christopher Covington wrote:
On 04/15/2014 06:44 AM, Daniel Thompson wrote:
Hi Folks
I've just been rebasing some of my development branches against v3.15rc1
and observed some boot regressions due to TEXT_OFFSET changing from
0x8000 to 0x208000.
Now the boot
Hi Nicolas,
Thanks for your response.
On 04/16/2014 03:14 PM, Nicolas Pitre wrote:
On Wed, 16 Apr 2014, Christopher Covington wrote:
On 04/15/2014 06:44 AM, Daniel Thompson wrote:
Hi Folks
I've just been rebasing some of my development branches against v3.15rc1
and observed some boot
This set of patches adds support for the v1.3.0 version of the QCOM BAM
dmaengine driver. The older version of the BAM is present in the MSM8x64,
APQ8064, and IPQ8064 processors.
Due to register address space changes between versions, all of the register
accesses have to be calculated using
On Wed, Apr 16, 2014 at 05:08:35PM -0400, Christopher Covington wrote:
What I meant to ask about was variance from one kernel version and build to
the next, given a single platform. Platform-to-platform variation can probably
be abstracted where needed by the scripts controlling the external
On Wed, Apr 16, 2014 at 10:36:11PM +0100, Peter Maydell wrote:
On 16 April 2014 22:08, Christopher Covington c...@codeaurora.org wrote:
On 04/16/2014 03:14 PM, Nicolas Pitre wrote:
But both QEMU and the boot-wrapper should deal with zImage. That's the
only image format with documented load
