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
lyri has quit [Ping timeout: 260 seconds]
lyri has joined #armbian
Mangix_ has quit [Ping timeout: 260 seconds]
Mangix has joined #armbian
montjoie has quit [Ping timeout: 255 seconds]
montjoie has joined #armbian
jantones has quit [Quit: Leaving]
lyri has quit [Ping timeout: 255 seconds]
lyri has joined #armbian
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian
<Macer>
I was just going off that earlier pine64 thread I posted.
<Macer>
sevan: it looks like people maybe got it working with newer uboot and newer mainline.
jclsn has quit [Ping timeout: 260 seconds]
jclsn has joined #armbian
crabbedhaloablut has joined #armbian
crabbedhaloablut has quit [Read error: Connection reset by peer]
crabbedhaloablut has joined #armbian
lyri has quit [Remote host closed the connection]
buzzmarshall has quit [Quit: Konversation terminated!]
jantones has joined #armbian
junaid_ has joined #armbian
junaid_ has quit [Remote host closed the connection]
jantones has quit [Quit: Leaving]
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
KREYREN_ has joined #armbian
marco44 has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
KREYREN__ has quit [Remote host closed the connection]
archetech has quit [Quit: Leaving]
marco44 has joined #armbian
danilogondolfo has joined #armbian
archetech has joined #armbian
tomreyn has quit [Quit: $Famous_last_words]
tomreyn has joined #armbian
<sevan>
Macer: understood. I'm on 6.1.55 here if that helps.
<sevan>
E: The repository 'http://beta.armbian.com bookworm Release' no longer has a Release file.
<Macer>
where on earth does armbian keep its settings to select which ui you start up?
<Macer>
ie: where do i cahnge defaults
<Macer>
i thought it would be in /etc/lightdm but i really don't see anything. i want to set it to ubutntu + wayland as default so i don't have to keep clicking on something to change it
<DC-IRC>
<viraniac> sevan: There is a repository update job running - https://github.com/armbian/os/actions. I suggest you to try again after some time
archetech has quit [Quit: Konversation terminated!]
<Macer>
e scratches his head
<Macer>
oops
<Macer>
ok well.. guess i'll hunt it down. weird that this isn't a bit more obvious in /etc/lightdm
<sevan>
viraniac: thanks for the heads up.
Net147 has joined #armbian
archetech has joined #armbian
gabes2 has joined #armbian
Tenkawa has joined #armbian
<Tenkawa>
Anyone else having Discord issues currently?
<Tenkawa>
Yep.. found thisf from another site:
<Tenkawa>
What we do know is that people are struggling to connect to Discord, and it’s not obvious why. On September 27, the official discord account on X (formerly Twitter), posted:
<Tenkawa>
That was on a PC review site
<Tenkawa>
They are apparently having a rough go.
rpardini has joined #armbian
<DC-IRC>
<viraniac> I am having issues as well, lets wait few hours may be it will discord team will get it sorted
<Tenkawa>
viraniac: yeah it appears they can't find the root cause at the moment and it appears more that its a problem of overwhelming system outages it sounds like
buzzmarshall has joined #armbian
rpardini has quit [Quit: ZZZzzz…]
<DC-IRC>
<Werner> Mobile seems fine
<CapNemo>
meanwhile irc still purrs without issue ^^
lyri has joined #armbian
<DC-IRC>
<tenkawa42> Now we're back
<DC-IRC>
<tenkawa42> That might be the most I've ever seen Discord out
alekksander has joined #armbian
oida has joined #armbian
rpardini has joined #armbian
rpardini has quit [Client Quit]
flyback has quit [Quit: Leaving]
flyback- has joined #armbian
flyback- has quit [Client Quit]
flyback has joined #armbian
yang has joined #armbian
rpardini has joined #armbian
alekksander has quit [Ping timeout: 255 seconds]
DarthGandalf has quit [Ping timeout: 245 seconds]
DarthGandalf has joined #armbian
zeemate has joined #armbian
rpardini has quit [Quit: ZZZzzz…]
rpardini has joined #armbian
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
danilogondolfo has quit [Remote host closed the connection]
rpardini has quit [Quit: gone]
zeemate has quit [Ping timeout: 258 seconds]
<KREYREN_>
It's taking so long to merge the riscv contributions that it seems that i have to refactor them again to make them usable
<KREYREN_>
my life is never ending suffering
<KREYREN_>
*receives 5 EUR donation with note "don't complain"*
<KREYREN_>
okay everything is fine
<DC-IRC>
<rpardini> yeah dude I'm not too thrilled about that opensbi builder at the core
<DC-IRC>
<rpardini> why don't use you use a hook? no one is ever maintaining any riscv at all since introduction, and you're adding moar stuff to maintain.
<KREYREN_>
because i want to maintain that? :D
<DC-IRC>
<rpardini> well then you should first refactor out the part you copy/pasted
<KREYREN_>
since it's not really high maintanance thing that can be always skipped with build option and is nice to have
<KREYREN_>
which one?
<DC-IRC>
<rpardini> dunno but looks like ATF to me?
<DC-IRC>
<rpardini> you _clearly_ copy/pasted most of it
<KREYREN_>
no i wrote the whole thing from scratch and then was told to scrap that and make it look like armbian standard
<DC-IRC>
<rpardini> ATF was already pretty abandoned, and you duplicated it. no, go reduce that to a hook in your family file
<KREYREN_>
there is actually a lot of though behind it to make it work btw
<DC-IRC>
<rpardini> If you get to a point where it _makes sense_ to be generic core thing then we'll think again
<KREYREN_>
it's literally the thing that makes the board to boot
<KREYREN_>
hard dependency
<KREYREN_>
making that a pre-built thing is imho not smart
<DC-IRC>
<rpardini> also learn to _read_, that's not what I said
<DC-IRC>
<rpardini> I said _implement the build in a hook in your family code_, not _use a prebuilt_
<KREYREN_>
i know afaik the opensbi binary by chainsx is compiled for licheepi4a
<DC-IRC>
<rpardini> betcha you can build it in 20 lines of hook code
<KREYREN_>
so puting that in family code doesn't make sense to me since they seem to each need different one
<DC-IRC>
<rpardini> if it does not fit in family code, refactor out the parts that are common, and use board code to hook
<DC-IRC>
<rpardini> or simply do it all in board code
<DC-IRC>
<rpardini> meson-s4t7 is common across S4 and T7... so 3 boards
<DC-IRC>
<rpardini> you're adding _core stuff_ to support a single board
<DC-IRC>
<rpardini> no, do at family what is potentially useful for other boards, otherwise do in board
<DC-IRC>
<rpardini> reduce your blast radius. we've no indication of _any_ continued support of riscv64 stuff
<KREYREN_>
i hate that it's integrating something that we are not sure will work for other boards so it's adding work in the long run.. i would prefer to integrate that as a family code when we have more riscv systems that we know actually work with the blob
<DC-IRC>
<rpardini> ok. so not family ready, _definitely_ not core ready
<DC-IRC>
<rpardini> so _go do it in board code_
<KREYREN_>
dunno what you mean core ready
<KREYREN_>
afaik it's like uboot where each needs different config
Tenkawa has left #armbian [Was I really ever here?]
<KREYREN_>
we could provide one to run them all but then we would provide a64_defconfig crust config for olimex teres-a64 which then causes issues and takes me 2 weeks to figure out why bcs it's hidden somewhere in the include file
<KREYREN_>
so i assume similar situation would be there if it was in family code
<KREYREN_>
so the board code makes it more flexible and once we can confirm that we can make a generic binary that works then we could use that in family
<DC-IRC>
<rpardini> core code is in `lib/` folder
<DC-IRC>
<rpardini> don't touch anything there, do all your stuff in `config/boards/xxx.whatever`
<DC-IRC>
<rpardini> we've plently hooks for uboot, and you'll get version hash for free in return
<DC-IRC>
<rpardini> again, go look at meson-s4t7 -- except add your hooks to board file.
<KREYREN_>
that's overcomplicating it and making a hacky solution for opensbi compilation so more issues than solutions in terms of features and support
<DC-IRC>
<rpardini> well that
<DC-IRC>
<rpardini> I'm not overcomplicating anything, you're adding a shitton of copy/pasted code, I'm telling you to do it properly.
<DC-IRC>
<rpardini> since it's unproven, it does not belong in core
<DC-IRC>
<rpardini> it seems it does not even belong in family code
<DC-IRC>
<rpardini> so board code is your only option.
<KREYREN_>
it's not copy pasting it's rewritting in armbian standard from a objectively better code in original licheepi4a contribution
<DC-IRC>
<rpardini> that's all the time I'm gonna waste on this
<DC-IRC>
<rpardini> good luck
<KREYREN_>
like it might look copy pasted but this is like 18 hours of work
<KREYREN_>
and like i plan on refactoring the whole compilation management but that is not within the scope of the OpenSBI contribution atm
<KREYREN_>
which is mostly me refactoring chainsx's code
<DC-IRC>
<rpardini> Yeah I won't take that. That's adding opensbi to core. Reduce that to 20 lines of hook code in your board file.
<DC-IRC>
<rpardini> fetch it, build it, use it in your u-boot build hook
<KREYREN_>
I won't it's adding lot of work so that i get to do more work later which is really stupid, if you don't want to merge it then it will work without the OpenSBI compilation for the time being
<DC-IRC>
<rpardini> how will it work if you're building u-boot and no sbi? blob?
<KREYREN_>
it already has blob contributed by chainsx and the beaglev and licheepi4a use the same chip
<KREYREN_>
the opensbi is meant to be a management for more riscv chips down the line
<DC-IRC>
<rpardini> well then close the sbi PR, fix the board PR not even mention it
<KREYREN_>
not just special feature for one board
<DC-IRC>
<rpardini> dude I know perfectly well what sbi is, I just don't want to add support for building it to core. _use hooks_
<KREYREN_>
you explained hooks as function added to the family scope.. opensbi is too complex to be painlessly maintained in that
<KREYREN_>
well opensbi compilation
<KREYREN_>
could i do that in less than 20 lines? yes.. doesn't mean that it's a good idea
hook has joined #armbian
<DC-IRC>
<rpardini> we discussed this during meeting yesterday. we don't wanna add _more_ riscv stuff to core, for now at least.
<DC-IRC>
<rpardini> so hooks are your only option for adding opensbi build.
<DC-IRC>
<rpardini> so it's either use hooks, or close the PR