Hi,

On 13-08-15 08:45, Siarhei Siamashka wrote:
On Tue, 11 Aug 2015 13:53:53 +0200
Hans de Goede <[email protected]> wrote:

Hi,

On 11-08-15 13:43, Siarhei Siamashka wrote:
On Sun, 09 Aug 2015 21:44:00 +0200
Olliver Schinagl <[email protected]> wrote:

<snip>

In my case, all the Allwinner hardware that I have is already supported
by the mainline u-boot. Except for the http://linux-sunxi.org/Hyundai_A7
tablet. I could easily contribute support for it to the mainline
u-boot, but I strongly dislike the fact that it is probably a trademark
violating counterfeit product. I surely don't want to be listed as a
maintainer for this thing :-) But if anyone wants to add support for
this tablet under his own name, I'll be happy to provide assistance.
I may even post patches for this tablet *without* my S-o-b.

How about submitting a u-boot defconfig and dts file with a different
name for the board, e.g. Allwinner_M723GDX_defconfig and
sun4i-a10-allwinner-m723gdx.dts ? Then we can point people to this
defconfig in: http://linux-sunxi.org/Hyundai_A7

That's an interesting suggestion. So in other words you suggest to treat
this tablet just like any no-name tablet without identification labels?

Yes.

Furthermore, you suggest to use Allwinner as the dts vendor name.

Yes, because in the dts we must provide a vendor name, we do the
same with e.g. the mk802 which is made by a lot of different vendors, see:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/sun4i-a10-mk802.dts

Which has:

        compatible = "allwinner,mk802", "allwinner,sun4i-a10";

For the board compatible. Note that in this case we do not have
allwinner in the dts filename, thinking more about this I think this
probably best to do for the tablet in question too, so name the dts
file: sun4i-a10-m723gdx.dts nad the u-boot defconfig m723dx_defconfig.

And for the board compatible use:

        compatible = "allwinner,mk723gdx", "allwinner,sun4i-a10";

I'm not sure if Allwinner would be happy to have such a honour

See above, this would leave allwinner only as the vendor in the
board compatible, where allwinner is already present anyways
since they are the SoC vendor.

but this
is none of my concern as long as everything is done according to the
official linux kernel and/or dts policy. Could you please provide a
reference to the relevant documentation if it exists, or do some work
on making sure that such documentation is created?

I'm afraid that there is no documentation on this specifically, nor
would I know where exactly to document it, but there is a clear
pattern for how to deal with generic boards where we do not have
a clear vendor, and that pattern is that they all do as described
above, so I think that treating your tablet as coming from a generic
vendor and then using the above pattern is a good solution.

Mainlining support for this tablet is not very high in my priority
list. It is basically a junk hardware from a questionable vendor
( http://www.hyundai-digital.cn ), which even does not exist anymore.
I don't know if they were shut down because of the official Hyundai
complaint (searching on google shows a few examples of Hyundai
trademark related lawsuits) or just went out of business because they
were not profitable enough. Still, if there are actual users who are
stuck with this hardware and want to have it mainlined, then we can
see what can be done.

Before you were pointing out that one problem with retiring the old
u-boot branches was that they still support boards mainline u-boot
does not, the only way to fix this is one board at a time.

So if you've some time, please add support for this tablet to
mainline u-boot.

Anyway, this was just one example of the Allwinner based hardware
without mainline U-Boot support. I even did not remember about it
until Olliver brought attention to this topic :-) We are yet to decide
about what to do with the wiki pages for such hardware in order to
make sure that the users do not get confused (this was the
Olliver's intention, right?). And unless there is further feedback
and good constructive suggestions, it looks like the git branches
of the u-boot-sunxi repository are best to be kept as they were.

Hmm, I'm really with Olliver on this one that the time has come
to retire the old u-boot branches.

Lets see which boards are supported by the old u-boot which are
not supported by mainline u-boot :

A10_MID_1GB             no one really knows what this is, it seems to come from 
the SDK and not a real thing, it has no wiki page
Coby_MID7042            http://linux-sunxi.org/Coby_MID7042
Coby_MID8042            no wiki page
Coby_MID9742            no wiki page
Iteaduino_Plus_A10/A20  http://linux-sunxi.org/Itead_Iteaduino_Plus
DNS_M82                 no wiki page
EOMA68_A10/A20          no wiki page, did these things ever actually ship ?
EU3000                  http://linux-sunxi.org/Wedo_HD22
Forfun_Q88DB            http://linux-sunxi.org/Forfun_Q88DB
Gooseberry_A721         http://linux-sunxi.org/Topwise_A721  I have one of 
these I'll add support soon-ish
H6                      http://linux-sunxi.org/Eearl_H1026A A10 netbook
Hackberry               http://linux-sunxi.org/Hackberry
HBD_MID_S906            no wiki page
HCore_HC860             no wiki page
HSG_H702                http://linux-sunxi.org/HSG_H702
Hyundai_A7              http://linux-sunxi.org/Hyundai_A7
ICOU_Fatty_I            http://linux-sunxi.org/ICOU_Fatty_I
Interra-3               http://linux-sunxi.org/Yonnet_Interra-3
INet_86VZ               http://linux-sunxi.org/Inet_86vz
INet97F-II              http://linux-sunxi.org/Inet_97f
INet_K70HC              http://linux-sunxi.org/Inet_k70hc
K1001L1C                no wiki page
Kurio_7S                http://linux-sunxi.org/Kurio_7S
Langcent_H6S            http://linux-sunxi.org/Langcent_h6s
Marsboard_A20           http://linux-sunxi.org/MarsBoard_A20
Megafeis_A08            http://linux-sunxi.org/Megafeis_a08
merrii_m2               no wiki page
OLIMEX-A13-SOM          http://linux-sunxi.org/Olimex_A13-SOM
Olimex_A20-SOM          http://linux-sunxi.org/Olimex_A20-SOM
pengpod700              no wiki page
pengpod1000             no wiki page
pineriver-h25           http://linux-sunxi.org/Pineriver_H25
POV_TAB_P703            http://linux-sunxi.org/Q8
PoV_ProTab2_IPS9        no wiki page
PoV_ProTab2_IPS_3g      no wiki page
PoV_ProTab2_XXL         http://linux-sunxi.org/Inet_1
prestigio_pmp3670b      no wiki page
Sanei_N90               http://linux-sunxi.org/Sanei_N90
T702A                   no wiki page
TXCZ_A20                http://linux-sunxi.org/TXCZ_A20
TZX-Q8-713B6            http://linux-sunxi.org/TZX-Q8-713B6
uhost_u1a               http://linux-sunxi.org/Smallart_Uhost1  I have one of 
these I'll add support soon-ish
wobo-i5                 no wiki page  I have one of these I'll add support 
soon-ish
xzpad700                no wiki page
YBKJ_A20_JN             http://linux-sunxi.org/YBKJ_A20

I suggest that we simply forget about the ones without a wiki page, and for the 
other we
should probably try to contact the creator of the wiki page.

Olliver do you feel up to contacting these people?

Regards,

Hans

--
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to