narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
jacobk has quit [Ping timeout: 268 seconds]
jacobk has joined #linux-amlogic
kenny has joined #linux-amlogic
Kwiboo- has joined #linux-amlogic
rawoul has joined #linux-amlogic
gis- has joined #linux-amlogic
montjoie has quit [Ping timeout: 260 seconds]
montjoie has joined #linux-amlogic
cottsay08 has joined #linux-amlogic
Kwiboo has quit [Ping timeout: 264 seconds]
cottsay has quit [Ping timeout: 264 seconds]
gis has quit [Ping timeout: 264 seconds]
rawouF has quit [Ping timeout: 264 seconds]
jacobk has quit [Ping timeout: 240 seconds]
f_ has quit [Read error: Connection reset by peer]
f_ has joined #linux-amlogic
luka177 has quit [Ping timeout: 252 seconds]
naoki has quit [Quit: naoki]
naoki has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
rawoul has quit [Ping timeout: 255 seconds]
rawoul has joined #linux-amlogic
ldevulder has quit [Ping timeout: 255 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
hexdump0815 has quit [Ping timeout: 255 seconds]
hexdump0815 has joined #linux-amlogic
luka177 has joined #linux-amlogic
<montjoie> xdarklight: how do find issue with the vendor ? last time I tried it has none (perhaps due to not enough testing)
jacobk has joined #linux-amlogic
anessen9733 has quit [Ping timeout: 240 seconds]
adeepv has joined #linux-amlogic
anessen9733 has joined #linux-amlogic
glaroque has joined #linux-amlogic
neoninteger has quit [Remote host closed the connection]
kenny has quit [Ping timeout: 272 seconds]
neoninteger has joined #linux-amlogic
ldevulder_ is now known as ldevulder
anessen9733 has quit [Ping timeout: 255 seconds]
kenny has joined #linux-amlogic
marc|gonzalez has joined #linux-amlogic
<marc|gonzalez> narmstrong: you wrote "This change doesn't apply on top of either v6.8-rc1 or linux-next"
<marc|gonzalez> You inserted that remark in the middle of the changelist
<marc|gonzalez> Are you referring to a particular patch then?
<marc|gonzalez> For the record:
<narmstrong> marc|gonzalez: yep the vendor prefix is the first one which doesn't apply, haven't checked the other ones
<marc|gonzalez> 451d85a4779a8 arm64: dts: amlogic: add fbx8am DT overlays
<marc|gonzalez> 899a43f6728ad arm64: dts: amlogic: add fbx8am board
<marc|gonzalez> 66319b98bd9b4 dt-bindings: vendor-prefixes: add freebox
<marc|gonzalez> fad10c5a97886 dt-bindings: arm: amlogic: add fbx8am binding
<marc|gonzalez> 6613476e225e0 (tag: v6.8-rc1) Linux 6.8-rc1
<marc|gonzalez> Maybe I messed something up in the email, but it's straight up 6.8-rc1
<narmstrong> ok weird
<marc|gonzalez> I'll test right now
<marc|gonzalez> Must be some formatting issue
<marc|gonzalez> Do the boards need to be in lexicographic order in the amlogic yaml?
<narmstrong> $ git describe
<narmstrong> v6.8-rc1
<narmstrong> ...
<narmstrong> Applying: dt-bindings: vendor-prefixes: add freebox
<narmstrong> Patch failed at 0001 dt-bindings: vendor-prefixes: add freebox
<narmstrong> ...
<narmstrong> error: patch failed: Documentation/devicetree/bindings/vendor-prefixes.yaml:500
<narmstrong> error: Documentation/devicetree/bindings/vendor-prefixes.yaml: patch does not apply
<narmstrong> I don't care, but it seems nowadays the DT bindings maintainers seems to care...
<narmstrong> so yes
<marc|gonzalez> These evolving standards are maddening
<marc|gonzalez> Like the DT is a straight up copy/paste of 5 other trees, WTF would K get on my case for that
<marc|gonzalez> It's a double standard
<narmstrong> yes, it became harder, but at least we can validate the DT now, which is a great feature
<narmstrong> I have a script that does a ton of check on a full patchset, which wasn't possible a few years ago
<marc|gonzalez> narmstrong: I suspect K is hinting at the schema errors from dtbs_check
<marc|gonzalez> I'm not Jesus Christ, I can't turn water to wine, and fix schema warnings
<narmstrong> marc|gonzalez: yep probably, he's very picky of those _ in node names
<marc|gonzalez> No I meant another comment of his
<marc|gonzalez> Anyway, I'll reply in email
<narmstrong> yeah his english style is quite harsh, I prefer Conor's comments which are pretty constructive and positive
<narmstrong> marc|gonzalez: I know it's mainly copy paste so no big deal, cleaning dt is part of the slowly ongoing process, just make sure the bindings works when running dt_binding_check, and DTBS_CHECK on meson-g12a-fbx8am.dts doesn't spit more errors than the sei510 DT and it's good to go
<marc|gonzalez> narmstrong: yup, I can reproduce the bad patch issue, sorry my bad (misconfigured MUA)
adeepv has quit [Quit: adeepv]
jacobk has quit [Ping timeout: 260 seconds]
<narmstrong> so I've installed JELOS on the Odroid Go Ultra (using the A311d) which is using Linux v6.7 and my DSI patchset + some optimizations dones by HardKernel, and I must say it's quite impressive!
<narmstrong> I've been playing to PSP, PS2, Gamecube games and they are all emulated super smoothly, all this using Panfrost and Wayland!
<mkorpershoek> super awesome !
chewitt has joined #linux-amlogic
<chewitt> phh: the Odroid N2 u-boot has prior art for using saradc values to select the device tree
<narmstrong> indeed I forgot about that
anessen9733 has joined #linux-amlogic
<f_[xmpp]> narmstrong Nice!!
<phh> chewitt: thanks. As I said before, I don't really plan on fixing the bootloader just yet, but good to know anyway
jacobk has joined #linux-amlogic
<f_[xmpp]> better upstream good code than fixing hacky code :)
<f_> *fix
<f_> IMO
<phh> hum so dynamic configfs device tree overlay has never been merged?
<narmstrong> Yeah honestly it’s not a good idea, all drivers should be reworked to handle runtime property change for example
<marc|gonzalez> narmstrong: do you know how to tell 'make dt_binding_check' to check a single file?
<narmstrong> marc|gonzalez: dts or yaml file ?
<marc|gonzalez> It's been running for an hour on a decent workstation (16 threads, 48 GB RAM)
<marc|gonzalez> YAML file
<narmstrong> make dt_binding_check DT_SCHEMA_FILES=filename.yaml
<marc|gonzalez> thanks, you're a life saver
<narmstrong> you're welcome
<marc|gonzalez> why is KK busting my balls when it doesn't make a warning? ooooh, he's probably running into the same issue as you!
<marc|gonzalez> i.e. my patches were mangled by the stupid MUA that had been working for years
<marc|gonzalez> narmstrong: in arm/amlogic.yaml, you want the boards in alphabetical order?
<narmstrong> marc|gonzalez: yeah it will make conor happy
<marc|gonzalez> "If it makes you happy, it can't be that baaaaaaaad. If it makes you happy, then why the hell are you so sad?" :)
psydroid has joined #linux-amlogic
<f_[xmpp]> marc|gonzalez: have fun lol
anessen9733 has quit [Ping timeout: 255 seconds]
naoki has quit [Quit: naoki]
<marc|gonzalez> f_[xmpp]: writing DT patches? Are you crazy? :)
<f_> yes
<f_> I'm crazy, probably.
<marc|gonzalez> Everyone is crazy to someone somewhere :)
<f_> :)
<marc|gonzalez> When I was a teen, I read a book called "The fascinating number Pi". Friends thought it was weird to be reading that :)
<narmstrong> I've read and loved `The Apollo Guidance Computer: Architecture and Operation`, Am I weird ?
<f_> I'm reverse engineering BL2 on yeee old SoCs, am I weird?
<narmstrong> probably, but it's ok :-D
buzzmarshall has joined #linux-amlogic
<f_> lol
ungeskriptet has quit [Ping timeout: 252 seconds]
anessen9733 has joined #linux-amlogic
ungeskriptet has joined #linux-amlogic
luka177 has quit [Ping timeout: 252 seconds]
anessen9733 has quit [Ping timeout: 255 seconds]
<marc|gonzalez> narmstrong: I've figured out where I messed up. I posted the patch series from an old work laptop that wasn't correctly set up
<marc|gonzalez> I'll spin a v3, and fix the nits for KK along the way
<narmstrong> good!
anessen9733 has joined #linux-amlogic
<marc|gonzalez> narmstrong: I'm confused (what's new?). If I merge the overlays in the kernel build, then it will build 3 DT blobs for everyone who has ARCH_MESON ?
<marc|gonzalez> As opposed to only 2 when I didn't use overlays... So not even space savings, but instead space gobbling?
<narmstrong> marc|gonzalez: yeah the overlay support in kernel is not very clear, I don't mind building dtbos for platforms that needs those, but I thought is was ok since other platforms do it
<phh> and so to clarify completely, when we'll add two additional dtso for DVB support, let's call them -avl6762 and -cxd2856. we'll also add the merge of {base + avl6762} and {base + cxd2856} to the build, right?
<f_> That is, if/when DVB support lands in mainline?
<phh> f_: yeah
<f_> Do you have plans for that to happen or..?
<phh> not really, but hopefully I'll the the courage one day. honestly demod/tuner frightens me most
<f_> rn my S905 box has 2 huge holes currently used for uart cables lol
jacobk has quit [Ping timeout: 268 seconds]
jacobk has joined #linux-amlogic
luka177 has joined #linux-amlogic
marc|gonzalez has quit [Quit: Leaving.]
jacobk has quit [Ping timeout: 268 seconds]
vagrantc has joined #linux-amlogic
ldevulder has quit [Ping timeout: 268 seconds]
ldevulder has joined #linux-amlogic
jacobk has joined #linux-amlogic
djrscally has joined #linux-amlogic
jacobk has quit [Ping timeout: 240 seconds]
psydroid has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
djrscally has quit [Quit: Konversation terminated!]
f_[xmpp] has quit [Ping timeout: 264 seconds]
exkc has quit [Ping timeout: 264 seconds]