freemangordon has quit [Read error: Connection reset by peer]
<tmlind>
hmm how fast does it need to be?
<tmlind>
if it does not have to be super fast, m1 mini running linux might do. i don't think it has 32-bit arm support if you need to compile in a chroot though, i could be wrong
Arch-TK has joined #maemo-leste
<tmlind>
my m1 macbook air running linux builds kernel and modules in about 5 mins, so quite usable for building stuff
atk has quit [Remote host closed the connection]
<tmlind>
i think it's thermal throttling a lot though
<tmlind>
the current generation of arm servers may be disappointing for build boxes still, single core performance sucks on them and that's needed for linking unless lld is used
<buZz>
tmlind: how's the linux port for it?
bencoh has joined #maemo-leste
bencoh has quit [Changing host]
<tmlind>
buZz: mainline has basic support for the cpu, driver patches missing for nvme and wlan at least. still using the corellium kernel that works with xorg
<Wizzup>
tmlind: if kvm works that's fine too
<tmlind>
Wizzup: folks are playing with virtualization on #asahilinux, not sure if kvm works yet, some patches went in though
<Wizzup>
tmlind: hmmm ok, I am kind of looking for something that 'just works' given that I am not always physically around to reset/fix things
<Wizzup>
but it's an interesting suggestion
<tmlind>
Wizzup: yeah, get a remove power switch too still :)
<tmlind>
s/remove/remote/
<tmlind>
if 32-bit instructions don't work, m1 mini might not be that usable for m-l though
<Wizzup>
well our current setup does, it's just scummvm that's particularly bad wrt build system
<buZz>
'a pile of raspi' with some remote relays etc might make a lot more sense
<buZz>
financially
<buZz>
or well, raspi-alike with real storage perhaps
<tmlind>
yeah fast storage and preferrably at least 8GB of memory is needed to build stuff
<tmlind>
rust is a different story though.. i tried building alacritty for arm and had to add a swap file despite 8GB of memory :(
<Wizzup>
we'd use ata over ethernet'
<buZz>
and usbethernet? :D
sunshavi has joined #maemo-leste
<Wizzup>
buZz: doesn't pi4 have gbe?
<buZz>
yeah it does
<buZz>
and comes in high ram modesl
<buZz>
models*
<buZz>
all other pis use usbethernet though
<buZz>
always suprised me that -broadcom- would make a soc without networking
<Wizzup>
I think I have the 8GB model here
diejuse1 has quit [Quit: Leaving.]
vectis has quit [Ping timeout: 252 seconds]
vectis has joined #maemo-leste
<uvos>
wait whats the problem with crosscompiling everything on x86
<uvos>
am i missing something?
<Wizzup>
do you mean with qemu-user?
<uvos>
no i mean with just arm-linux-gnueabihf-g* and a leste rootfs
<bencoh>
just a leste rootfs won't be enough, many packages break when crosscompiling them out-of-the-box
<bencoh>
but you can do what scratchbox used to do, it's just a pain to setup/optimize
<uvos>
why/ how do they break
<uvos>
i have done this before, addmitily with farily trival programs
<bencoh>
I don't remember for every package, but you can try to build Xorg and see if it works for instance
<bencoh>
it might have been fixed since then though
<Wizzup>
uvos: things break (like scummvm), and I don't want to fix their broken build systems and just work on our things
<bencoh>
(by out-of-the-box, I meant using the dbuild/dpkg-buildpackage crosscompiling facility)
<Wizzup>
and we had it like this before: qemu-system for armv7l
<uvos>
i gues the most cost efective way to do it would be to have a beefy x86 box that uses debian crosscompile suport and have jenkins build on that and then if the build fails it trys to do it on a rpi or soemthing
<uvos>
should not be to hard to set up
<uvos>
a beefy arm box is even less work ofc
<uvos>
or a big farm of cheep sbcs
<uvos>
but you will run into a package that just needs to mutch ram for a sbc eventually
<buZz>
8GB ram on pi4, uvos :)
<uvos>
8gb is tight
<Wizzup>
uvos: we do it with less atm
<uvos>
try compiling something like freecad
<buZz>
uvos: i'd name libboost as notoriously big to build
<uvos>
Wizzup: sure our packages are small atm
<Wizzup>
I have a system where we can do qemu-user with armv7 btw
<Wizzup>
it's NP to do that now
<Wizzup>
but it's slow
<Wizzup>
even if it's beefy
<Wizzup>
a pi is faster
<uvos>
i mean a realy quick optimization for that box is for it to try to crosscompile and then use qemu
<uvos>
i dont see mutch downside to doing this
random_yanek has quit [Ping timeout: 250 seconds]
<Wizzup>
uvos: it will break in many unexpected ways, especially newer build systems are not good at cross compiling
<Wizzup>
cmake used be a bad offender
<Wizzup>
probably not so much anymore
<Wizzup>
I'd really rather have a 'native' arch (even if it's emulated), rather than a chroot with different host arch
<uvos>
Wizzup: just listing that really we only "support" n900,mapphones and the pp
<uvos>
Wizzup: with the rest being just testing and dont-expect-it-to-even-boot
<uvos>
Wizzup: otherwise people get dissapointed
<uvos>
and makes a bad image
<Wizzup>
agreed
pere has joined #maemo-leste
<Wizzup>
not sure if we can do it with our wiki, or if we need plugins like semantic mediawiki
<sicelo>
M-L evolving too fast for me to know what's the plan ... dropping N9?
<Wizzup>
sicelo: no, just state it as 'not really working atm'
<uvos>
yeah right now its really hard to discover what devices acctually work
<uvos>
and the level of testing and developer attention between something like the n9 target
<uvos>
and the d4 target is vast
<sicelo>
Last I recall parazyd was doing some N9 work
sunshavi has quit [Read error: Connection reset by peer]
jonsger has joined #maemo-leste
sunshavi has joined #maemo-leste
diejuse1 has joined #maemo-leste
diejuse1 has quit [Ping timeout: 265 seconds]
<Wizzup>
I have one too
<Wizzup>
dreamer: have time to help us with our wiki? :-p
<dreamer>
omg -_-
* dreamer
hasn't done serious wiki-work in like 6 years
<dreamer>
what do you need exactly? :)
<dreamer>
(and I don't exactly have that much time to spare, but many hands make light work I guess :) )
<dreamer>
apparently I do have an account on the wiki though :)
* enyc
meows
* enyc
thinks n900 battory failed somehow ;-( never stays on long
<uvos>
enyc: possibly
<uvos>
enyc: my n900 underdischarges the battery with leste
<enyc>
uvos: interesting... in my case I put on external charger in any case
<uvos>
ok
<uvos>
but be carfull, with mapphones too
<uvos>
currently leste will turn off at <3v in cases
<uvos>
thats pretty bad for the batteries
<enyc>
I don't understand "mapphones too"
<uvos>
enyc: mapphones = the motorola devices
<enyc>
i.e. droid4 and otherwise [ok]
<Wizzup>
dreamer: well, I think our wiki could benefit from someone who understands it a bit better, so some semantic mediawiki stuff perhaps (maybe it's not even required)
<Entitlement>
dreamer - [ Version - Maemo Leste Wiki ]
<dreamer>
oh, I see pmOS does that with some new thing called `cargo`
<dreamer>
(which just makes me think of rust ..)
<Wizzup>
cargo? hmm
<dreamer>
from that page you linked: `#cargo_query:`
<dreamer>
which seems to be installed
<dreamer>
"Cargo is an extension to MediaWiki that provides a lightweight way to store and query the data contained within the calls to templates, such as infoboxes. It is similar in concept to the Semantic MediaWiki extension, but offers a number of advantages, including ease of installation and ease of use. "
<dreamer>
I'll see if I can copy/paste some things from pmOS :)
<dreamer>
then you don't have to install SMW
<dreamer>
and I don't have to drudge up old knowledge, but instead learn something new
<Wizzup>
cool
<dreamer>
I hope to have some more time in 1-2 weeks. will see if I can at least make a start at that
<dreamer>
(and remind me if I don't :D)
<Wizzup>
ok, great
<dreamer>
Wizzup: do you want such a table on the frontpage?