02:25 <MasterR3C0RD> Aha! The R_TWI pin cfg is 0x2 on A133, not 0x3 like the H616

02:31 <MasterR3C0RD> Also, iscle, apritzel: I did a little more looking around at the Sonic Pad sources, and it appears that the .a files in https://github.com/CrealityTech/sonic_pad_os/tree/main/lichee/brandy-2.0/spl/board/r818 are the ones that match the "DRAM BOOT DRIVE" version of V0.69 in my board's logs; more specifically `sun50iw10p1_sdcard.a` (which is also a `.o` with wrong extension)

02:35 <MasterR3C0RD> Since even with the PMIC up and running, my DRAM init code isn't worked, going to restart my porting work but using that as a base

02:36 <MasterR3C0RD> s/worked/working/

10:56 <dsimic> aperezdc: when it comes to reverse engineering the DRAM init code from binary blobs, are there some associated LICENSE files that prohibit reverse engineering?

10:57 <dsimic> oops, sorry, I wanted to ping apritzel, but they're offline at the moment

10:57 <dsimic> I'll get back later

13:04 <aperezdc> dsimic: no worries, I figured you were trying to ask someone else ;-)

13:09 <dsimic> thanks :)

13:33 <wens> just leave a message, he reads the logs mostly

13:37 <dsimic> ah, alright

13:39 <dsimic> so, basically, I'd like to know what happens with any possible licensing terms associated with the DRAM init blobs, which may explicitly forbit reverse engineering, and the reverse engineering of the same blobs that has already taken place?

13:40 <dsimic> s/forbit/forbid/

13:44 <jakllsch> supposedly there are some jurisdictions where such clauses are unenforcable

13:44 <jakllsch> (but there are some where they are too)

13:51 <dsimic> does it depend on the country one lives in?

13:51 <jakllsch> yes

13:52 <dsimic> sounds good :)

13:52 <dsimic> is there someone who could check it further?

13:52 <jakllsch> that's about all I know

13:53 <jakllsch> i imagine someone has written about it online

13:53 <dsimic> I'm afraid it always requires some lawyer to be involved, becase the regulations change all the time

13:54 <dsimic> i.e. someone's experince from a while ago may no longer apply

13:54 <dsimic> s/experince/experience/

13:57 <jakllsch> yeah

16:54 <MasterR3C0RD> dsimic: I'm not a lawyer, but I would presume in this case that there's a reasonable interoperability defense

17:08 <dsimic> MasterR3C0RD: huh, what do you actually mean?

17:09 <MasterR3C0RD> >so, basically, I'd like to know what happens with any possible licensing terms associated with the DRAM init blobs, which may explicitly forbit reverse engineering, and the reverse engineering of the same blobs that has already taken place?

17:12 <MasterR3C0RD> The DRAM init code that's been reverse engineered might be covered under interoperability exclusions that are in place for multiple jurisdictions; for example the US

17:14 <dsimic> ah, I wasn't aware of that

17:14 <dsimic> sounds great to me!

17:15 <dsimic> does that stand even if the associated blob license says "reverse engineering prohibited"?

17:17 <MasterR3C0RD> That's where it gets fuzzy; again not a lawyer

17:19 <MasterR3C0RD> Main idea though is that you can only reverse engineer as much as is necessary for interoperability purposes. If you straight up copy the source code for the entire SPL, for example, it's probably less legally palatable

17:23 <MasterR3C0RD> In my case though, it's in a repository that only contains the GPL2.0 license, and there may be some code being used from U-Boot in the SPL that contains the DRAM init code, which might bring up some additional licensing questions.

17:47 <dsimic> MasterR3C0RD: hmm, it's all rather convoluted

17:48 <dsimic> e.g. what if U-Boot already contains DRAM init code that goes up to DDR-800, and I want to reverse-eigineer a DRAM init blob to create additional source code in U-Boot and have DDR-1066 supported as well?

17:48 <dsimic> s/reverse-eigineer/reverse-engineer/

22:02 <apritzel> dsimic: first: I wouldn't worry about any licensing issue, from my experience they (AW?) don't care at all, and also they have quite some skeletons in the closet (GPL violations in their kernel code)

22:04 <apritzel> dsimic: and also: this whole repo has a GPL LICENSE file in the root directory, so if nothing else one could ask them (CrealityTech) to send us the source code for the blobs in there

22:06 <apritzel> also, MasterR3C0RD mentioned: there are rules about reverse engineering, which allow us to do this

22:09 <apritzel> copying from source code with an incompatible license is of course a no-go, but I don't see any EULA before accessing this repository, so I don't think they can impose any restrictions on reverse engineering

23:51 <apritzel> macromorgan: I pushed your U-Boot Anbernic series to sunxi/master: can you please verify that this still works for now? I dropped one DRAM patch (TPR6 change)

23:51 <apritzel> https://source.denx.de/u-boot/custodians/u-boot-sunxi/-/commits/master