Posted 21 July 2022 - 20:45
Also Blackhole has same modification on file "configure.ac" and "dvb.cpp" files, with "vmsg2" variable:
1) https://github.com/B...a01938f85dc6f68
2) https://github.com/B...lib/dvb/dvb.cpp
So this is the solution
And as you can see the commit is upgraded continously because new devices have same problem and has been added to the line. So this is the solution.
Edited by orator89, 21 July 2022 - 20:47.
Posted 21 July 2022 - 20:53
*VMSG_TYPE2
Posted 21 July 2022 - 21:26
Also OpenHDF has same modification with "VMSG_TYPE2" defined in the two files, and the tuner works perfectly, I tested now on my decoder. This is OpenHDF conf, like OpenATV:
1) https://github.com/o...er/configure.ac
2) https://github.com/o...lib/dvb/dvb.cpp
Posted 21 July 2022 - 22:08
@wanwizard
Please modify the two files adding "VMSG_TYPE2". THe modification is necessary because there is conflict of IOCTL in "Arm" processors, because "_IOC_NONE" is zero and "Arm" processor doesn't define "_IOC_NONE" causing conflict. Instead "Mips" processor define the "_IOC_NONE" and avoit conflict. In "Mips" you don't need "VMSG_TYPE2".
As you can read here:
https://githublab.co.../satip-client/3
If you read this you can understand what is the problem! On architecture different from "Mips", like "ARM", there is IOCTL conflict, and for that is necessary to define the "VMSG_TYPE2" variable. In the link a solution proposed is to develop an "auto-detect" to avoid the definition of variable "VMSG_TYPE2", but this "auto-detect" purpose is still not developed and for that you need to "to create manual exceptions for each new platform to be supported" about "ARM" decoders.
So you need to add manually the "VMSG_TYPE2" and box names like OpenATV and others images did.
Edited by orator89, 21 July 2022 - 22:10.
Posted 21 July 2022 - 22:10
I'll add it to the todo list.
What kind of device uses this chipset?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 21 July 2022 - 22:22
I'll add it to the todo list.
What kind of device uses this chipset?
My device with "Arm" processor is "uclan Ustym 4k Pro". But also Sf8008 and others with ARM cpu...
I think all the decoders you see in the line of "configure.ac" of OpenATV
if test "$BOXTYPE" == "vusolo4k" -o "$BOXTYPE" == "vuuno4k" -o "$BOXTYPE" == "vuuno4kse" -o "$BOXTYPE" == "vuultimo4k" -o "$BOXTYPE" == "vuzero4k" -o "$BOXTYPE" == "vuduo4k" -o "$BOXTYPE" == "vuduo4kse" -o "$BOXTYPE" == "cc1" -o "$BOXTYPE" == "sf8008" -o "$BOXTYPE" == "sf8008m" -o "$BOXTYPE" == "sf8008opt" -o "$BOXTYPE" == "sx988" -o "$BOXTYPE" == "ustym4kpro" -o "$BOXTYPE" == "ustym4kottpremium" -o "$BOXTYPE" == "gbmv200" -o "$BOXTYPE" == "beyonwizv2" -o "$BOXTYPE" == "viper4k" -o "$BOXTYPE" == "dagsmv200" -o "$BOXTYPE" == "og2ott4k" -o "$BOXTYPE" == "sfx6008"; then
AC_DEFINE(VMSG_TYPE2, 1,[define vtuner_message type 2])
fi
so they are "vu solo 4k", "octagon sf8008", "uclan ustym 4k pro" etc etc, the list is updated when new "Arm" or generally "not mips" decoder is out in the market... All those decoders have architecture "not MIPS", I think...
Posted 22 July 2022 - 09:40
Maybe so?
P.S.Looks like I'm wrong 
Edited by Dimitrij, 22 July 2022 - 09:46.
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Posted 22 July 2022 - 10:17
I see in your commit:
if test `uname -m | cut -b 1-3` == "arm"; then AC_DEFINE(VMSG_TYPE2, 1,[define vtuner_message type 2]) fi
but you have to talk with teams like OpenATV, I think that not all the "ARM" boxes have this problem maybe, because I don't see the "zgemma" models, for example, in the code of OpenATV... So I don't know if your modification that applies to all "arm" boxes is valid.
Edited by orator89, 22 July 2022 - 10:19.
Posted 22 July 2022 - 14:08
I also think that uname tests the ARCH of the build host, and not the platform being built?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 22 July 2022 - 14:24
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Posted 22 July 2022 - 14:37
Yes, I know.
But do we have a variable BOXTYPE available? Where is that defined? I see it is already used but I doubt that will work.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 22 July 2022 - 15:22
Yes, I know.
But do we have a variable BOXTYPE available? Where is that defined? I see it is already used but I doubt that will work.
This one:
AC_ARG_WITH(boxtype, [ --with-boxtype=NAME box type [[none,dm7025,dm800...]]], [BOXTYPE="$withval"],[BOXTYPE="dm800"]) AC_SUBST(BOXTYPE) AC_DEFINE_UNQUOTED(BOXTYPE,"$BOXTYPE",[box type])
thi "BOXTYPE" in "configure.ac" requires a "boxtype" defined already previously?
I checked both "Enigma2" repositories from Openpli and OpenATV, searching in all the files... In OpenATV there is this:
#check for default sat settings stbcheck=00 if [ -e /proc/stb/info/subtype ]; then stbcheck=`cat /proc/stb/info/subtype` fi if [ -e /proc/stb/info/boxtype ] && [ -e /proc/stb/info/chipset ]; then boxtype=`cat /proc/stb/info/boxtype` chipset=`cat /proc/stb/info/chipset` if [ $boxtype == "et7000" ] && [ $chipset == "bcm73625" ]; then stbcheck=01 fi fi
the file where it's, is "\tools\enigma2.sh.in"
I don't know if its the right file. If you want I can search also on the "oe alliance core 5.0" repository...
Posted 22 July 2022 - 17:43
I'm pretty sure we don't have that, all you can check is MACHINE or one of the ARCH variables.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 22 July 2022 - 19:09
OpenATV uses MACHINE for platforms and MACHINEBUILD for the actual box.
MACHINE=vusolo4k MACHINEBUILD=vusolo4k MACHINE=vuuno4k MACHINEBUILD=vuuno4k MACHINE=vuuno4kse MACHINEBUILD=vuuno4kse MACHINE=vuultimo4k MACHINEBUILD=vuultimo4k MACHINE=vuzero4k MACHINEBUILD=vuzero4k MACHINE=vuduo4k MACHINEBUILD=vuduo4k MACHINE=vuduo4kse MACHINEBUILD=vuduo4kse MACHINE=cc1 MACHINEBUILD=clap4k MACHINE=sf8008 MACHINEBUILD=sf8008 MACHINE=sf8008m MACHINEBUILD=sf8008m MACHINE=sf8008opt MACHINEBUILD=sf8008opt MACHINE=sx988 MACHINEBUILD=sx988 MACHINE=ustym4kpro MACHINEBUILD=ustym4kpro MACHINE=ustym4kottpremium MACHINEBUILD=ustym4kottpremium MACHINE=gbmv200 MACHINEBUILD=gbtrio4k MACHINE=gbmv200 MACHINEBUILD=gbip4k MACHINE=beyonwizv2 MACHINEBUILD=beyonwizv2 MACHINE=viper4k MACHINEBUILD=viper4k MACHINE=dagsmv200 MACHINEBUILD=dual MACHINE=og2ott4k MACHINEBUILD=og2ott4k MACHINE=sfx600 MACHINEBUILD=sfx600
Posted 22 July 2022 - 20:04
I think for OpenPLi the MACHINE list reduces to
MACHINE=vusolo4kMACHINEBUILD=vusolo4k MACHINE=vuuno4k MACHINEBUILD=vuuno4k MACHINE=vuuno4kse MACHINEBUILD=vuuno4kse MACHINE=vuultimo4k MACHINEBUILD=vuultimo4k MACHINE=vuzero4k MACHINEBUILD=vuzero4k MACHINE=vuduo4k MACHINEBUILD=vuduo4k MACHINE=vuduo4kse MACHINEBUILD=vuduo4kse MACHINE=sf8008 MACHINEBUILD=sf8008 MACHINE=sf8008m MACHINEBUILD=sf8008m MACHINE=ustym4kpro MACHINEBUILD=ustym4kpro MACHINE=gbmv200 MACHINEBUILD=gbtrio4k
Posted 22 July 2022 - 21:23
Weird that no zgemma / mutant / maxytec box is listed. And how about the Abcom Pulse 4K (which is identical to the never release Mutant HD61)?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 22 July 2022 - 22:56
I had a look in our build tree.
By default, /usr/include/asm-generic/ioctl.h is used, which contains
# define _IOC_NONE 0U
indicating the default.
These mipsel boxes seem to override that by using what I assume is mipsel specific asm code:
./dm8000-oe-linux/linux-dreambox/3.2-r14.20.90/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./osmini-oe-linux/linux-os/4.11-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./osminiplus-oe-linux/linux-os/4.11-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./osnino-oe-linux/linux-os/4.8.17-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./osninoplus-oe-linux/linux-os/4.8.17-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./osninopro-oe-linux/linux-os/4.8.17-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./fusionhd-oe-linux/linux-xsarius/4.2.1-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./fusionhdse-oe-linux/linux-xsarius/4.2.1-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./purehd-oe-linux/linux-xsarius/4.2.1-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./purehdse-oe-linux/linux-xsarius/4.2.1-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et7x00-oe-linux/linux-et-nextv/4.4.8-r0.1/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et8000-oe-linux/linux-et/4.10.6-r0.2/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et8500-oe-linux/linux-et-nextv/4.4.8-r0.1/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./h3-oe-linux/linux-zgemma/4.10.12-.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./h4-oe-linux/linux-zgemma/4.10.12-.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./h5-oe-linux/linux-zgemma/4.10.12-.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./h6-oe-linux/linux-zgemma/4.10.12-.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./i55-oe-linux/linux-zgemma/4.10.12-.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./alphatriplehd-oe-linux/linux-sab/4.1.24-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vipercombo-oe-linux/linux-amiko/4.10.6-r0.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vipercombohdd-oe-linux/linux-amiko/4.10.6-r0.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./viperslim-oe-linux/linux-amiko/4.10.6-r0.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./lunix-oe-linux/linux-qviart/4.2.1-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./xp1000-oe-linux/linux-xp/4.10.12-r1.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et4x00-oe-linux/linux-et/4.10.6-r0.2/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./osmega-oe-linux/linux-os/4.11-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vusolo2-oe-linux/linux-vusolo2/3.13.5-r2.7.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et10000-oe-linux/linux-et/4.10.6-r0.2/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vipert2c-oe-linux/linux-amiko/4.10.6-r0.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./sh1-oe-linux/linux-zgemma/4.10.12-.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./formuler1-oe-linux/linux-formuler/4.10.6-r3.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./formuler3-oe-linux/linux-formuler/4.10.6-r3.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./formuler4-oe-linux/linux-formuler/4.10.6-r3.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./formuler4turbo-oe-linux/linux-formuler/4.10.6-r3.0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et7000mini-oe-linux/linux-nextv/4.1.21-r0.8/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vs1000-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./hd11-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./hd1200-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./hd1265-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./hd1500-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./hd2400-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./hd530c-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./mbmicro-oe-linux/linux-mbmicro/4.0.1-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./mbmicrov2-oe-linux/linux-mbmicrov2/4.10.12-r0oea4.1-r3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./mbtwinplus-oe-linux/linux-mbtwinplus/4.1.24-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./spycat-oe-linux/linux-spycat/4.11-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./spycatmini-oe-linux/linux-spycat/4.11-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./spycatminiplus-oe-linux/linux-spycat/4.11-r0/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vuduo2-oe-linux/linux-vuduo2/3.13.5-r1.7.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vuduo-oe-linux/linux-vuduo/3.9.6-r5.5.5/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vusolo-oe-linux/linux-vusolo/3.9.6-r5.5.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vusolose-oe-linux/linux-vusolose/3.13.5-r1.7.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vuultimo-oe-linux/linux-vuultimo/3.9.6-r5.5.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vuuno-oe-linux/linux-vuuno/3.9.6-r5.5.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./vuzero-oe-linux/linux-vuzero/3.13.5-r1.7.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./xpeedc-oe-linux/linux-xpeedc-nextv/4.1.21-r0.8/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et5x00-oe-linux/linux-et/3.8.7-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et6x00-oe-linux/linux-et/3.8.7-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./et9x00-oe-linux/linux-et/3.8.7-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./hd500c-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./hd1100-oe-linux/linux-hd/4.10.12-r0.3/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U ./lc-oe-linux/linux-zgemma/4.10.12-.4/recipe-sysroot/usr/include/asm/ioctl.h:#define _IOC_NONE 1U
So it is indeed all ARM based CPU's that need this.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 23 July 2022 - 01:07
So it is indeed all ARM based CPU's that need this.
If so, why in all the "configure.ac" files of other images (OpenATV, OpenHDF, OpenVIX etc...), , with variable "BOXTYPE" to define "VMSG_TYPE2", there aren't listed "zgemma h9" and similar decoders that uses "ARM"?
Edited by orator89, 23 July 2022 - 01:08.
Posted 23 July 2022 - 08:08
Weird that no zgemma / mutant / maxytec box is listed. And how about the Abcom Pulse 4K (which is identical to the never release Mutant HD61)?
Edited by 4l3x2k, 23 July 2022 - 08:09.
Posted 23 July 2022 - 08:51
Weird that no zgemma / mutant / maxytec box is listed. And how about the Abcom Pulse 4K (which is identical to the never release Mutant HD61)?
If I look at the configure.ac from the satip client, then your missing boxes ala zgemma, mutant, maxytec and abcom actually appear there.Also with VMSG_TYPE2.But we're talking about usb tuner and not satip. I only mentioned satip because it also uses vtuner.
Ah, perfect! So maybe those decoders ARM, zgemma h7, h9 and others, were not added to "configure.ac" of enigma2 because no user needed vtuner USB on Zgemma H7 and similar that are combo devices with DVB-T2 included? Instead, a lot of people uses "SatIP" and because of this they were added in "configure.ac" of "satip", i suppose...
Edited by orator89, 23 July 2022 - 08:51.
0 members, 6 guests, 0 anonymous users
