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 22:09:24 +0100 [thread overview]
Message-ID: <20120124210924.GD8502@pengutronix.de> (raw)
In-Reply-To: <4F1F16A8.7010407@antcom.de>
> Unfortunately, I currently don't have a phy3250, but can check
> tomorrow with colleagues.
Shouldn't matter that much, or? Once the core support is back and works for
your board, others could test with their boards.
> 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?
You can keep the work92105_defconfig in your tree, but we'd need to introduce a
lpc32xx_defconfig. That should start with a minimal (but working) config and
can be extended once the drivers are in place.
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/17c3e0f3/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <w.sang@pengutronix.de>
To: Roland Stigge <stigge@antcom.de>
Cc: linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
grant.likely@secretlab.ca, linus.walleij@stericsson.com,
linux-kernel@vger.kernel.org, Kevin Wells <kevin.wells@nxp.com>
Subject: Re: LPC32xx status (Re: [PATCH] Correct bad gpio naming)
Date: Tue, 24 Jan 2012 22:09:24 +0100 [thread overview]
Message-ID: <20120124210924.GD8502@pengutronix.de> (raw)
In-Reply-To: <4F1F16A8.7010407@antcom.de>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
> Unfortunately, I currently don't have a phy3250, but can check
> tomorrow with colleagues.
Shouldn't matter that much, or? Once the core support is back and works for
your board, others could test with their boards.
> 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?
You can keep the work92105_defconfig in your tree, but we'd need to introduce a
lpc32xx_defconfig. That should start with a minimal (but working) config and
can be extended once the drivers are in place.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-01-24 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 17:57 [PATCH] Correct bad gpio naming Roland Stigge
2012-01-22 17:57 ` Roland Stigge
2012-01-22 19:31 ` Grant Likely
2012-01-22 19:31 ` Grant Likely
2012-01-24 15:59 ` Wolfram Sang
2012-01-24 15:59 ` Wolfram Sang
2012-01-24 16:32 ` Roland Stigge
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 19:25 ` Wolfram Sang
2012-01-24 20:38 ` Roland Stigge
2012-01-24 20:38 ` Roland Stigge
2012-01-24 21:09 ` Wolfram Sang [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=20120124210924.GD8502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.