Posts by roel

I understand, but what makes the pinetab so nice is that you can switch a OS by only throwing in another µSD-card. So If you want to run your media isolated from your other stuff, you can use a LibreElec SD-card. Or you want to play your ancient games through a emulator and you need the maximum of the resources to play them full speed, you can use Lakka. If you have a home party and you want to control your music with your tablet without the risc visitors start sniffing in your personal documents you can use a squeesebox OS.

Maybe my point is not so clear, but I have a LibreElec-box connected to my TV. Why didn't I put a ordinary PC next to my TV with Kodi installed?

Can I find somewhere some documentation how to properly specify regulators? Is it related to the type of eemc or the size or the board?

Jernej,

I have a problem with odroid emmc on the pineH64. It gives this message during boot: sunxi-mmc 4022000.mmc: data error, sending stop command

I see you fixed it for the Tanix T6 with this patch:

But I don't find this patch in your LibreElec patches for Allwinner H6, only this one: LibreELEC.tv/13-Tanix-TX6.patch at master · LibreELEC/LibreELEC.tv · GitHub

The LE patches are only patches for the dts of the Tanix TX6, does this mean if I apply these patches in the pineH64 dts, the board will boot from emmc? Probably it's a better fix that enables the HS DDR mode?

OK,

so not necessary to do a poll?

Otherwise I remove it.

As the PineTab is available for pre-order, I wonder if there is any interest from the LE-userbase to have LE running on the PineTab.

The main reason for me to get LE on the PineTab is the kids. So they can watch some movies, read a comic, listen to music or podcast in the car. LE is easy to set-up, play's almost all formats, connects to a lot of server protocols (when you put a little dlna server in the car, with those mobile routers).

But probably other people have other reason's.

On the other hand, everybody has already a tablet and is not waiting for a second tablet with (to be honest) low specs running a unknown OS. So LE would be a great selling point, especially for this price point.

I don't have this problem. Go to Index of / and choose the image you need.

This is really good news, thanks for sharing and thanks to Martin for not giving up and all the invested hours.

It's realy stunning: the latest kernel, lima and a pre-alpha kodi!

Armbian has a dts for it: Add preliminary support for Orangepi Lite 2 H6 · armbian/build@d4f52f8 · GitHub

To be honest, I have already problems with DVD mounting/ejecting with a usb dvd-rom since I started with openelec. I never made a point of it as DVD's are something I seldom use. Only for the kids,but I make a habit of it to rip them immediately and put them on the server. This way I can avoid the kids to see all the "commercials" they have to watch first.

Altough, really of topic, but a strange problem I have all these years is when I put in a DVD, my external usb-drive isn't recognised anymore. For example when a DVD is inserted I can't start a movie that is located on the external hdd. Then I have to eject the DVD and restart LE, only then my external hdd is recognised. I first taught it was a power issue, but I gave the hdd-drive and the DVD-drive a separate power supply, but the issue persist.

Not that I expect it should be solved, the dev's have more important stuff to do that affects more users.

This is his question from OP:

Quote from MrSoul

So, here is my question, can we modify the LibreElec parameters to add the SCSI ejection option so that it works directly from the interface?

Or, can we add a shortcut on a joystick to have a SCSI ejection?

Seems he knows it is mounted as SCSI, he asks how he can eject his DVD from the interface when it is mounted as scsi.

Quote from roel

jernej seems its parallel. It's certainly not LVDS is this one is not enabled. The fex section describes it as lcd_para so I assume this means parallel. I think this is out of my league but maybe I find a site with some good explanation. I already found this: ST Community

but I'm still confused about this drm/kms stuff.

I see somebody just recently is working on DRM/KMS for LVDS screens on the A20: Re: [linux-sunxi] LVDS screen on Cubieboard 2 (Allwinner A20) via DRM/KMS

jernej seems its parallel. It's certainly not LVDS is this one is not enabled. The fex section describes it as lcd_para so I assume this means parallel. I think this is out of my league but maybe I find a site with some good explanation. I already found this: ST Community

but I'm still confused about this drm/kms stuff.

Quote from jernej

Anything can run LE if it uses DRM driver and GPU driver which supports GBM interface. You just need to figure how to properly describe LCD panel in device tree. But I'm not right person to help you with that, I don't have experience with any output besides HDMI.

OK, I will see if I can get further with this, I see in the pinephone dtb these lines that refer to the screen:

&dsi {
	vcc-dsi-supply = <&reg_dldo1>;
	#address-cells = <1>;
	#size-cells = <0>;
	status = "okay";

	panel@0 {
		compatible = "xingbangda,xbd599";
		reg = <0>;
		reset-gpios = <&pio 3 23 GPIO_ACTIVE_LOW>; /* PD23 */
		backlight = <&backlight>;
	};
};

So probably it will be something regarding dsi. For the moment I don't find a specific A20 dtb for tablets using mainline.

Quote from jernej

simple-fb (U-Boot initialized screen) is not useful for LibreELEC.

So I have this projector running android on a A20. In the fex file, hdmi is disabled and lcd is enabled. So it seems the projector works through the lcd interface. On the sunxi pages it is mentioned that a custom u-boot should be build and the data in the fex file should be converted to u-boot config. But now you say this will not work on LE because it doesn't us simple-fb? How can I make LE picture through the projector then?

Would you say: don't bother, don't waist your time. Because this would means that LE will not work on any tablet, right?

jernej

it seems to activate a lcd screen it has to happen in uboot. So if I build a new custom uboot, can I use a already flashed image and just dd the new uboot to the sd-card like this:

dd if=u-boot.bin of=/dev/mmcblk0 bs=1024 seek=32 

Quote from myxal

Not quite sure what that does, but here's what looks relevant from A1000 fex file:

Code

[usbc0]
usb_used = 0
usb_port_type = 0
usb_detect_type = 0
usb_id_gpio =
usb_det_vbus_gpio =
usb_drv_vbus_gpio = port:PB09<1><0><default><0>
usb_host_init_state = 0

[usbc1]
usb_used = 1
usb_port_type = 1
usb_detect_type = 0
usb_id_gpio =
usb_det_vbus_gpio =
usb_drv_vbus_gpio = port:PH06<1><0><default><0>
usb_host_init_state = 1

[usbc2]
usb_used = 1
usb_port_type = 1
usb_detect_type = 0
usb_id_gpio =
usb_det_vbus_gpio =
usb_drv_vbus_gpio = port:PH03<1><0><default><0>
usb_host_init_state = 1

Display More

OK usbc0 is disabled in the fex. So dtb should be OK. I don't see any differences.

Quote from jernej

Not sure what's going on.

Probably something with these lines in dtb:

&usbphy {
	usb1_vbus-supply = <&reg_usb1_vbus>;
	usb2_vbus-supply = <&reg_usb2_vbus>;
	status = "okay";
};

in most other dtb's it something like this:

&usbphy {
	usb0_id_det-gpios = <&pio 7 4 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>; /* PH4 */
	usb1_vbus-supply = <&reg_usb1_vbus>;
	usb2_vbus-supply = <&reg_usb2_vbus>;
	status = "okay";
};

Same error message on the MELE A1000. I have also a cubieboard A10. Is it just a matter of changing dtb's?