linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: AT91: add board support for Pcontrol_G20
Date: Tue, 19 Oct 2010 11:25:31 +0200	[thread overview]
Message-ID: <4CBD640B.1050402@atmel.com> (raw)
In-Reply-To: <20101014151451.GB23434@n2100.arm.linux.org.uk>

Le 14/10/2010 17:14, Russell King - ARM Linux :
> On Thu, Oct 14, 2010 at 04:47:47PM +0200, Nicolas Ferre wrote:
>>> diff --git a/arch/arm/configs/pcontrol_g20_defconfig b/arch/arm/configs/pcontrol_g20_defconfig
>>> new file mode 100644
> 
> Is it really necessary to have another platform specific defconfig rather
> than grouping it together with other similar platforms?

Hi Russell,

Peter used the new defconfig infrastructure (which produces a reduced
defconfig) and we are working on merging board code as much as we can
(Cf. merging of 9g20ek and 9g20ek_2mmc).

So, maybe you can take this board support and we will try to share
defconfig per platform during .37 development cycle?


BTW, will I have to merge this change to conform with new "debug macro
infrastructure" ?

--- a/arch/arm/mach-at91/board-pcontrol-g20.c
+++ b/arch/arm/mach-at91/board-pcontrol-g20.c
@@ -314,8 +314,6 @@ static void __init pcontrol_g20_board_init(void)

 MACHINE_START(PCONTROL_G20, "PControl G20")
        /* Maintainer: pgsellmann at portner-elektronik.at */
-       .phys_io        = AT91_BASE_SYS,
-       .io_pg_offst    = (AT91_VA_BASE_SYS >> 18) & 0xfffc,
        .boot_params    = AT91_SDRAM_BASE + 0x100,
        .timer          = &at91sam926x_timer,
        .map_io         = pcontrol_g20_map_io,

Best regards,
-- 
Nicolas Ferre

      parent reply	other threads:[~2010-10-19  9:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 15:41 [PATCH] ARM: AT91: add board support for Pcontrol_G20 Peter Gsellmann
2010-10-08 12:34 ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-08 15:10   ` Peter Gsellmann
2010-10-11  9:02     ` [PATCH v2] " Peter Gsellmann
2010-10-11 10:22       ` [PATCH v3] " Peter Gsellmann
2010-10-13 13:15         ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-13 14:18           ` [PATCH v4] " Peter Gsellmann
2010-10-14 14:47             ` Nicolas Ferre
2010-10-14 15:14               ` Russell King - ARM Linux
2010-10-15  1:50                 ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-15 16:31                   ` avictor.za at gmail.com
2010-10-18  8:00                     ` Peter Gsellmann
2010-10-19  9:25                 ` Nicolas Ferre [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=4CBD640B.1050402@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --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).