linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: saeed.bishara@gmail.com (saeed bishara)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Moving Marvell Dove platform defaults to ARMv7
Date: Wed, 6 Apr 2011 11:22:51 +0300	[thread overview]
Message-ID: <BANLkTinJP1S_tUfTG8jeeZRTq80bCE8kvw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104051450550.28032@xanadu.home>

On Tue, Apr 5, 2011 at 9:55 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> On Tue, 5 Apr 2011, saeed bishara wrote:
>
>> On Sun, Apr 3, 2011 at 10:13 AM, Konstantin Porotchkin
>> <kostap@marvell.com> wrote:
>> > Disabled legacy support for ARMv6 archtecture on Dove platform.
>> > Latest Dove HW uses only ARMv7 model.
>
> What about older Dove hardware? ?That's all I have for testing.
1. you can configure it to v7 mode by setting dip switch #6 of SW2 to off.
SW2 dip switch group is the middle one out of 3 that located near the DRAM DIMM.
2. but, we are going to drop support for the old boards when we add
mpp configuration, I'll check if we can send you new board.
>
>> > --- a/arch/arm/configs/dove_defconfig
>> > +++ b/arch/arm/configs/dove_defconfig
> [...]
>> > -# CONFIG_MISC_DEVICES is not set
>> > +CONFIG_LEGACY_PTY_COUNT=16
>> > -CONFIG_LEGACY_PTY_COUNT=16
>> > -# CONFIG_VGA_CONSOLE is not set
>> > -CONFIG_USB_EHCI_TT_NEWSCHED=y
>> > -CONFIG_INOTIFY=y
>> > -# CONFIG_RCU_CPU_STALL_DETECTOR is not set
>> > -CONFIG_CRYPTO_CBC=y
>> > -CONFIG_CRYPTO_MD5=y
>> > -CONFIG_CRYPTO_DES=y
>
> Those changes above are unrelated to the reason for this patch. ?Please
> remove.
should we prepare a separate patch that syncs the dove_defconfig with
latest kernel?

>
>
> Nicolas
>

  reply	other threads:[~2011-04-06  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03  7:13 [PATCH] Moving Marvell Dove platform defaults to ARMv7 Konstantin Porotchkin
2011-04-05 13:00 ` saeed bishara
2011-04-05 18:55   ` Nicolas Pitre
2011-04-06  8:22     ` saeed bishara [this message]
2011-04-06 13:05       ` Nicolas Pitre

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=BANLkTinJP1S_tUfTG8jeeZRTq80bCE8kvw@mail.gmail.com \
    --to=saeed.bishara@gmail.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).