<hejux>
xdarklight: thanks, the thing is, the patch is issue on : arch/arm64/boot/dts/amlogic/meson-axg.dtsi and arch/arm64/boot/dts/amlogic/meson-gx.dtsi
<xdarklight>
ah, yes
<hejux>
i don't find these two DTBs in my running /boot/dtbs/
<xdarklight>
a .dtb always contains the sum of the .dts and all of the .dtsi files which it included
<xdarklight>
so there's no separate .dtb for the ".dtsi" ("i" stands for include), it's all part of your .dtb
<hejux>
i have this: /boot/dtbs/amlogic/meson-gxl-s905d-p230.dtb, on my running alarm.
<hejux>
but it is supposed to remove eee from this file.
<xdarklight>
do to the includes in the original .dts file your .dtb also contains the contents of arch/arm64/boot/dts/amlogic/meson-gx.dtsi
<xdarklight>
and there's a change to the IRQ in meson-gx.dtsi which you need to apply as well
<afaerber>
xdarklight, that change is only going into 4.21?
<xdarklight>
afaerber: sorry, I was replying to hejux
<hejux>
i mean, i can use dtc to make meson-gxl-s905d-p230.dts into meson-gxl-s905d-p230.dtb, no problem. but where do find the file related to amlogic/meson-axg.dtsi ?
<afaerber>
yeah, I understand, but I was facing same/similar issue earlier
<hejux>
there is no such file called meson-axg.dtsi (or DTB?) under /boot/dtbs/amlogic/ on my running arch
<afaerber>
my plan was to write an overlay so apply on top of distro .dtb
<afaerber>
*to
<xdarklight>
afaerber: ah okay, I believe it can be backported to -stable once it hits mainline
<afaerber>
hejux, you can also use dtc to convert from .dtb to .dts, apply your changes and go back to .dtb :)
<xdarklight>
hejux: the contents of all .dtsi files are also part of your .dtb file (the .dts file states: include <some name>.dtsi - the "dtc" tool then goes ahead and takes all the contents from the .dts file and all referenced .dtsi files and builds a .dtb from that)
<hejux>
i guess it is save to cp meson-gxl-s905d-p230_modified.dt as /boot/dtb.img ?
<hejux>
if so, i got to cancel the on going kernle compiling.
<hejux>
yeah, i'll try now.
<xdarklight>
yes, you probably have to save it as dtb.img (I'm not sure where the naming "dtb.img" comes from exactly, it it's simply a .dtb then it's correct to replace it)
<hejux>
make some notes first.
<hejux>
xdarklight: the kernel PKGBUILD has a line for that, copy /boot/yyy/xxx.dtb /boot/dtb.img
<hejux>
xdarklight: normally we use uEnv.ini to define dtb, but this kernel i'm using, use /boot/dtb.img instead, nothing in uEnv.ini
hejux has quit [Remote host closed the connection]
<hejux_>
xdarklight: hard to say for such a short time food ping
<hejux_>
flood *
<xdarklight>
ok
<xdarklight>
I'll get some dinner now, see you guys later
* afaerber
testing with the above overlay applied now (needed to update my U-Boot first)
<hejux_>
slightly better iperf3 performance than before. 240M to 250M now, under 300M wifi
<hejux_>
xdarklight: see you, enjoy
<hejux_>
thanks.
<hejux_>
afaerber: how to use an overlay?
<afaerber>
hejux_, I wrote a boot script for U-Boot (boot.scr) that uses the "fdt apply" command to apply my overlay on top of my unmodified distro .dtb
<hejux_>
that's cool.
<hejux_>
i have no idea about uboot, tried to take full use of the emmc of my Phicomm N1 by formating it from start to end... almost bricked the box
<hejux_>
/dev/mmcblk1p1 221184 1269760 1048577 512M e W95 FAT16 (LBA)
<afaerber>
ouch, yeah Amlogic is a bit tricky - was hoping to continue work on my meson-tools for S905X/S912 during the holidays...
<hejux_>
/dev/mmcblk1p2 1400832 15269887 13869056 6.6G 83 Linux
<hejux_>
i still don't understand why i have to format the mmc like this
<hejux_>
there's free space that i can't use or i won't boot mmc or usb drive
<afaerber>
part of the bootloader may sit around sector 97
<afaerber>
(at least on Odroid-C2)
<hejux_>
Odroid is much easier to deal with i guess, Phicomm N1 was a TV Set top box orig.
<afaerber>
hmm, deleting the eee-broken-1000t property is not working the way I hoped
<hejux_>
afaerber: along with the IRQ fix?
hejux has joined #linux-amlogic
<afaerber>
hejux_, the interrupts override seems working okay - problem is that /delete-property/ doesn't seem to work for overlays and I find no alternative documented and see it as a to-do in https://elinux.org/Frank%27s_Evolving_Overlay_Thoughts
<hejux>
isee, overlay did not overlay :)
<afaerber>
well, 50% :)
<afaerber>
should be an improvement over current state already
<hejux>
what about sed
<hejux>
:) with your script,
<afaerber>
hmm, not a bad idea, let me try "fdt rm"...
<hejux>
good luck
<afaerber>
hejux, btw what I did on TV boxes of mine was to chain-load a newer U-Boot from the vendor U-Boot
<hejux>
but still, not able to use all mmc space
<hejux>
usually, for x86, there is 2M Bytes free space at the head, all the rest can be used by OS
<hejux>
however, i'm already happy with that i can use bootstrap method to install alarm to mmc, that's easier than i thought
<afaerber>
worked!
<hejux>
figured out!
<hejux>
cool
hejux has quit [Quit: leaving]
<afaerber>
hejux_, here the first partition starts on sector 2048, i.e. 1048576
<hejux_>
and?
<hejux_>
finally i got that dts is like dsl to ACPI, while dtb is like aml.
<hejux_>
intel got iasl, arm got dtc :)
<hejux_>
that's easier for me to understand
<hejux_>
:3
The_CooIest has quit [Ping timeout: 246 seconds]
The_Coolest has joined #linux-amlogic
The_Coolest has quit [Client Quit]
The_CooIest has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
phh has quit [Remote host closed the connection]
phh has joined #linux-amlogic
hejux_ has quit [Remote host closed the connection]
Darkmatter66 has joined #linux-amlogic
Darkmatter66_ has quit [Ping timeout: 268 seconds]
sputnik_ has quit [Remote host closed the connection]