All of lore.kernel.org
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Added phy3250_defconfig
Date: Thu, 26 Jan 2012 17:04:36 +0100	[thread overview]
Message-ID: <4F217994.2080906@antcom.de> (raw)
In-Reply-To: <1327592865-16859-1-git-send-email-stigge@antcom.de>

Hi,

On 01/26/2012 04:47 PM, Roland Stigge wrote:
> This patch provides a working default config for the reference board (PHY3250)
> of the NXP LPC32XX architecture. It is the first in a series of patches to
> provide more complete support for that architecture.

We recently discussed that the first step for better LPC32XX integration
would be a respective defconfig file.

With this patch (for Linux 3.3.0-rc1), I'm providing a phy3250_defconfig
that especially supports the reference design by PHYTEC. This is because
every supported board (including the PHY board) will have hardware
specific parameters that don't map very good to a reasonably general
lpc32xx_defconfig. Please tell me what you think about that.

Some further notes:

* I added LPC3XXX to mach-types because the bootloader on my PHY3250
board identifies as machine type no. 736.

* This is a minimal patch that makes lpc32xx compile and boot. I will
submit further drivers for LPC32xx building upon that.

* OHCI HCD is currently broken, disabled for now (already have a newer
one working, will submit later)

* The previously discussed update for clock.c will also follow in a
separate patch (currently compiles with several warnings).

You can have a preview for the remaining drivers at
http://git.antcom.de/ , repo "linux-2.6", branch "work92105".

Thanks in advance,

Roland

  reply	other threads:[~2012-01-26 16:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 15:47 [PATCH] Added phy3250_defconfig Roland Stigge
2012-01-26 16:04 ` Roland Stigge [this message]
2012-01-26 20:49   ` Wolfram Sang
2012-01-26 20:31 ` Russell King - ARM Linux

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=4F217994.2080906@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 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.