linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: LPC32xx status (Re: [PATCH] Correct bad gpio naming)
Date: Tue, 24 Jan 2012 21:38:00 +0100	[thread overview]
Message-ID: <4F1F16A8.7010407@antcom.de> (raw)
In-Reply-To: <20120124192545.GB8502@pengutronix.de>

On 24/01/12 20:25, Wolfram Sang wrote:
>> Expect the first one of the drivers to be submitted soon, I will
>> do them one by one.
> 
> I think the first step should be adding a generic defconfig and
> make sure this builds and boots (I think I have a phy3250
> somewhere, so I could test). After that new drivers would make
> sense. IIRC clock.c was pretty broken, we needed hacks to get USB
> working with a 2.6.35. I also see that your tree modifies it.

I see that you are already at it ;-) - for the others: On the server
"git.antcom.de", I meant repository "linux-2.6.git", branch "work92105".

Unfortunately, I currently don't have a phy3250, but can check
tomorrow with colleagues.

I guess the work92105_defconfig is only useful once the drivers
currently missing in mainline are merged. Or is there an arm specific
tree I should update from?

Thanks in advance!

Roland

  reply	other threads:[~2012-01-24 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 17:57 [PATCH] Correct bad gpio naming Roland Stigge
2012-01-22 19:31 ` Grant Likely
2012-01-24 15:59 ` Wolfram Sang
2012-01-24 16:32   ` Roland Stigge
2012-01-24 19:25     ` LPC32xx status (Re: [PATCH] Correct bad gpio naming) Wolfram Sang
2012-01-24 20:38       ` Roland Stigge [this message]
2012-01-24 21:09         ` Wolfram Sang

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=4F1F16A8.7010407@antcom.de \
    --to=stigge@antcom.de \
    --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).