From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: LPC32xx status (Re: [PATCH] Correct bad gpio naming)
Date: Tue, 24 Jan 2012 20:25:45 +0100 [thread overview]
Message-ID: <20120124192545.GB8502@pengutronix.de> (raw)
In-Reply-To: <4F1EDD15.7010704@antcom.de>
> > Since you are modifying LPC32xx :) Which kernel version do you run?
> > I was trying to get a board up with 3.0 (not booting) and 3.3-rc1
> > (build breakage). I even thought about removing that mach, since
> > vital parts seem to be missing (Net, NAND) or broken. So, I am
> > interested if there are still users.
>
> I'm actively maintaining an LPC32xx machine line (WORK Microwave GmbH
> devices) at http://git.antcom.de/ - feel free to merge from there.
Cool, best answer I could get \o/
> 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.
Kevin: Are you with us?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120124/6d8e020a/attachment.sig>
next prev parent reply other threads:[~2012-01-24 19:25 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 ` Wolfram Sang [this message]
2012-01-24 20:38 ` LPC32xx status (Re: [PATCH] Correct bad gpio naming) Roland Stigge
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=20120124192545.GB8502@pengutronix.de \
--to=w.sang@pengutronix.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).