All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Jason Cooper <jason@lakedaemon.net>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Nadav Haklai <nadavh@marvell.com>,
	Tawfik Bayouk <tawfik@marvell.com>,
	Lior Amsalem <alior@marvell.com>,
	Gregory Clement <gregory.clement@free-electrons.com>
Subject: Re: [PATCH 0/4] Make Armada 375 use the reference clock when possible
Date: Thu, 23 Oct 2014 09:43:29 -0300	[thread overview]
Message-ID: <5448F7F1.1080509@free-electrons.com> (raw)
In-Reply-To: <20141023142657.6b4d61fb@free-electrons.com>

On 10/23/2014 09:26 AM, Thomas Petazzoni wrote:
> Dear Ezequiel Garcia,
> 
> On Thu, 23 Oct 2014 09:16:33 -0300, Ezequiel Garcia wrote:
> 
>>> You don't clearly state whether your patch series keep compatibility
>>> with the 375 Z1 or not. And in fact, it doesn't keep compatibility with
>>> Z1. I'm fine with that, but then it means we should officially declare
>>> the Z1 support in mainline as dead, and get rid of the workarounds that
>>> applied only to 375 Z1.
>>
>> How many people have Z1 boards? And is someone actually using one for
>> something? Do we have any other reason to support Z1?
>>
>> FWIW, a v3.18-rc1 kernel built with mvebu_v7_defconfig, silently stalls
>> in the middle of the boot on Z1. Had to remove lots of compile time
>> options to make it boot.
>>
>> Before I start digging into this, maybe we can discuss your suggestion
>> to drop it. If nobody is booting this often enough, maybe nobody cares
>> about this, and it makes sense to drop the support?
> 
> Marvell has always said they are not interested in having Z1 supported
> in mainline, except as a first step to start getting the 375 support in
> mainline. I have been waiting for everyone of us to have access to 375
> A0 platforms, which is now the case. So I believe we can probably get
> rid of the 375 Z1 support entirely.
> 
> It saddens me to know that a shiny development board in the office will
> no longer be useful for anything else but its own physical beauty, but
> I believe that's a normal retirement strategy for a very early
> development platform :-)
> 

I'm afraid I have news for you. Even now, the board is almost unusable,
as the mvpp2 network driver only supports A0 (Z1 support was never even
planned).

So you have a NAS development board without network... sounds pretty
useless to me :)
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Make Armada 375 use the reference clock when possible
Date: Thu, 23 Oct 2014 09:43:29 -0300	[thread overview]
Message-ID: <5448F7F1.1080509@free-electrons.com> (raw)
In-Reply-To: <20141023142657.6b4d61fb@free-electrons.com>

On 10/23/2014 09:26 AM, Thomas Petazzoni wrote:
> Dear Ezequiel Garcia,
> 
> On Thu, 23 Oct 2014 09:16:33 -0300, Ezequiel Garcia wrote:
> 
>>> You don't clearly state whether your patch series keep compatibility
>>> with the 375 Z1 or not. And in fact, it doesn't keep compatibility with
>>> Z1. I'm fine with that, but then it means we should officially declare
>>> the Z1 support in mainline as dead, and get rid of the workarounds that
>>> applied only to 375 Z1.
>>
>> How many people have Z1 boards? And is someone actually using one for
>> something? Do we have any other reason to support Z1?
>>
>> FWIW, a v3.18-rc1 kernel built with mvebu_v7_defconfig, silently stalls
>> in the middle of the boot on Z1. Had to remove lots of compile time
>> options to make it boot.
>>
>> Before I start digging into this, maybe we can discuss your suggestion
>> to drop it. If nobody is booting this often enough, maybe nobody cares
>> about this, and it makes sense to drop the support?
> 
> Marvell has always said they are not interested in having Z1 supported
> in mainline, except as a first step to start getting the 375 support in
> mainline. I have been waiting for everyone of us to have access to 375
> A0 platforms, which is now the case. So I believe we can probably get
> rid of the 375 Z1 support entirely.
> 
> It saddens me to know that a shiny development board in the office will
> no longer be useful for anything else but its own physical beauty, but
> I believe that's a normal retirement strategy for a very early
> development platform :-)
> 

I'm afraid I have news for you. Even now, the board is almost unusable,
as the mvpp2 network driver only supports A0 (Z1 support was never even
planned).

