02:02 <Armbian-Discord> <s​amduploader> is there a11 rom avilable for tanix tx3 mini

06:53 <Armbian-Discord> <W​erner> Barely anybody here is dealing with tvboxes. Better ask in forums but do not expect much.

06:55 <Armbian-Discord> <W​erner> Interesting. That bug seems to spread across SoCs ^^. First I discovered that was years ago with H6 SoC and vendor images lol. Have you tried edge kernel too?

07:58 <frog> Hi everyone,

07:58 <frog> I noticed support for cubox i was dropped. I am well aware of the high burden on armbian maintainers. I was wondering what the reason for this was: just a lack of time or was there some hardware support issues which surfaced? From what I know, i.mx6 is very well supported in mainline, and I would have thought keeping the cubox i supported in armbian would be relatively low effort. I have a spare cubox i I co

07:58 <frog> uld use for building and testing armbian images. I would be happy to contribute to keep this board supported by armbian.

07:59 <Armbian-Discord> <W​erner> supported status depends on active maintainer for hardware: https://docs.armbian.com/User-Guide_Board-Support-Rules/

07:59 <ArmbianHelper> ^ Board Support Rules - Armbian Documentation

08:09 <Armbian-Discord> <I​gorPec> one cubox is still held in automated testing facility, community auto builds will remain enabled, but for more then this ... answering a single question regarding this hardware, its not possible. That little time we have.

08:13 <obinou> I also have a cubox i4 that I uses for trainings and test on embedded stuff. Armbian is really a plus here as a reference. I don't know if I can help

08:13 <obinou> I also need time to work on my new bananapi-r3 :-)

08:16 <Armbian-Discord> <I​gorPec> we will keep providing 32bit arm builds, but outside main focus. If it will stop working due to upstream changes, we can't really do much and hw won't get new kernels. That's worse thing that can happen here

08:17 <Armbian-Discord> <I​gorPec> we need help as a project in various areas - from tweaking servers to drawing some documents

08:18 <Armbian-Discord> <I​gorPec> banana r3 is not in the program, but if you can bring it up to armbian, why not

10:11 <frog> IgorPec - I understand that if upstream causes breakage for a particular board, it requires a lot more work to get things working again. What I'm asking is if a maintainer commited to the cubox i, would that be enough to move it into WIP support status?

10:40 <wifasoi[m]> Hi, I'm still trying to make the rk3566 boot. I maybe found the coulprit. I don't put the blobs in the right folder.. maybe. So where should I put the blob (here the code that set the variables: https://github.com/armbian/build/blob/armbian-next/config/sources/families/include/rockchip64_common.inc#L79-L83)

10:40 <ArmbianHelper> ^ build/rockchip64_common.inc at armbian-next · armbian/build · GitHub

10:41 <wifasoi[m]> there is a variable somewhere that permits to dowload it.. or just a very sneaky blob folder somewhere else?

10:49 <wifasoi[m]> The very question is if the folder are relative to the uboot sources? If so what is the best way to add the blobs from a remote location?

11:12 <wifasoi[m]> aha! foud the source!

11:12 <wifasoi[m]> https://github.com/armbian/rkbin/tree/master/rk35

11:12 <ArmbianHelper> ^ rkbin/rk35 at master · armbian/rkbin · GitHub

11:47 <Armbian-Discord> <I​gorPec> frog check this https://docs.armbian.com/Board_Maintainers_Procedures_and_Guidelines/

11:47 <ArmbianHelper> ^ Board Maintainers Procedures and Guidelines - Armbian Documentation

11:49 <frog> Thanks IgorPec. Think I'll try and build a cubox image with the latest armbian build system and see how it works

14:25 <Armbian-Discord> <T​heBug> @everyone Reminder: https://discord.com/events/854735915313659944/1025403962662342657

14:25 <ArmbianHelper> ^ Discord

14:28 <Armbian-Discord> <T​heBug> @Tenkawa @c0rnelius @MicroLinux (Salva) @monkaBlyat @NicoD @teslacreiste @ManoftheSea @Tonymac32 @lanefu @mdburmeister @meteyou @rpardini - https://discord.com/events/854735915313659944/1025403962662342657 - Hope to see you guys there!

14:28 <ArmbianHelper> ^ Discord

14:31 <Armbian-Discord> <N​icoD> I'll try to attend. But I might be drunk by then.

14:32 <Armbian-Discord> <T​heBug> Well, are you better or worse at english when your drunk? don't know? lets find out 😄

14:33 <Armbian-Discord> <T​heBug> you're*

14:33 <Armbian-Discord> <T​heBug> I'm not even drunk and I am already making mistakes 😄

14:47 <Armbian-Discord> <N​icoD> Lol. I don't think it helps for me 🙂

14:50 <Armbian-Discord> <W​erner> As stated. BYOB 😄

14:54 <Armbian-Discord> <p​rofbbrown> I've only tried the stock kernel. Someone else thinks it may be a problem with the device tree, that the FUSB I2C pin may be wrong. But I've checked with the schematic and it seems OK.

14:55 <Armbian-Discord> <W​erner> Well I am neither a developer nor very deep into that kind of stuff so the only thing I can do is observe 🙂

14:56 <Armbian-Discord> <M​icroLinux (Salva)> niceee! I will try to be drunk too

14:56 <Armbian-Discord> <W​erner> (and complain 🤪 )

15:10 <Armbian-Discord> <T​onymac32> that's my job

15:15 <Armbian-Discord> <W​erner> being drunk or complaining?

15:21 <stipa> drunkcomp

15:22 <stipa> sounds like something cyberpunkish

15:28 <[TheBug]> Drunkplaining

15:51 <stipa> the team leader has to be the drunkest

16:12 <IgorPec> Ballmer Peak meeting then ?:)

16:22 <stipa> right

16:23 <stipa> some of the best use it

16:24 <stipa> like Steve Palmer

16:24 <stipa> Ballmer*

16:25 <stipa> can't go wrong with that one

20:01 <Armbian-Discord> <T​onymac32> Yes.

20:12 <Armbian-Discord> <T​onymac32> it's what I do, I drink and I know things

22:26 <Armbian-Discord> <M​icroLinux (Salva)> No one resist a drunk salvador 😂😂😅

22:27 <Armbian-Discord> <N​icoD> Thank you for giving something to watch, but I've gotten pain in my neck from it.

22:27 <Armbian-Discord> <M​icroLinux (Salva)> Hahahah okaa

22:27 <Armbian-Discord> <M​icroLinux (Salva)> Have a nice weekends guys

22:28 <Armbian-Discord> <M​icroLinux (Salva)> Linux is for everyone, whoever say something different: Blocked()

22:29 <Armbian-Discord> <N​icoD> I'm watching hackers...

22:29 <Armbian-Discord> <M​icroLinux (Salva)> If people use chromebooks/apple: Blocked()

22:30 <Armbian-Discord> <M​icroLinux (Salva)> Such a nice meeting, see you next week guys