About: ""Add bad block table implementation" BREAKS all other NAND devices that use BBT-pattern"
Of it looks like the best way but this should done by a person that are have contact to the Kernel-developer and do know what are BBT are.
Them i guess it need long time to implement and a result ( so i guess ) are an extra Kernel config parameter.
For this reason it is not better to add a new Kernel parameter like MTD_NAND_CUSTOMIZED_BBT_VGV952CJW33EIR and hatches this service to ./config/Config-kernel.in
Because there is an other problem: the Easybox-904xDSL need a special openwrt-config like:
Or is this not a Problem ?
But at the moment i can not test i have some strange read errors on mtd device and i have not idea if it a hardware error, a problem with this devicetype or an general linux problem.
While that might make things a bit neater, it won't really help the problem at hand, as the same kernel image is shared among all devices of a (sub-)target. Meaning if you need to enable your hypothetical MTD_NAND_CUSTOMIZED_BBT_VGV952CJW33EIR, and you do, if you want to support the EB904xDSL, you break all other xrx200 devices with NAND at the same time - nothing won. What would be needed here is some way to influence the kind of BBT at runtime, either by adding some kind of quirk for the EB904xDSL or maybe DTS side configuration.
Yes, those are a problem, but compared to BBT and switch support an optional one (display/ touchscreen don't 'need' to work for basic device support --> defer to stage 2).
This is not a problem. DEVMEM is used only to set needed MAC delay settings for port, where Ralink WiFi SoC connected. We can extend device tree parameters for xrx200 ethernet port to set this delay in the register. It just where done as DEVMEM manipulations in original firmware from Arcadian, but, indeed, this is a MAC settings register.
There a alot of things that fail and can be the reason for the different errors:
So i do not explore for it because it sucks, anything is always wrong since months,
It was not possible to build an stabel fullworking image.
(I build USB-Storage and f2fs inside my kernel)
At the moment i try to build a solution for the special-NAND-bbt-patch-destroy-other-devices problem.
I use minimal images without f2fs and USB-storage support and they are working (but possible that my Flash are defect on a higher position)
If you use the extra Kernel.config from post
do not use this part:
Starting from USB-Stick does not really working too because:
It starts fine from USB-Stick but the overlay-fs is on UBI0_1 (from the size it looks like mtd12).
And this make not really sense.
How can i change it and not using any overlay-fs or using it on /dev/sda1 (f2fs)
@slh: Thanks, I also put on my old EasyBox 802 with LEDE 17.04 build and analysed that the Ralink 2870 chipset there is also still fragile. You can use the chipset already as a WWAN and AP at the same time, but usually then the wifi breaks with heavy load completly and takes a minute to come up again.
The driver says it should be possible to use it in mesh-networks, but unfortunately a test with an WR801v2 with working mesh-options don't work proper with this Ralink (shit) devices....
Is there any idea if also NF offloading will be enabled in the near future for Ralink-chipsets? As I understand other discussions there is usually only Atheros chipset support... unfortunately.
So still continueing to find a good working device...
It's so annyoing with the Easyboxes. They all have a descent hardware (RAM, Flash, CPU), but always lacks of driver support. - Especially the Easybox 904 with a price < 10€ a lot of RAM and Flash, fast CPU should be a perfect development plattform for openwrt and should get supported offically!
LCD does not work on my build @takimata why did you think that fb-tft includes ILI9341 ?
I see no message in dmesg and no /dev/fb device exist.
I can not see any ILI9341-kmod.
A kmod-fb-tft-ili9486 exist but it is an other device.
An other thing are:
When enablening FB-devices the following lines are missed in kernelconfig and it is not possible to make an build without stopping, or adding this lines:
of course you can use the kernel packages that are include the my archiv-file in path packages only.
(the kernel can use only modules that where built with them (I have no idea why is it, but the answer where much interessting for me))
You have to install from hand: scp first then opkg install full-path-file-name
Or theoreticly modifi the /etc/opkg/customfeeds.conf add
src/gz any_name file://usb-path/to-packages"
And copy the files to the place where should be (it does make only sense on USB)