So you have a NAS development board without network... sounds pretty
useless to me :)
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2014-10-23 12:45 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 13:34 [PATCH 0/4] Make Armada 375 use the reference clock when possible Ezequiel Garcia
2014-10-22 13:34 ` Ezequiel Garcia
2014-10-22 13:34 ` [PATCH 1/4] clocksource: armada-370-xp: Add missing clock enable Ezequiel Garcia
2014-10-22 13:34   ` Ezequiel Garcia
2014-10-22 13:50   ` Thomas Petazzoni
2014-10-22 13:50     ` Thomas Petazzoni
2014-10-22 14:37   ` Gregory CLEMENT
2014-10-22 14:37     ` Gregory CLEMENT
2014-10-22 13:34 ` [PATCH 2/4] watchdog: orion: Use the reference clock on Armada 375 SoC Ezequiel Garcia
2014-10-22 13:34   ` Ezequiel Garcia
2014-10-22 13:51   ` Thomas Petazzoni
2014-10-22 13:51     ` Thomas Petazzoni
2014-10-22 14:02   ` Andrew Lunn
2014-10-22 14:02     ` Andrew Lunn
2014-10-22 22:41     ` Ezequiel Garcia
2014-10-22 22:41       ` Ezequiel Garcia
2014-10-22 22:54       ` Guenter Roeck
2014-10-22 22:54         ` Guenter Roeck
2014-10-22 23:59       ` Andrew Lunn
2014-10-22 23:59         ` Andrew Lunn
2014-10-23  0:55         ` Ezequiel Garcia
2014-10-23  0:55           ` Ezequiel Garcia
2014-10-22 13:34 ` [PATCH 3/4] clocksource: armada-370-xp: Use the reference clock on A375 SoC Ezequiel Garcia
2014-10-22 13:34   ` Ezequiel Garcia
2014-10-22 13:54   ` Thomas Petazzoni
2014-10-22 13:54     ` Thomas Petazzoni
2014-10-22 15:22     ` Ezequiel Garcia
2014-10-22 15:22       ` Ezequiel Garcia
2014-10-22 13:34 ` [PATCH 4/4] ARM: dts: Enable the reference clock for timer and watchdog on Armada 375 SoC Ezequiel Garcia
2014-10-22 13:34   ` Ezequiel Garcia
2014-10-22 13:55   ` Thomas Petazzoni
2014-10-22 13:55     ` Thomas Petazzoni
2014-10-22 15:27     ` Ezequiel Garcia
2014-10-22 15:27       ` Ezequiel Garcia
2014-10-22 13:55 ` [PATCH 0/4] Make Armada 375 use the reference clock when possible Andrew Lunn
2014-10-22 13:55   ` Andrew Lunn
2014-10-22 13:56 ` Thomas Petazzoni
2014-10-22 13:56   ` Thomas Petazzoni
2014-10-22 14:08   ` Andrew Lunn
2014-10-22 14:08     ` Andrew Lunn
2014-10-22 14:25     ` Thomas Petazzoni
2014-10-22 14:25       ` Thomas Petazzoni
2014-10-22 15:29       ` Ezequiel Garcia
2014-10-22 15:29         ` Ezequiel Garcia
2014-10-23 12:36     ` Ezequiel Garcia
2014-10-23 12:36       ` Ezequiel Garcia
2014-10-23 12:16   ` Ezequiel Garcia
2014-10-23 12:16     ` Ezequiel Garcia
2014-10-23 12:26     ` Thomas Petazzoni
2014-10-23 12:26       ` Thomas Petazzoni
2014-10-23 12:43       ` Ezequiel Garcia [this message]
2014-10-23 12:43         ` Ezequiel Garcia
2014-11-03 21:29         ` Thomas Petazzoni
2014-11-03 21:29           ` Thomas Petazzoni
2014-10-22 14:43 ` Gregory CLEMENT
2014-10-22 14:43   ` Gregory CLEMENT
2014-10-22 14:49   ` Thomas Petazzoni
2014-10-22 14:49     ` Thomas Petazzoni
2014-10-22 15:10     ` Ezequiel Garcia
2014-10-22 15:10       ` Ezequiel Garcia

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=5448F7F1.1080509@free-electrons.com \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=alior@marvell.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=nadavh@marvell.com \
    --cc=tawfik@marvell.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=wim@iguana.be \
    /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.