Posts by chewitt

Write the .img.gz file to an SD card using the LE USB/SD Creator App .. same as any other image that LE offers

Quote from Pampat2014

The last image amlg12 ... X96 runs superbly on the bqeel y5

what device tree are you using? .. and what remote keymap (assuming it's the remote that ships with the box)?

"No rule to make target" means you're calling "make <something>" and <something> doesn't exist in the "Makefile" in the sources.

e.g. Makefile provides build targets for apples, pears and organges, but you're running "make apricots" which doesn't exist.

BT works fine with the commit I listed above - this chip is in a number of Amlogic boards that I'm poking right now. If you can point me to sources for those distros i'll have a look, but they're probably using the BCMDHD driver. This works, but there's no way we're switching from "supports everything except this one chip" well written/maintained upstream kernel code to "fugly out of tree Android BSP kernel cap" .. it would be retrograde step

I think the first step is to document the additional config required in our wiki so that anyone looking to use EAP understands how it's done; what info is needed and where the files need to live. Once that's understood, we can ask people to think about how

BCM4359 is not supported in the upstream kernel. brcmfmac4359-sdio experiments · chewitt/linux@a658583 · GitHub will result in card detection allowing BT to work but the driver has an issue loading WiFi firmware. I'm actively trying to resucitate an attempt to diagnose the issue with kernel maintainers, but it doesn't seem to have much traction with them yet - it will take time.

I cannot comment on the eMMC issue other than saying to check the UUID is correct.

Quote from Jedi

dtb used: gxl_p212_2g (i have tried many)

Device-trees from 3.14 kernel images are not compatible with the 5.1 kernel .. so the lack of boot is not surprising. PEBKAC.

I'm on a business trip for the next 4-5 days .. no access to toys.

Sounds like SD card corruption. Not much we can do about power-pull problems. Don't pull the cord!

Have a look at the mainline kernel images for Amlogic. I've no idea if those are any better, but at least the codebase is worth looking into for changes if not. I've boot tested 5.2rc4 kernel on C2 earlier today (current images are 5.1 kernel but an update will come soon).

I moved your post because the other thread is for mainline kernel images, not legacy kernel images.

If you mean the nVidia driver .. It was possible to custom build LE 7.x/8.x images with the older 304.xx driver and there's a thread for those images in the forum somewhere. Since LE 9.x the versions of Xorg and mesa we are using are no longer ABI compatible with the 304.xx driver and AFAIK there are no LE 9.x images with the necessary bits downgraded to make an image. Whatever hardware you have - if it's old enough to need that driver the performance of an RPi3 would be a huge upgrade.

HEVC is work in progress.

Quote from A.S._id

And I'm thought, about I not good enough know English, for understand it. 😂

гугл переводчик не хороший - напиши английский перевод, также напиши оригинальный русский - тогда мы понимаем

Quote from afl1

I already tried to upstream first patch to [email protected] on Feb 3, but no answer. It was pinctrl for tsin pins.

LibreELEC.tv/linux-99999-pinmux.patch at master · 150balbes/LibreELEC.tv · GitHub

The kernel maintainers provided feedback on the patch submission so you need to submit v2 with the requested changes. For that patch I can see the following issues:

a) Lines over 80-characters

b) Subject line should be something like "pinctl: meson: add tsin pins for meson gxbb/gxl/gxm"

c) No "Signed-of-by Jan Afl <[email protected]>" line

One of the lessons everyone learns the hard way is there is zero negotiation on kernel code style .. and typo's count

Run scripts/checkpatch.pl on patches to check for common style/format errors before resending. Run scripts/get_maintainer.pl on the the file being changed to get the list of email addresses to send the patch to.

I recommend you reach out to Neil Armstrong and Kevin HiIlman to discuss how to submit the driver. I know Neil has looked at the current changes in your repo and there are some structural issues to resolve. It will be easier to know what the main objections are (and address them) before you send the next set of changes.

p.s. If you need any assistance please just ask. We all want this code to go upstream and we greatly appreciate the effort it will take.

Okay, good to know. Thanks.

escalade what's the plan to submit an Exynos build project? .. GBM/V4L2 will improve with the stateful decoder work that's planned/pending for Amlogic and Rasbperry Pi (which share the same code path).

Kestouf I normally ask HK directly if we need board samples; then they're aware of who's active within their developer community.

ping CvH