From: simon.guinot@sequanux•org (Simon Guinot)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: kirkwood: DT board setup for CloudBox
Date: Mon, 1 Apr 2013 18:44:11 +0200 [thread overview]
Message-ID: <20130401164411.GD16404@kw.sim.vm.gnt> (raw)
In-Reply-To: <20130330150807.GQ13280@titan.lakedaemon.net>
On Sat, Mar 30, 2013 at 11:08:07AM -0400, Jason Cooper wrote:
> On Sat, Mar 30, 2013 at 07:51:53AM +0100, Chris Moore wrote:
> > Hi Simon et al.
> >
> > Le 29/03/2013 19:41, Simon Guinot a ?crit :
> > >On Fri, Mar 29, 2013 at 11:31:32AM -0400, Jason Cooper wrote:
> > >>Neat! another new board!
> > >Others are coming :)
> >
> > That's great, thank you.
> >
> > >>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
>
> In this case, we usually look for a model number on the back and append
> that to the compatible string. There are three model numbers listed
> here [1] under specifications, based on capacity.
Hi Jason,
I don't believe this numbers are related with the board. I will check
but IMHO "lacie,cloudbox" is a correct compatible string.
Thanks,
Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130401/5eb8734a/attachment-0001.sig>
next prev parent reply other threads:[~2013-04-01 16:44 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 [this message]
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
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=20130401164411.GD16404@kw.sim.vm.gnt \
--to=simon.guinot@sequanux$(echo .)org \
--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