If I could help I would, but I don't understand a thing about making device trees. I once started reading the documentation, but I have zero background, so it's all chinese to me.
If I find another wetek core, I will contact you regarding Martin's adress.
Just test it on my M8S. Boots fine with the mxIII-plus dtb, but not with the M8S dtb.
Could test further as it seems I got a overload on the usb ports and now the usb doesn't work anymore. I hope there is some kind of overcurrent protection on this box, so when it's cooled down, it works again.
Regarding the wetek core. It seems there is no dtb for the wetek core in mainline.
Edit: My usb-ports don't work anymore...
It's a s812. I asked because this thread is for MIII-plus. So the dtb should match. Or can we select the appropriate dtb?
great news, should it work on the wetek core also? If not, is the sourcecode available on github, so we can build it ourselves?
You are correct. I think I'm getting crazy. I downloaded the latest kernel from github and unpacked it, I can't remember I patched it. But it seems I did. Time to go to sleep.
I just checked them in 5.10 and it seemed they where already there. Patch 01 is according me from line 1190 until line 1220 and patch 02 is on line1146 in sun50i-a64.dtsi
EDIT: my fault, seems my kernel was already patched. Just checked the kernel sources on github.
is it possible some patches are deprecated?
I'm talking about patch 01 and 02 frome here:
Is there a libreelec branch where we can find the necessary stuff to build test images for S805/S812? Or is there still to much hacking involved?
I'm interested in this inet1 stuff. The problem is with these tablets is that you should know which protocol the display is using. This should be defined in the dts to get it working. I don't have the knowledge to create such a dts, so a example of a working dts for a tablet would be a good starting point.
You can't use dtc anymore, there is a problem with changes of syntax. You should use on a arm system:
make dtbs to create all dtb's or
make sun4i-a10-cubiebaord.dtbNot me. Ubuntu is my daily driver.
Sorry for my misinterpretation. CDEX, although opensource, seems to be a windows app.
Not really. Kodi (and LibreELEC) is designed to be a application CLIENT. It is not meant to be a server. It does have SMB because Windows supports it basically as its only sharin, Linux can do both SMB and NFS quite easily. NFS server is not implement in LE because it would add to LibreELEC becoming bloated.
I don't have a problem with this, I just think it's easier to mount a directory structure from a nfs-server on linux then from a SMB server. My LE box has it own hdd, so I have to put files on it on regular base. And yes it would be easier to put everything on my PC or a NAS and serve it to LE. But I'm kind of a low electricity consumer nerd and don't want to run a extra device just to watch a movie.
Probably nfs would indeed just taking space on 90% of the LE-devices.
Personally I have never used that option in Kodi (or XBMC), not in the least because there are far better CD ripping applications available, such as CDex. After that, Kodi can import simply 'scrape' the .mp3 files in the usual manner.
Seems like most of the LE team is using windows as main OS. Now I understand why nfs-server in LE isn't available. As linux user it's a lot user friendly to use nfs over smb and probably more secure also. (totally off-topic, I know...)
I would mention jernej , unbeleivable how helpfull and calm he always is!
Please help me man!
First of all follow the wiki to get a build environment: Compile [LibreELEC.wiki] -> Stop at "Choose the PROJECT and ARCH to compile"
If you have done that, you should have a directory structure that is the same as the LE github page: GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI
What jernej is trying to tell you is:
-> Add correct lines to scripts/uboot_helper: open the folder scripts and search the file uboot_helper.
example: LibreELEC.tv/uboot_helper at master · LibreELEC/LibreELEC.tv · GitHub
In this file you will see all supported allwinner boards. Add the lines for your board. The correct name should be the same of the linux dts file and adjust it to resemble the other lines in the file. Look here: linux/arch/arm64/boot/dts/allwinner at master · torvalds/linux · GitHub
-> You have to create H2 section and add your board. Then copy project/Allwinner/devices/H3 to H2. After that, you're on your own:
go to your start directoy and browse to the folder /projects/allwinner/devices/
example: LibreELEC.tv/projects/Allwinner/devices at master · LibreELEC/LibreELEC.tv · GitHub
Make a new folder for H2 and copy the stuff from inside H3 to the new H2 folder.
Proceed the wiki Compile [LibreELEC.wiki] starting from
"Choose the PROJECT and ARCH to compile" and use the allwinner H3 example as base. Should be something like this:
PROJECT=Allwinner ARCH=arm DEVICE=H2 UBOOT_SYSTEM=(your_board_name_from_uboot_helper) make imageNo guarantee it will work so from there you are on your own.
If this is all to complicated, buy yourself a new board that is supported.
I want to do a PR; I only never done it before, so I have to find out how to do it first.
See attachement,
I tested a 32GB Pine64 emmc and the 64GB odroid emmc. The result is really disappointing. The pine64 emmc is slightly faster but it's not even 44MB/sec.
No problem, will do it this evening.
it's orange odroid 64GB emmc for odroid_N2. I just checked the odroid N2 dtb and indeed mmc-hs200-1_8v; should be enough. I can't read what's on the chip, the kids took my magnifier and I don't find it. I will ask them tomorrow because they are already sleeping.