From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <531372CF.4060608@xenomai.org> Date: Sun, 02 Mar 2014 19:05:03 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <530D0205.9050406@xenomai.org> <530D0BBD.6070704@xenomai.org> <530D2C92.9010607@xenomai.org> <530E6159.4050204@xenomai.org> <530F17EC.6020204@xenomai.org> <530F9CA2.2040601@xenomai.org> <531075E7.7060107@xenomai.org> <53134A2E.1000406@xenomai.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] RaspberryPi kernel 3.8 issue List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gregory Dymarek Cc: xenomai@xenomai.org On 03/02/2014 06:26 PM, Gregory Dymarek wrote: > So I started from scratch, have not used any xenomai/ipipe patches. But > used the same .config. > As a result all worked fine. The USB device is getting initialized > correctly. > > So the current situation is that xenomai does work on 3.2 but does not on > 3.8 because of some USB driver issues. > I diff'ed the code for dwc_otg_hcd_handle_intr and this has changed. > What is intriguing: > https://github.com/raspberrypi/linux/blob/rpi-3.8.y/drivers/usb/host/dwc_otg/dwc_otg_hcd_intr.c#L530 > > // We should be OK doing this because the common interrupts should already > have been serviced > > So I removed all the DEBUG code from this function, but this did not help > either. Not sure if my test is valid in here. As I said, I believe there is now no substitute to understanding how the driver works if you want to debug the issue on 3.8. The problem to understand is why the interrupt handler does nothing and returns IRQ_NONE instead of acknowledging the interrupt and returning IRQ_HANDLED. -- Gilles.