Posts by chewitt

The one reference to that PHY that I found on Google was on schematics for the Rock64 (a Rockchip device) but marked optional, and TL Lim who makes that board says he has no memory of looking at ZTE parts. I've asked internal to Amlogic as well, but if it's only been used in a handful of devices I wouldn't be too hopeful.

It might be possible to capture and then force the EDID via kernel boot params. The raw EDID data and override location is probably under the /sys/kernel path somewhere, but I have no idea what the specific steps are for a Rockchip 4.4 kernel.

The normal complaint about slow Ethernet on recent/mainline kernel is solved by disabling eee in device tree or from userspace via ethtool.

See linux/meson-gxbb-odroidc2.dts at master · torvalds/linux · GitHub .. although that dts is for mainline kernel so that binding might not exist in the older BSP kernels.

I can ask contacts, but replies to random Q's (vs. things we're working on) are never quick.

because it's a "code doesn't exist" issue, not something that can be reconfigured after spotting a problem in a log file

Android only due to the locked bootloader.

An 802.11n device with dual antenna supporting 5GHz modes and a well written driver will outperform the latest 80211.ac hardware with a crap driver. And 802.11n hardware might not make use of the full 802.11ac featureset, but it's fully compatible with 'ac' routers. And if you want your media to play reliably you'll run an Ethernet cable, because ultimately all wireless leads to disappointment

Last time I looked on eBay there were still plenty of 'Virgin' branded WNDA3200 adapters (which use ath9k) going cheap. I bought a couple for £4/each but that was a while ago. Use wikidevi to find other brands/models.

3B+ is considerably better than B3 for radio things. The next alpha release will have some BT firmware improvements for the RPi3B+ that reduce interference with wireless (which is usually active at the same time even if you're using Ethernet) which might help.

Logs won't make a difference, it's just something that's not currently supported. Hopefully that changes over time with more development.

I have the 65" version of the same LG panel and a similar AVR and a legion of test boxes/devices to experiment with. The short answer to the question is "the box you are seeking does not exist" .. and on that basis I'd go pick up a cheap S905D box with GB ethernet (avoid the S905D devices with 100-BaseT PHYs). It'll be fairly cheap so when you chuck it out in 24 months time to get a newer (still not meeting that spec, but more advanced in some way) device you're not left writhing in angst about how much it cost you.

NB: Nothing truly supports HDR on Linux right now, but Amlogic is the leading "least worst" option at the current moment

The LE staff have a generally low opinion on Realtek wireless devices. The hardware is probably reasonable, and performance on Windows is probably great because that's where they invest all the Engineering time. Their Linux drivers are an afterthought, and we're fed up with they way they breed chipsets and new drivers that rehash the same greatest-hits compilation of hacks over and over.

Find something that uses the ath9k driver, which is in-kernel and much higher quality code.

The moral of your story is buy a USB wireless dongle that has a decent chipset and in-kernel driver, not some piece of realtek crap.

LibreELEC is intended for dedicated HTPC devices so Kodi (on LibreELEC) runs full-screen and outputs to the primary display device (whatever that is) and there is no GUI support for running with multiple-monitors (or laptop screen + HDMI output). It can be done from the command line, but that's more advanced. Another option for a laptop could be forcing the display output in the BIOS.

If you want GUI multi-monitor support, use Windows or a conventional distro like Ubuntu.

Which kernel? .. DS1307 has been enabled in our Raspberry Pi kernel config since 2013.

RPi.GPIO is part of the "RPi Tools" addon in our repo and should work exactly the same way (the wheel wasn't reinvented).

Update to the current 8.90.003 alpha which has newer drivers (newer everything) and retest.

It's hard to comment without knowing what hardware you have, which driver that unknown hardware is trying to use, and which OE/LE versions you're comparing?

Sorry I thought you were trying to play media using Kodi. Chrome runs outside Kodi (in the OS core) and nothing is logged. Most issues are down to the media being played being 1080p and requiring hardware decoding; and hardware decode not working. What does Chrome show for those settings?

Amlogic hardware isn't the best with 3D media (AFAIK not all 3D formats are supported) and an S905X device will struggle with full-size ISO rips due to the 100Base-T ethernet port being slow for the large size of media files. Raspberry Pi 3B+ has GB ethernet (not full speed to the internal USB 2.0 bus but good enough) and the best 3D playback support of any Kodi device; the Pi Foundation staff put a lot of effort into their (pi only) hardware decoders.