From: moore@free•fr (Chris Moore)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: kirkwood: DT board setup for CloudBox
Date: Tue, 02 Apr 2013 06:17:10 +0200 [thread overview]
Message-ID: <515A5BC6.5000007@free.fr> (raw)
In-Reply-To: <20130401163316.GC16404@kw.sim.vm.gnt>
Hi Simon,
Le 01/04/2013 18:33, Simon Guinot a ?crit :
> On Sat, Mar 30, 2013 at 07:51:53AM +0100, Chris Moore wrote:
>
> Le 29/03/2013 19:41, Simon Guinot a ?crit :
>>> On Fri, Mar 29, 2013 at 11:31:32AM -0400, Jason Cooper wrote
>>>> On Fri, Mar 29, 2013 at 12:06:46PM +0100, Simon Guinot wrote:
>>>>> This patch adds DT board setup for the LaCie NAS CloudBox. The CloudBox
>>>>> is a low cost NAS based on the Network Space v2.
>>>>>
>>>>> Chipset list:
>>>>> - CPU MARVELL 88F6702 1Ghz
>>>>> - SDRAM memory: 256MB DDR2-800 (2x128MB x8) 400Mhz
>>>>> - 1 Ethernet Gigabit port (PHY MARVELL 88E1318)
>>>>> - SPI flash, NOR 512KB
>>>>> - 1 push button
>>>>> - 2 LEDs (red and blue)
>>>>>
>>>>> +
>>>>> +/ {
>>>>> + model = "LaCie CloudBox";
>>>>> + compatible = "lacie,cloudbox", "marvell,kirkwood-88f6702", "marvell,kirkwood";
>>>> Is there a more specific string we can add here? eg
>>>> "lacie,cloudbox-MODEL", "lacie,cloudbox", ...
>>> Unfortunately no. CloudBox is a product name which is also used by LaCie
>>> to name the board and the project.
>>>
>> I think it really is necessary to have a more specific name.
>> I have two, very different, products corresponding to LaCie CloudBox:
>> - The first one was a small black one with a 2.5" disk reviewed
>> here: http://www.smallnetbuilder.com/cloud/cloud-storage/462-lacie-cloudbox-reviewed
>> - The later one is a larger white one with a 3.5" disk described
>> here: http://www.smallnetbuilder.com/nas/nas-news/31927-lacie-relaunches-its-cloud-connected-nas
>>
>> IIRC the later one was originally called "CloudBox Family" although
>> maybe Family was dropped when it was officially released.
> Indeed, there is two (or rather one and half) released products called
> CloudBox.
>
> The old one (the first smallnetbuilder link) has been first called
> Network Space v2 mini, then SafeBox and finally released under the name
> Cloudbox. Very very few products have been sold. I don't know any owner
> and I suspect you got yours from the LaCie beta test program :)
>
Yes, in fact I was given both by LaCie for beta testing :)
Thank you, LaCie ;-)
> The new CloudBox is a very different product which has been first named
> FamilyBox and then released under the CloudBox name. Because the previous
> CloudBox was a really confidential product, the marketing guys have
> decided to reuse the name. This was a bad idea and despite the warnings
> they did that even so.
>
> Now, the fact is that the new CloudBox is a huge-selling LaCie product.
> That's why I propose to keep the names just as they are.
>
That is surprising: I greatly prefer the old black one, mainly because
it uploads autonomously with the PC powered off.
Are all the new ones white and all the old ones black?
If so, can't we add white to the name or at least specify in Kconfig
that it is the white version with a 3.5" disk?
Cheers,
Chris
next prev parent reply other threads:[~2013-04-02 4:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 11:06 [PATCH] ARM: kirkwood: DT board setup for CloudBox Simon Guinot
2013-03-29 15:31 ` Jason Cooper
2013-03-29 18:41 ` Simon Guinot
2013-03-30 6:51 ` Chris Moore
2013-03-30 15:08 ` Jason Cooper
2013-04-01 16:44 ` Simon Guinot
2013-04-01 16:33 ` Simon Guinot
2013-04-02 4:17 ` Chris Moore [this message]
2013-04-02 11:04 ` Simon Guinot
2013-04-02 11:45 ` Jason Cooper
2013-04-02 12:54 ` Simon Guinot
2013-04-02 17:24 ` Jason Cooper
2013-04-04 4:54 ` Chris Moore
2013-04-04 8:00 ` Simon Guinot
2013-04-04 9:34 ` Simon Guinot
2013-04-05 1:11 ` Jason Cooper
2013-04-05 5:14 ` Chris Moore
2013-04-08 17:00 ` Jason Cooper
2013-03-29 17:09 ` Andrew Lunn
2013-03-29 18:51 ` Simon Guinot
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=515A5BC6.5000007@free.fr \
--to=moore@free$(echo .)fr \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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