From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 09/10] Documentation: devicetree: rockchip: Document Landingship
Date: Mon, 8 Feb 2016 11:51:04 +0100 [thread overview]
Message-ID: <56B87318.9020007@suse.de> (raw)
In-Reply-To: <6744409.i2u8076vm4@phil>
Am 08.02.2016 um 11:29 schrieb Heiko Stuebner:
> Am Montag, 8. Februar 2016, 03:17:38 schrieb Andreas F?rber:
>> Use "geekbuying,landingship" compatible string, plus those of GeekBox.
>
> I do believe this would be better as geekbuying,geekbox-landingship . They
> might reuse the landingship naming for future baseboards as well ;-)
Well, the question is: Is this MXM3 interface as generic as Qseven so
that it could be used as is for other modules (and baseboards from other
manufacturers could be used for the module)? Then my thought was
landingship as identifier for the baseboard and geekbox as identifier
for the contained module.
I agree that if this Landingship is specific to the GeekBox then
geekbox-landingship would be more appropriate. We could also do both.
Can you tell? Unfortunately I spot no real documentation of the MXM3
connector pins in the schematics we could compare, only an on-board
documentation of the three-row pins.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2016-02-08 10:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 2:17 [PATCH v2 00/10] ARM64: rockchip: Initial GeekBox enablement Andreas Färber
2016-02-08 2:17 ` [PATCH v2 01/10] Documentation: devicetree: Add vendor prefix for GeekBuying.com Andreas Färber
2016-02-08 21:27 ` Rob Herring
2016-02-08 2:17 ` [PATCH v2 02/10] Documentation: devicetree: rockchip: Document GeekBox Andreas Färber
2016-02-08 21:28 ` Rob Herring
2016-02-08 2:17 ` [PATCH v2 03/10] ARM64: dts: rockchip: Add GeekBox config Andreas Färber
2016-02-08 2:17 ` [PATCH v2 04/10] ARM64: dts: rockchip: Add GMAC to GeekBox Andreas Färber
2016-02-08 10:28 ` Heiko Stuebner
2016-02-08 10:40 ` Andreas Färber
2016-02-08 2:17 ` [PATCH v2 05/10] ARM64: dts: rockchip: Add eMMC " Andreas Färber
2016-02-08 2:17 ` [PATCH v2 06/10] ARM64: dts: rockchip: Add IR receiver " Andreas Färber
2016-02-09 3:08 ` Andreas Färber
2016-02-09 10:45 ` Julien Chauveau
2016-02-08 2:17 ` [PATCH v2 07/10] ARM64: dts: rockchip: Add power key " Andreas Färber
2016-02-08 16:26 ` Julien Chauveau
2016-02-08 2:17 ` [PATCH v2 08/10] ARM64: dts: rockchip: Add tsadc for GeekBox Andreas Färber
2016-02-08 2:17 ` [PATCH v2 09/10] Documentation: devicetree: rockchip: Document Landingship Andreas Färber
2016-02-08 10:29 ` Heiko Stuebner
2016-02-08 10:51 ` Andreas Färber [this message]
2016-02-08 2:17 ` [PATCH v2 10/10] ARM64: dts: rockchip: Add Landingship config Andreas Färber
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=56B87318.9020007@suse.de \
--to=afaerber@suse.de \
--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).