mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@antcom.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: bangaragiri.g@nxp.com, srinivas.bakki@nxp.com,
	sundarapandian.andithevar@nxp.com, linus.walleij@linaro.org,
	linux-kernel@vger.kernel.org, kevin.wells@nxp.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: LPC32xx: Support for OHCI HCD
Date: Thu, 02 Feb 2012 20:37:42 +0100	[thread overview]
Message-ID: <4F2AE606.7090903@antcom.de> (raw)
In-Reply-To: <20120202164114.GB3219@pengutronix.de>

Hi,

On 02/02/2012 05:41 PM, Wolfram Sang wrote:
> Okay, I asked for a patch to test USB, so thanks. It did not work 
> for me, sadly, so there seems to be more work needed in that area.

Of course, we need to first sort things out. :-)

Already now, when you apply all my patches on top of each other, USB
(and ethernet) works fine for me.

Of course, the just re-posted base series ("v3") has priority, but if
you are curious, you can have a look at the patches at
http://antcom.de/lpc32xx/ and apply them on top of current mainline
(3.3-rc2). You need to manually enable OHCI and the LPC-ETH drivers,
based on our new defconfig, of course. If it still doesn't work,
please tell me at which point it doesn't compile or boot.

I just re-tested this with my PHYTEC3250 board, using NFS root and
mounting USB mass storage.

> also misses important mailing lists (usb).

I posted the drivers for ethernet, usb and iio to the respective
maintainers and mailing lists, separately.

> May I ask if you read Documentation/development-process and/or 
> Documentation/SubmittingPatches? If not, please do so.

Good. Thanks for the hint. :-)

We can do one step after another.

Thanks for your involvement here!

Roland

      reply	other threads:[~2012-02-02 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 13:30 stigge
2012-02-02 16:41 ` Wolfram Sang
2012-02-02 19:37   ` Roland Stigge [this message]

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=4F2AE606.7090903@antcom.de \
    --to=stigge@antcom.de \
    --cc=bangaragiri.g@nxp.com \
    --cc=kevin.wells@nxp.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.bakki@nxp.com \
    --cc=sundarapandian.andithevar@nxp.com \
    --cc=w.sang@pengutronix.de \
    /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

Powered by JetHome