From: moore@free•fr (Chris Moore)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: kirkwood: DT board setup for CloudBox
Date: Thu, 04 Apr 2013 06:54:14 +0200 [thread overview]
Message-ID: <515D0776.7050208@free.fr> (raw)
In-Reply-To: <20130402172454.GT13280@titan.lakedaemon.net>
Hi,
Le 02/04/2013 19:24, Jason Cooper a ?crit :
> On Tue, Apr 02, 2013 at 02:54:11PM +0200, Simon Guinot wrote:
>
...
>> There is two different LaCie boards. There is no relations between this
>> boards except their final product name (which is quite silly).
>>
>> From a LaCie point, there is no board but only product naming. Here are
>> the different names used by LaCie for this two boards/products:
>>
>> 1: netspace_mini_v2 -> SafeBox -> CloudBox
>> 2: FamilyBox -> CloudBox
>>
>> "1" is the oldest board.
> Got it.
I may be thick but I didn't realise that my old black CloudBox was
already supported under the name netspace_mini_v2 :(
There is no reference to CloudBox anywhere in the kernel; only the
SafeBox alias (of which I was also unaware) is given in Kconfig.
>> Under Linux, with my patch we are using the following names:
>>
>> 1: netspace_mini_v2
>> 2: cloudbox
>>
>> The problem raised by Chris is that the cloudbox name could be
>> confusing because one could try a "cloudbox" dtb on the board "1". For
>> my part I don't think it is an issue because "1" is rather confidential
>> (and it is an euphemism).
> Agreed.
I wasn't aware that the original CloudBox was so confidential.
I even saw them for sale in my local FNAC (a hi-tech and media shop
present in most large French shopping centres).
>> It would be more confusing for users if the kernel name for "2" is not
>> cloudbox but cloudbox_{color,number,...} or even familybox. Moreover
>> netspace_mini_v2 is a correct name for "1".
>>
>> IMHO, we could let things as they are. Additionally, I could either
>> extend the Kconfig description and add a some comments in the dts files,
>> in order to to prevent any misunderstanding...
>>
>> Let me know if you agree or not.
> Yes, that makes more sense. Thanks for clearing it up. Please add the
> clarifying remarks to the dts.
I agree that it would be confusing to change the netspace_mini_v2 name now.
In view of all the above, please disregard my objection.
Sorry for the noise :(
> As for the model number for the public board (#2), why can't we append
> "-90003xx"? See [1], Specifications tab.
>
> [1] http://www.lacie.com/us/products/product.htm?id=10597
This seems like a good idea to me but I don't think Simon favoured
adding a model number.
In any case Simon would know better than me whether this covers the
models correctly.
What do you think, Simon?
Cheers,
Chris
next prev parent reply other threads:[~2013-04-04 4:54 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
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 [this message]
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=515D0776.7050208@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