Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
<Armbian-Discord>
<PhotoJim> hmm, can't seem to get anywhere with those methods
<Armbian-Discord>
<PhotoJim> I think what I'll do is install a new system onto an SD card, then boot from that and chroot into the eMMC to see if I can fix it right from the NanoPi
<Armbian-Discord>
<PhotoJim> but not tonight
alekksander has quit [Quit: Konversation terminated!]
<Armbian-Discord>
<Jason123> I am going to test the orange pi zero without a heatsink to see if it works because at some point I need to work it out with the seller to get one for the cpu
norwich has quit [Ping timeout: 268 seconds]
norwich has joined #armbian
<Armbian-Discord>
<NicoD> Take a picture of it. I'm curious about what you were talking about.
<Armbian-Discord>
<Jason123> I did not put the heatsink on the cpu yet its just there for size
<Armbian-Discord>
<c0rnelius> i wouldn't worry about it unless it starts running at 70*C or something.
<Armbian-Discord>
<Jason123> it runs at 2.8c
<Armbian-Discord>
<Jason123> about
<Armbian-Discord>
<Jason123> at idle
<Armbian-Discord>
<c0rnelius> it will heat up more when you start using the eth and usb port. But its not a big deal till it is... You'll know when it is.
<Armbian-Discord>
<Jason123> i do use the ethernet
<Armbian-Discord>
<Jason123> its not a big deal even with the case and the expansion board on?
<Armbian-Discord>
<c0rnelius> well you need to test it and find out 🙂 You should be able to pick those little drop on heat sinks online. You can buy a little box of them in diff sizes for not much at all.
<Armbian-Discord>
<Jason123> if I were to get a heatsink how big would it need to be?
<Armbian-Discord>
<Jason123> for the h3
<Armbian-Discord>
<c0rnelius> one that just fits where you have the current one in that pic should be fine.
<Armbian-Discord>
<Jason123> what would the size be for the h3 heatsink?
<Armbian-Discord>
<Jason123> oh i asked the question
<Armbian-Discord>
<Jason123> but how would i know what the size needs to be
<Armbian-Discord>
<c0rnelius> i think the last one I used was a 15x15x6.5mm but an 11x11 would also work fine. the 15x15 is a bit large on it.
<Armbian-Discord>
<c0rnelius> like completely covers it and the edge goes over.
<Armbian-Discord>
<Jason123> i think 14 by 14 is the size and I know someone that could give me one
<Armbian-Discord>
<Jason123> really I just need to test the board if i need a heatsink and I will be fine
<Armbian-Discord>
<Jason123> is the reported temps correct it looks lower then I would think my raspberry pi runs higher
<Armbian-Discord>
<Tenkawa> Those measurements aren't right... the cpu isn't running as low as those other #'s
<Armbian-Discord>
<Tenkawa> both directions of #'s are wrong
<Armbian-Discord>
<Tenkawa> how are you getting those numbers
<Armbian-Discord>
<Jason123> armbian monitor
<Armbian-Discord>
<Tenkawa> it possible could if you were idling with a fan on a very low frequency but if you were doing anything on there at the time I would expect those numbers to be at least 4C
<Armbian-Discord>
<Jason123> I was not doing anything at that time
<Armbian-Discord>
<Jason123> but now I rebooted and it says 3-4c
<Armbian-Discord>
<Tenkawa> Yeah thats more what I would expect
<Armbian-Discord>
<Jason123> my raspberry pi zero 2 is at 36c
<Armbian-Discord>
<Tenkawa> yeah the zero's always run hot
<Armbian-Discord>
<Jason123> with the flirc case
<Armbian-Discord>
<c0rnelius> not much
<Armbian-Discord>
<c0rnelius> i ssuspect those number are wrong
<Armbian-Discord>
<Tenkawa> I agree
<Armbian-Discord>
<Tenkawa> They do still seem a bit low
<Armbian-Discord>
<Jason123> how do I know for sure if the numbers are correct?
<Armbian-Discord>
<c0rnelius> i use mine for audio or web stuff.
<Armbian-Discord>
<c0rnelius> kinda useless beyond that really
<Armbian-Discord>
<Jason123> to put it into the case with the expansion board with ethernet and use it as some headless linux
<Armbian-Discord>
<c0rnelius> should be good then
<Armbian-Discord>
<c0rnelius> most of my headless bits I have laying around doing something are allwinner boards. h3, h5, a20. some run warmer than others but they all run.
<Armbian-Discord>
<Jason123> should be good to run before I get the heatsink?
<Armbian-Discord>
<c0rnelius> yeah I would think so.
<Armbian-Discord>
<Jason123> ok thanks i just don't know I always run with heatsink
<Armbian-Discord>
<Jason123> because I am thinking to not dispute over missing screws and heatsink if i can get them
<Armbian-Discord>
<Jason123> well my raspberry pi zero i don't have a heatsink
<Armbian-Discord>
<c0rnelius> you'll know something is wrong if the board goes off line.
<Armbian-Discord>
<Jason123> the lts boards do claim to fix heating issues so it should not be an issue
<Armbian-Discord>
<c0rnelius> i use my zeros as cams. i have little tiny sinks on them.
<Armbian-Discord>
<Jason123> it was $38 for the whole kit with psu + case + board + expansion board + heatsink
<Armbian-Discord>
<c0rnelius> i don't know if they help really... but I feel better about it 🙂
<Armbian-Discord>
<Jason123> not bad seal
<Armbian-Discord>
<c0rnelius> for the OPI?
<Armbian-Discord>
<Jason123> yes for the orange pi one
<Armbian-Discord>
<c0rnelius> yeah thats pretty good
<Armbian-Discord>
<Jason123> cheapest option out of all the other boards I found
alekksander has joined #armbian
<Armbian-Discord>
<Jason123> the orange pi zero 2 might have been a similar price but it was bigger and not as good software wise
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #armbian
lemonzest has joined #armbian
alekksander has quit [Quit: Konversation terminated!]
<ArmbianHelper>
Meeting started Sat Jan 7 15:04:14 2023 UTC. The chair is Werner. Information about MeetBot at http://wiki.debian.org/MeetBot.
ArmbianHelper changed the topic of #armbian to: (Meeting topic: developer meeting)
<IgorPec>
#topic check-in
<Werner>
#topic check-in
ArmbianHelper changed the topic of #armbian to: check-in (Meeting topic: developer meeting)
<Heisath>
Heisath, for mvebu (clearfog & helios) here.
<IgorPec>
i'll cover some of allwinner, some build system, infra
<IgorPec>
anybody around @jock said he will come, @brentr its 7 am (perhaps)
<Heisath>
jock wrote hello only 14 minutes back, so he should be here
<jock>
yes I'm here
<IgorPec>
cool, so we have some rockchip coverage
<jock>
yup
<IgorPec>
while we are waiting - any late topics?
lpirl has joined #armbian
<jock>
@igor none from my side
<IgorPec>
k
<Heisath>
I don't think we need to wait any longer.
<IgorPec>
ok
<Heisath>
Lets go on with #topic FYI. Anything from armbian management side you want to address, Igor?
<Werner>
#topic FYI
ArmbianHelper changed the topic of #armbian to: FYI (Meeting topic: developer meeting)
<IgorPec>
from management? only that we are working hard on bringing
<IgorPec>
this partnership program up
<IgorPec>
to stabilise funding. progressing, slowly
<IgorPec>
don't have much prepared in this regard
<Heisath>
k. I have question for the Armbian Private Subscriber Forum, is that the same as the "Contributors/Maintainers lounge"?
<IgorPec>
no, that is designed for partners
<IgorPec>
that is answered with certainty
<Heisath>
So not even read only to the general public?
<Werner>
hidden (for now)
<IgorPec>
it is still under development and until we don't define our side, its limited
<Heisath>
Ok just wondering because the post by Bug made it sound like it is done.
<IgorPec>
its a place where a partner can post the problem
<[TheBug]>
Heisath: the answer I think you are looking for..
<IgorPec>
it is done, but internally we haven't define this yet
<IgorPec>
so far there are two partners that have asked something
<IgorPec>
and we are working on it
<Heisath>
Ah and we is?
<[TheBug]>
Anyone who has been a long term contributor to Armbian and wants to participate and be able to answer questions in the pay forum, if you have been here for at least a year then we will put you into a Community Supporter state so you can have access. To post an issue you would still need to pay, but you would be able to paricipate without payment.
<[TheBug]>
If you are in this position please contact me directly and I will work out getting the forum changes made and it documented internally
<Heisath>
Ok then lets continue with board status, I guess.
<IgorPec>
yes, this is more on the business side of the armbian
<Heisath>
#topic development Allwinner
<Werner>
#topic development Allwinner
ArmbianHelper changed the topic of #armbian to: development Allwinner (Meeting topic: developer meeting)
<[TheBug]>
Heisath: thanks for bringing that up, I will add this note soon to the forum post on it to make it more clean for Contributor / Maintainers that give their time to Armbian -- that is still a donation
<IgorPec>
recent troubles with allwinner
<[TheBug]>
s/clean/clear
<ArmbianHelper>
[TheBug] meant to say: Heisath: thanks for bringing that up, I will add this note soon to the forum post on it to make it more clear for Contributor / Maintainers that give their time to Armbian -- that is still a donation
<IgorPec>
are related to boot loader
<IgorPec>
some boards got troubles with 2022.07
<IgorPec>
the same as rockchip
<IgorPec>
then we have H616 mainline in rough state
<IgorPec>
wireless support on Oranges is broken in 6.x
<IgorPec>
with this new chip
<IgorPec>
the rest is outside of my knowing. we should start cleaning patches
<IgorPec>
Allwinner is the dirtiees
<Heisath>
#info Allwinner has boot loader troubles
<IgorPec>
and i did u-boot cleaning few months back. at least that part is good. for upcoming release i don't think we will bump allwinner to 6.1 with CURRENT
<IgorPec>
that's it
<Heisath>
#action clean Allwinner patches
<Heisath>
#topic development Amlogic
<Werner>
#topic development Amlogic
ArmbianHelper changed the topic of #armbian to: development Amlogic (Meeting topic: developer meeting)
<Heisath>
Anyone here for amlogic?
<IgorPec>
i know there are troubles with eMMC driver, some timings or ... boot loader
<IgorPec>
otherwise is in pretty decent state AFAIK
<IgorPec>
not many patches on top of mainline
<Heisath>
great.
<Heisath>
#topic development Marvell
<Werner>
#topic development Marvell
ArmbianHelper changed the topic of #armbian to: development Marvell (Meeting topic: developer meeting)
<Heisath>
nothing new here. mvebu edge is on 6.1 now, I guess we will test that and then go to 6.1 current with the 23.05. release. Maybe retire then. Not much happening on mvebu. All the same patches not a lot but constantly breaking.
rpardini has joined #armbian
<IgorPec>
i would propose to widen question of device retirement at the end
<IgorPec>
its not just this device
<Heisath>
It might make sense to attach mvebu edge to Russel Kings Clearfog Kernel tree, which gets updates often and he adjust patches. Maybe just have it auto build then via the new community release thing.
<IgorPec>
i mean mvebu gets very low interest on forums
<Heisath>
mvebu64 (so Ebin) is clean mainline right now, so that can stay for long probably.
<IgorPec>
its now an old device, perhaps moving whole section down
<Heisath>
Or it runs great :D
<IgorPec>
i understand it works well, but if there is no support needs
<Heisath>
Maybe not many noobs try it and get lots of small problems with irrelevant stuff like graphics and desktop.
<IgorPec>
dedicated forum existance is not needed
<Heisath>
true.
<Heisath>
Also only 32bit
<IgorPec>
and if we retire device, it has to be different at saying "its not supported"
<Heisath>
anyway. If @manofthesea has no ebin points we can continue.
<IgorPec>
ok
<Heisath>
#topic development Rockchip
<Werner>
#topic development Rockchip
ArmbianHelper changed the topic of #armbian to: development Rockchip (Meeting topic: developer meeting)
<IgorPec>
here we have a patch mess (rockchip64)đ
<IgorPec>
@jock can tell more
<jock>
yes, first of all rk322x and rockchip 32 bit are quite ok with kernel 6.1
<jock>
I tested them a bit and IMHO current can go 6.1
<lpirl>
I recently had a rk3399 (NanoPi M4v2) that got stuck in uboot, but I'll test again soon with a freshly built image.
<IgorPec>
rockchip boards also broke with uboot 2022.07
<IgorPec>
some of them
<Heisath>
Remind me, why do we keep updating uboot?
<jock>
about rockchip64, the tests I did with a 3318/3328 device, it seems to work well enough. There were some issues with broadcom bluetooth that have been fixed removing a Pinebook patch
<Heisath>
Is there ever new features?
<rpardini>
-- damn -- so sorry -- had bike trouble and was stranded nowhere in the rain.
<IgorPec>
EFI support is something that might be interesting
<IgorPec>
rpardini np. i covered you on amlogic "there are no troubles" :)
<jock>
u-boot v2022.07 has been a wreck with 32bit rockchips
<IgorPec>
jock: are those BC issues fixed by now?
<IgorPec>
and what we can do to go down with patch entrophy
<IgorPec>
u-boot / rockchip64 / media
<jock>
yes about the patch mayhem of rockchip64, there was no consesus about converting the patches into series
<lpirl>
I unfortunately haven't understood the implications of the uboot 2022.07 breakage yet. Are the causes known? How can board maintainers help with that?
<IgorPec>
board maintainer can help by reporting it. I can only see it on test devices.
<jock>
@igor, IMHO the armbian patches could at least move to series, so they at least apply over kernel sources and don't substitute them like now
<lpirl>
Thanks Igor, I'll have a go with fresh images soon.
<IgorPec>
lpirl:
<[TheBug]>
https://www.armbian.com/rc-testing/ can be used anytime for reporting issues by a maintainer. We have to reset the ticket for this cycle, but that should be done here later today.
<jock>
@lpirl I spent quite some time months ago for u-boot v2022.07 on 32 bit rockchips, but could get it sorted out; on 64 bit rockchips it seems to work decently although
<IgorPec>
i have move some of one boot loader back
<jock>
*could NOT
<IgorPec>
lpirl: open a Jira ticket in case image from download does not work / is killed by upgrade
<IgorPec>
when we will produce RC images for next re-build, that rc-testing link applies
<Heisath>
ok #topic development Others
<Werner>
#topic development Others
ArmbianHelper changed the topic of #armbian to: development Others (Meeting topic: developer meeting)
<Heisath>
Any other boards, Jetson?
<IgorPec>
that is covered by media kernel AFAIK
peterm6881 has joined #armbian
<IgorPec>
so more like Oleg theritory, i have open one bug lately
<IgorPec>
switchjing kernel from current to next killed the board
<IgorPec>
otherwise its fine
<Heisath>
Alright then lets go to #topic buildsystem
<Heisath>
I think here is most of the new stuff
ArmbianHelper changed the topic of #armbian to: build framework (Meeting topic: developer meeting)
<Werner>
#topic build framework
<IgorPec>
@rpardinig
<IgorPec>
this is now covered in weekly meetings
<peterm6881>
whats the lowest cost platform currently supported by Armbian
<IgorPec>
as Richardo has time until end of February to finally merge NEXT in
<jock>
@peterm6881 not the right moment to ask about
<Heisath>
Ok so if anyone is interested in that he needs to watch the video from wednesday.
<IgorPec>
i would encorage people to join weekly developers meetings. they are mainly focused into build framework
<rpardini>
yes, watch the videos, there's also the slides; try out the armbian-next branch and report the problems, either in forum or directly to me, I'm happy to happy
<rpardini>
do expect failures -- the whole point of next is to stop-on-errors instead of fail-silently
califax has quit [Remote host closed the connection]
<rpardini>
we've addressed already 2 dozens of bugs in the last week
califax_ has joined #armbian
<rpardini>
but everyone has different host setup, etc, so testing is the most valuable for now
<rpardini>
(and I mean testing the build system, although testing the produced images is also ok)
califax_ is now known as califax
<Heisath>
Move on?
<Heisath>
#topic infrastructure
<Werner>
#topic infrastructure
ArmbianHelper changed the topic of #armbian to: infrastructure (Meeting topic: developer meeting)
<Heisath>
any news here?
<IgorPec>
yes
<IgorPec>
we are seeking for aarch64 iron
<rpardini>
we had a few apt mirrors trouble the last few days
<IgorPec>
i am talking to fallen fosshost, but nothing new
<rpardini>
might impact testing armbian-next. if that is the case: add `SKIP_ARMBIAN_REPO=yes` to command line, and it will do work without using mirrors
<IgorPec>
i have option b and c to precoeed
<IgorPec>
we really need to improve arm buil infrastructure
<[TheBug]>
https://status.armbian.com/ - Has been updated, now tracks all Armbian maintained infrastructure (including internal Mirrors) and reports uptime
<IgorPec>
for mirrors
<lanefu>
FYI if fosshost has spare iron in the USA I can colo a box or 2 in my lanecloud Texas for you
<rpardini>
yes. native / high-core-count arm64 iron is needed -- but also smaller builders, 4-core, 8-gig, for image building would be useful
<IgorPec>
yeah, we have full blown uptime monitor now
<IgorPec>
regarding redirector @cats might tell us more
<IgorPec>
lanefu: tnx. so far i haven't got any reply from them
<IgorPec>
only that some positive note that we are qualified
<Armbian-Discord>
<cats> So the redirector is a bit stagnant currently, the code to check versions/control files is done but I believe there were some regressions with tests that caused it to not pass... I was fixing a few, but between work and other side projects it somewhat fell off.
<Armbian-Discord>
<cats> I pushed everything I had up to Github so it's there for the world to see/tinker, it should be very close
<rpardini>
yep, I've also applied for the Ampere Developer program, but so far no result from them
<Armbian-Discord>
<cats> (I hope these messages get through)
<IgorPec>
so the idea around redirector is to automatically add / remove broken mirrors
<IgorPec>
so we won't be seeing errors anymore in case that happens
<Armbian-Discord>
<cats> Yep. My ideal state of the redirector is to have multiple active nodes, backed by failover, and the ability for it to automatically say "This is outdated" - the status checks do well and monitor http/https and TLS certificates, but that version information would be icing on the cake
<rpardini>
yes -- also redirector is "sticky" -- eg in -next, I retry 5 times every update/download... but every of the 5 times it gives out the same, possibly broken, mirror
<Armbian-Discord>
<cats> It isn't actually sticky, by design it's meant to take 3 of the top mirrors available and cycle through them
<IgorPec>
ok
<IgorPec>
also there is some interest to develop "Wireless devices testing action script"
<IgorPec>
which goes into this topic
<IgorPec>
i have around 25 wifi devices that can be xporteed via tcpip to test devices, so wifi can be tested on each kernel upgrade ... automatically
<rpardini>
that could be interesting, for the usb wireless you mean? and do usbip?
<IgorPec>
"just" scripting has to be done ;)
<IgorPec>
yes
<Armbian-Discord>
<cats> But if there's an error or it's sticking unintentionally, the code is all on github and you could run it yourself to verify if you'd like - I'd also like to add specific location test cases so you could say force it to test and see which mirrors return from "this or this" :)
<rpardini>
@cats nice can you post the link to the repo, I've seen it before but lost track
<rpardini>
golang right?
<IgorPec>
i can only add that a dedicated #infra project has been opened in Jira
<IgorPec>
to cover those topics
<IgorPec>
i think its for logged users only
<Heisath>
k. Next topic would be #topic Jira backlog / open issues in github.
<IgorPec>
armbian-config :)
<Werner>
Either or. Not both :P
<Heisath>
Pff ok then armbian config first maybe?
<Werner>
#topic armbian-config
ArmbianHelper changed the topic of #armbian to: armbian-config (Meeting topic: developer meeting)
<Werner>
As ordered :)
<IgorPec>
ok
<IgorPec>
after months of going wrong way
<IgorPec>
we went right way
<Heisath>
You learned how to use GPS?
<IgorPec>
sgjava made base structure for configurator
<IgorPec>
but his main goal is to intrduce IO handling libraries
<IgorPec>
we had one person, then another tring to help
<IgorPec>
but we can't move anywhere
<IgorPec>
if someone has spare time, armbian-config also have meetings, fridays
<rpardini>
it's highly intricate: armbian-config and armbian-build share stuff like /etc/armbian-release, uboot_platform.sh; also highly dependent on the overlay structure for the kernel, if bootscript / extlinux / grub, etc.
<IgorPec>
this tool is / will also be essential for testing features
<IgorPec>
exactly. its important that the base structure is rock solid and that its implemented into CI at all stages
<Heisath>
From the assigned issues there is only about 4 left "Todo"
<IgorPec>
some could be closed. yes. Release log will be done from things in Jira
<IgorPec>
so please add at least a tittle and close it, if its not there yet
<IgorPec>
for things you want to see in the release log
<IgorPec>
many those things in backlog can also be just closed. i am closing them now
<IgorPec>
which i know
<Heisath>
#topic open issues
<Werner>
#topic open issues
ArmbianHelper changed the topic of #armbian to: open issues (Meeting topic: developer meeting)
<Heisath>
Same thing here there is too many to actually cycle them - but please check if there are matching issues for PRs which have been completed.
<Heisath>
#action adjust the release documentation. There is 10 min for cycling these issues planned :D
<Heisath>
#topic Board Support Status updates
<Werner>
#topic Board Support Status Updates
ArmbianHelper changed the topic of #armbian to: Board Support Status Updates (Meeting topic: developer meeting)
<Heisath>
I think we should introduce a new category for EOL boards.
<IgorPec>
yes
<IgorPec>
or retired
<Heisath>
Not recommended for new projects/design
<IgorPec>
what sounds better. i don't want that people dump armbian and go to somewhere else
<IgorPec>
as somewhere else they never even try to fix anything
popolon has joined #armbian
<Heisath>
So the path is WIP -> Supported -> Retired. Parallel to that there is CSC
<IgorPec>
that's why this is a bit problematic. if we say "not supported", people take this very serious
<jock>
shouldn't retired/EOL boards become community supported and be left there for community only support for the time being?
<IgorPec>
or "Matured" ?
<IgorPec>
since last release, images are now frozen by default
<IgorPec>
this means - if they boot well now, they will bot well in years from now
<lpirl>
+1 for CSC
<IgorPec>
"Matured / no active development"
<IgorPec>
i am seeking for word of assurance, something possitive
<Heisath>
Careful with that, I would not want people to then choose old "matured" devices expecting greatness and fully working stuff to then have really old HW.
<lpirl>
"done" :)
<rpardini>
Matured to me means, fully mainlined, zero-patches, working well
<IgorPec>
look again - images will reamain in frozen state
<Heisath>
Whole mvebu(64) I would retire after 23.05. when we have stable 6.1 kernel
<Heisath>
@Bug those links are horrible we need to put them somewhere ppl can find them.
<IgorPec>
we need to keep providing images, that'ts the point
<IgorPec>
and we should not tag those images as some low quality materiral
<IgorPec>
which happens if we say "not supported". that's what i want to emphasise
rpardini has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Heisath>
Could call it not maintained anymore
<IgorPec>
please come out with concrete ideas which to remove
<IgorPec>
also one idea is to have a section on the download pages, below
<Heisath>
+1 for that.
<IgorPec>
hot stuff, maturer+stable, community (link to that page)
<Heisath>
Now it could also be some nsfw stuff
rpardini has joined #armbian
<IgorPec>
ok
<Heisath>
#topic release officer then?
<IgorPec>
yes
<Heisath>
<-
<IgorPec>
ok
<Werner>
#topic release officer
ArmbianHelper changed the topic of #armbian to: release officer (Meeting topic: developer meeting)
<Heisath>
this one right here sheriff.
<IgorPec>
Heisath, if you can, it would help a lot
<IgorPec>
if someone steps out even better
<Heisath>
I will be unavailable from next weekend until 11. of feb.
<Heisath>
so can only really do something after that for codefreeze etc.
<IgorPec>
this we are talking about April [1st]
<Armbian-Discord>
<cats> TheBug: I also have the full archive on my LV mirror
<[TheBug]>
Nice!
<[TheBug]>
:)
<IgorPec>
dates for code freeze and release are setpo
<IgorPec>
we will take care of call for testers when far enough
<Heisath>
good.
<IgorPec>
but 1st of april will be around in no time ;)
<Heisath>
then #topic misc
<Werner>
#topic misc
ArmbianHelper changed the topic of #armbian to: misc (Meeting topic: developer meeting)
<Heisath>
Anything anyone wants to say about anywhat?
<[TheBug]>
Werner thanks for running meeting :D
<Heisath>
Okay then lets close the meeting.
<jock>
I have a question about the committees...
<Heisath>
Oh yeah right thoooose
<jock>
:9
<jock>
:)
<[TheBug]>
I don't have any new on that unfortunately, that is something that is still being worked on with slow progress.
<jock>
are going to be established, work is stopped for some reason, they are not worth it... ?
<IgorPec>
ideas are generally acceptable, we have prepared material
<jock>
ok thanks
<IgorPec>
we are so overloade with this management work
<rpardini>
(I missed the Amlogic topic so sneaking this in here) I've heard troubles with the BananaPi M5 (sic? the one in the last give away), does anyone know anything? I don't have it to test
<IgorPec>
even two people were on this full time for 6 months
<IgorPec>
too many issues to resolve, idea is developed to some degree, but executing it require again resources
<Heisath>
Gotta go now, sorry. Thanks and I will read the log if anything happened
<rpardini>
:salute:
<jock>
bye, thanks!
<IgorPec>
yes, thank you Heisath for help
<Werner>
Bye
Heisath has quit [Quit: Leaving]
<IgorPec>
thank you everyone for joining1!
<Werner>
#endmeeting
<ArmbianHelper>
Meeting ended Sat Jan 7 16:33:52 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com