linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ospite@studenti.unina.it (Antonio Ospite)
To: linux-arm-kernel@lists.infradead.org
Subject: pxa27x_udc: Oops on probe with usb cable connected.
Date: Sat, 3 Jul 2010 22:10:22 +0200	[thread overview]
Message-ID: <20100703221022.27df1a2e.ospite@studenti.unina.it> (raw)
In-Reply-To: <877hld7np5.fsf@free.fr>

On Fri, 02 Jul 2010 20:17:42 +0200
Robert Jarzmik <robert.jarzmik@free.fr> wrote:

> Antonio Ospite <ospite@studenti.unina.it> writes:
> > Note that using the original blob bootloader from Motorola there is no
> > Oops but the UDC does not work at all, but maybe this is another
> > issue, I mean: should pxa27x_udc probe consider the case when UDC is
> > already active?
> It was not designed for, but it actually works on my platform, when I launch
> linux kernel from haret without disabling the UDC.
>

I see.

> > Tell me how can i help debugging this, I've put the binary and the
> > disassembled code in http://people.openezx.org/ao2/tmp/pxa27x-udc_BUG/
> > plus some notes about old discussions on the same matter.
> There are a few things I can do with a little more information.
> 
>  - Prevent gcc from being too smart by inlining functions : I think the right
>    flag is -fno-inline. This will prevent irq_handle_data() and others to be
>    inlined into pxa_udc_irq(), and ease the debugging.
>

Done that as well this time. See
http://people.openezx.org/ao2/tmp/pxa27x-udc_BUG/
I replaced the old files with the new ones as per your instructions.

Thanks,
   Antonio

-- 
Antonio Ospite
http://ao2.it

PGP public key ID: 0x4553B001

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100703/c34854b0/attachment.sig>

  reply	other threads:[~2010-07-03 20:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30  9:53 pxa27x_udc: Oops on probe with usb cable connected Antonio Ospite
2010-07-02 18:17 ` Robert Jarzmik
2010-07-03 20:10   ` Antonio Ospite [this message]
2010-07-03 23:48     ` Robert Jarzmik
2010-07-05  8:40       ` Antonio Ospite
2010-07-06 22:34         ` Robert Jarzmik
2010-07-06 22:56           ` Antonio Ospite
2010-07-11  8:13         ` Robert Jarzmik
2010-07-22 15:14           ` Antonio Ospite
2010-07-23 11:18             ` Antonio Ospite
2010-07-23 19:07               ` Robert Jarzmik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100703221022.27df1a2e.ospite@studenti.unina.it \
    --to=ospite@studenti.unina.it \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).