Re: [ANNOUNCE] linux-linaro kernel schedule / llct age

2013-06-03 Thread Tushar Behera
> Timely updates on llct for each mainline -rc are very interesting > though, in fact we depend on them. > +1. -- Tushar Behera ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev

problem using QEMU

2013-06-03 Thread David Long
I'm trying to build for versatile express to run under QEMU. When I boot under QEMU I get errors regarding the SD voltage, and it fails. I have not really used QEMU for testing before. Has anyone encountered this? It's likely I've got something basic wrong. Here is the command I'm using:

Re: [ANNOUNCE] linux-linaro kernel schedule / llct age

2013-06-03 Thread Andy Green
On 22/05/13 02:48, the mail apparently from Andrey Konovalov included: The next steps are: May 22: ll rebuild based on llct-20130521.0 May 23: ll rebuild based on llct-20130521.0, linux-linaro release candidate, code freeze The last llct update for this cycle is scheduled on May 21, The last l

Re: [PATCH V3 2/2] USB: OHCI: add a name for the platform-private field

2013-06-03 Thread Alan Stern
On Mon, 3 Jun 2013, Manjunath Goudar wrote: > This patch adds an ohci->priv field for private use by OHCI > platform drivers. > > Until now none of the platform drivers has used this private space, > but that's about to change in the next patch of this series. Acked-by: Alan Stern ___

[PATCH V3 1/2] USB: OHCI: make ohci-platform a separate driver

2013-06-03 Thread Manjunath Goudar
This patch splits the ohci-platform code from ohci-hcd out into its own separate driver module.This work is part of enabling multi-platform kernels on ARM. In V2: -Passed "hcd" argument instead of "ohci" in ohci_setup() because it is using "struct usb_hcd" argument. In V3: -Directly passed

[PATCH V3 2/2] USB: OHCI: add a name for the platform-private field

2013-06-03 Thread Manjunath Goudar
This patch adds an ohci->priv field for private use by OHCI platform drivers. Until now none of the platform drivers has used this private space, but that's about to change in the next patch of this series. Signed-off-by: Manjunath Goudar Cc: Arnd Bergmann Cc: Greg KH Cc: Alan Stern Cc: linux

[PATCH V3 0/2] USB: OHCI: Splitting ohci-platform into independent driver

2013-06-03 Thread Manjunath Goudar
This series patch begins the process of splitting ohci-platform up into independent driver modules and add a name for the platform-private field. Patch 1/2 separate ohci-platform into independent driver modules. V2 to V3: Directly Passed "hcd" argument without calling ohci_to_hcd() function. Pat

[PATCH 2/2] USB: OHCI: add a name for the platform-private field

2013-06-03 Thread Manjunath Goudar
This patch adds an ohci->priv field for private use by OHCI platform drivers. Until now none of the platform drivers has used this private space, but that's about to change in the next patch of this series. Signed-off-by: Manjunath Goudar Cc: Arnd Bergmann Cc: Greg KH Cc: Alan Stern Cc: linux

[PATCH 1/2] USB: OHCI: make ohci-platform a separate driver

2013-06-03 Thread Manjunath Goudar
This patch splits the ohci-platform code from ohci-hcd out into its own separate driver module.This work is part of enabling multi-platform kernels on ARM. In V2: -Passed "hcd" argument instead of "ohci" in ohci_setup() because it is using "struct usb_hcd" argument. In V3: -Directly passed

[PATCH V3 0/2] USB: OHCI: Splitting ohci-platform into independent driver

2013-06-03 Thread Manjunath Goudar
This series patch begins the process of splitting ohci-platform up into independent driver modules and add a name for the platform-private field. Patch 1/2 separate ohci-platform into independent driver modules. V2 to V3: Directly Passed "hcd" argument without calling ohci_to_hcd() function. Pat

Re: Couldn't locate release kernel sha key 0f66281a18ce706b4de2d4c208a852d358ecaf43

2013-06-03 Thread Ryan Harkin
On 3 June 2013 09:17, Jon Medhurst (Tixy) wrote: > On Mon, 2013-06-03 at 13:19 +0530, Viresh Kumar wrote: >> Hi Guys, >> >> Few of my ARM colleagues are facing issues in obtaining git tree for >> 13.03 release. >> They are referring: >> >> https://releases.linaro.org/13.03/android/vexpress >> >> f

Re: Couldn't locate release kernel sha key 0f66281a18ce706b4de2d4c208a852d358ecaf43

2013-06-03 Thread Jon Medhurst (Tixy)
On Mon, 2013-06-03 at 13:19 +0530, Viresh Kumar wrote: > Hi Guys, > > Few of my ARM colleagues are facing issues in obtaining git tree for > 13.03 release. > They are referring: > > https://releases.linaro.org/13.03/android/vexpress > > file: linaro_kernel_build_cmds.sh > > Which has got follow

Couldn't locate release kernel sha key 0f66281a18ce706b4de2d4c208a852d358ecaf43

2013-06-03 Thread Viresh Kumar
Hi Guys, Few of my ARM colleagues are facing issues in obtaining git tree for 13.03 release. They are referring: https://releases.linaro.org/13.03/android/vexpress file: linaro_kernel_build_cmds.sh Which has got following line to go to checkout released tree. git checkout 0f66281a18ce706b4de2

linaro armv8 kernel crashdump (kdump?)

2013-06-03 Thread phi debian
Hi All, I'd like to investigate kernel crashdump debuging for armv8. For this I need a crashdump, basically I would be happy with a vmlinux with debuginfos (-g compiled) either as 1 a.out or a splitted a.out ( ala suse) a save state of some sort (a crash notes records) and a vmcore that could be