mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: moore@free.fr (Chris Moore)
To: linus-amlogic@lists.infradead.org
Subject: DT: newbie questions
Date: Tue, 16 May 2017 06:18:39 +0200	[thread overview]
Message-ID: <00d73329-ff75-5041-7400-1f52f18ca46e@free.fr> (raw)
In-Reply-To: <cda48375-3c3e-8871-2598-8405b387aaa4@free.fr>

Le 15/05/2017 ? 11:28, Chris Moore a ?crit :
> Hi,
>
> Sorry for these newbie questions :(
>
> I would like to add support for the cheap Chinese KI PLUS S905 boxes 
> which seem very popular.
> They are re-branded (or cloned) by several different vendors.
> In particular the most serious seem to be:-
> VideoStrong (http://www.videostrong.com/product.asp?sid=257)
> Acemax 
> (http://www.acemax.net.cn/droid-world/droid-box/hybrid-android-dvb-t2-dvb-s2/kii-pro-ki-plus-s2-t2-combo-149.html#.WRls_GjyiUk)
>
> I actually have an Xtreamer mxV (http://www.xtreamer.net/mxv) which 
> seems to be an exact clone.
>
> My first question is what to put in the compatible line.
> I could put:
> a) compatible = "videostrong,kiplus", "acemax,kiplus", "xtreamer,mxv", 
> "amlogic,meson-gxbb";
> but there are many other KI PLUS vendors so I could maybe omit the 
> vendor:
> b) compatible = "kiplus", "xtreamer,mxv", "amlogic,meson-gxbb";
> but this poses the problem of what to put in amlogic.txt which seems 
> to require a vendor.

Another solution to the multi-vendor problem could be to create a 
pseudo-vendor "generic" (or similar) and then have:
c) compatible = "generic,kiplus", "xtreamer,mxv", "amlogic,meson-gxbb";
Would this be acceptable?

>
> My second question is what to base my patch on:
> Should it be v4.12/dt64 in Kevin's linux-amlogic.git?
>
> My third question concerns the SDIO WiFi.
> The WiFi chip seems to vary between boards.
> My board has a Realtek RTL8189ETV.
> I note that its (unfortunately out of tree) driver is loaded even if 
> the DT specifies a Broadcom chip.
> Is it really necessary to specify the chip in the DT?
> (It seems that the SDIO, like the PCI and USB buses, recognizes 
> connected devices by their IDs.)
>
> My final question is how to submit my patch.
> Should I send an RFC to this list for approval before possibly 
> spamming others?
>
> I thank you in advance for your replies and your tolerance.
>
> Cheers,
> Chris Moore
>
> _______________________________________________
> linux-amlogic mailing list
> linux-amlogic at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>

  reply	other threads:[~2017-05-16  4:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15  9:28 Chris Moore
2017-05-16  4:18 ` Chris Moore [this message]
2017-05-16  8:08   ` Neil Armstrong
2017-05-16 10:51     ` Chris Moore
2017-05-17 15:41       ` Chris Moore
2017-05-17 15:44         ` Neil Armstrong
2017-05-18  8:01           ` GXBB: 4.12-rc1 boot failure (was DT: newbie questions) Chris Moore
2017-05-17 22:38     ` DT: newbie questions Kevin Hilman

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=00d73329-ff75-5041-7400-1f52f18ca46e@free.fr \
    --to=moore@free.fr \
    --cc=linus-amlogic@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

all inboxes | Powered by JetHome®