System_Error has quit [Remote host closed the connection]
[TheBug] has quit [Ping timeout: 244 seconds]
System_Error has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
ikmaak has quit [Quit: No Ping reply in 210 seconds.]
ikmaak has joined #maemo-leste
[TheBug] has joined #maemo-leste
[TheBug] has quit [Changing host]
[TheBug] has joined #maemo-leste
joerg has quit [Ping timeout: 272 seconds]
joerg has joined #maemo-leste
DFP has joined #maemo-leste
_fab has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
ceene has joined #maemo-leste
System_Error has joined #maemo-leste
sch has joined #maemo-leste
xinomilo has joined #maemo-leste
vectis_ has joined #maemo-leste
saeed has quit [Ping timeout: 260 seconds]
<erebion>
Wizzup: Got any docs on porting? What's the process like for Maemo? Just want to know what that entails. I'd try to get a Maemo image at least booting, then I can see whether I get the rest working well.
System_Error has quit [Remote host closed the connection]
[TheBug] has joined #maemo-leste
System_Error has joined #maemo-leste
peetah has quit [Ping timeout: 244 seconds]
Livio has quit [Ping timeout: 244 seconds]
_fab_ has quit [Quit: _fab_]
_fab has joined #maemo-leste
<Wizzup>
erebion: getting things to work is mostly a matter of taking a rootfs tar, unpacking it and adding the right kernel/bootloader, once that works we have an image generation process and a few packages for device specific config and device-specific dependencies
<Wizzup>
is this aarch64?
<erebion>
Yup
<erebion>
I'm pretty sure it'll work, as I already got it to work with Mobian, so I'd just try generating an image with the kernel that Mobian uses and look at the device-specific configs and I'm pretty sure I'll end up with a somewhat working port
pere has quit [Ping timeout: 265 seconds]
xinomilo has quit [Ping timeout: 265 seconds]
xinomilo has joined #maemo-leste
Livio has joined #maemo-leste
<Wizzup>
erebion: what does mobian use for image generation?
<Wizzup>
I am asking mostly because I'm not super happy with our image generation tooling
<Wizzup>
erebion: in any case I can help assist with maemo specific questions when porting
<Wizzup>
I think we have a generic aarch64 tar rootfs
mkfx has left #maemo-leste [Error from remote client]
<erebion>
Wizzup: One would just execute for example this: ./build.sh -t sdm670 -s -u mobian -c -R myverysecretlukspassphrase | tee mobian-build.log # -s for SSH enabled
<erebion>
Wizzup: This is pretty everything that's required.
<erebion>
Wizzup: Assuming all info is there and there is a kernel, I could port to a device like the Pixel 3a in 10 minutes plus some time for compiling the kernel and building the image
<erebion>
Wizzup: plus some time for everything that isn't clear and has to be found out, of course
<Wizzup>
sounds good, thank you, let me study this a bit (in a few hrs)
_fab has quit [Quit: _fab]
<freemangordon>
would pinephone image be useful?
_fab has joined #maemo-leste
_fab has quit [Quit: _fab]
<erebion>
Wizzup: I wonder if this could be made into something that can be used for both Mobian and Maemo, then both projects would benefit from improvements and a ported device should automatically get an image in the other project, just with some things missing, but a lot could probably be made to work that way
<erebion>
Wizzup: But I know to little about how Maemo works yet to be sure, just an idea
<Wizzup>
I can try to write up a bit how maemo works but I have to head out first - when I gte back I can do some write up
<erebion>
*too
<Wizzup>
and yes, I'd like something like that too
<erebion>
Wizzup: Would be appreciated, I'd then try to get it ported to the Pixel 3a
<erebion>
And if I can find a working kernel, I'd have a look at the Xperia 10 II as well, that one arrives later today
<erebion>
* 10 III
saeed has joined #maemo-leste
<erebion>
Currently working on packaging an eSIM provisioning tool, so that feature would then be covered for both.
<erebion>
Also, Mobian has everything in the Debian repos except very few things which cannot be uploaded, mostly kernels: https://repo.mobian.org
<dsc_>
(you can ignore the VNC part, thats just how I choose to visually interact with the VM)
<dsc_>
because gnome + DPI scaling + QEMU spice viewer thingy = no workie
nela has quit [Ping timeout: 272 seconds]
nela has joined #maemo-leste
<erebion>
Huh
<erebion>
Will try to adapt that to virt-manager, cause that's how I like to interact with it
<erebion>
BTW, I always wanted to ask: What was the reasoning behind choosing Devuan over Debian?
<erebion>
Well, those are the settings I'm using
<erebion>
Perhaps a bug in qemu x86_64 on aarch64
<Wizzup>
erebion: the reasoning was that we used what was closer to fremantle in init style
<Wizzup>
also one of the founding devs was also a devuan developer
<erebion>
Ah, then it makes sense
<erebion>
Not because "systemd is from hell", but because the dev knew it well at the time :)
<Wizzup>
there might be some debian based version in the near future, right now we want to finish the daedalus migration (I think most people already migrated anyway) and then move to excalibur/trixie first, and then we'll see at swapping out pieces (gtk2, init stuff)
<Wizzup>
of course, if someone want to contribute/maintain that, we can ship both in one package afaict
<Wizzup>
it's mostly zsh and some other things and it has some issues, which is one of the reasons I'd like to migrate to a more clear style like the mobian stuff you linked
<Wizzup>
building a leste image is mostly a matter of configuring the device type, which typically has its own meta package, e.g. hildon-meta-droid4, which pulls in additional packages
<Wizzup>
so ideally the image builder doesn't know much about the device beyond what u-boot it might need, if we haven't packaged that yet, so that it build u-boot and dd it to the right place of the image, the same applies to partitioning
<Wizzup>
but, as stated, I'd like to move away from this to a debos or similar to mobian system
<Wizzup>
but for device porting, if you'd like to make an image, you'd need ultimately add a few things to arm-sdk and image-builder, but the main things would be a leste-config-<devname> and hildon-meta-<devname>, and define what additional packages are needed (is just upstream kernel ok, or do we need additional patches, in which case we'd maybe have to make a specific kernel pkg for it)
<Wizzup>
I also have virt-manager here so I can try to give that a try as well, I haven't used it for yet leste development since I have my shell scripts that start qemu, but I've been moving my infra on my servers all to libvirt, so it'd make sense to try to do the same with my maemo dev env
Livio has joined #maemo-leste
Twig has quit [Remote host closed the connection]
Twig has joined #maemo-leste
Livio has quit [Ping timeout: 244 seconds]
Livio has joined #maemo-leste
<inky>
perhaps i have to try to do a pinebook pro build. thank you for information.
arno11 has joined #maemo-leste
narodnik2 has quit [Ping timeout: 272 seconds]
System_Error has quit [Ping timeout: 244 seconds]
DFP1 has joined #maemo-leste
kiva has joined #maemo-leste
DFP has quit [Ping timeout: 260 seconds]
_fab has joined #maemo-leste
System_Error has joined #maemo-leste
arno11 has quit [Ping timeout: 265 seconds]
saeed has quit [Remote host closed the connection]
_fab has quit [Ping timeout: 260 seconds]
arno11 has joined #maemo-leste
arno11 has quit [Read error: Connection reset by peer]
<kiva>
Wizzup: put that to Leste wiki, just copy paste as example and clean up it as much you have time and improve later.
Livio_ has joined #maemo-leste
Livio has quit [Ping timeout: 244 seconds]
Twig has quit [Remote host closed the connection]
<kiva>
inky: ah that full screen thing was overlap windows..only time I have missed it in small screens is in file management..maybe side by side two thunar windows fork would be solution...when you have missed it with Maemo?
xinomilo has quit [Quit: Leaving]
Livio_ has quit [Ping timeout: 244 seconds]
f_ is now known as funderscore
Livio has joined #maemo-leste
kiva has quit [Quit: human have to sleep to make some clean ups in memory.]
<inky>
kiva, i use maemo with motorola lapdock, on a big screen. it becomes like a laptop. i also use it on a pinephone withkeyboard. and i code. so i need to look at some window, and code in other.
<inky>
that can be chat & vim, can be terminal that shows me interface or manual, and vim, can be browser and vim.
<sicelo>
yes Hildon doesn't support multi-window.
<sicelo>
the underlying matchbox WM was specifically designed to show 1, and only one window at a time
<sicelo>
of course i guess supporting two windows might be a worthwhile goal, but someone needs to put in the work :-)
<dsc_>
i was already investigating this, in this particular case for the vkb
<dsc_>
where it horizontally splits 50%
<dsc_>
just an investigation so far, its a bit 'involved' and currently busy with porting some Qt plugins stuff to Qt6
<dsc_>
but I have Hildon running with a remote debugger etc.
<dsc_>
which is the first step :p
crab has quit [Quit: WeeChat 4.5.1]
akossh has joined #maemo-leste
crab has joined #maemo-leste
System_Error has quit [Ping timeout: 244 seconds]
System_Error has joined #maemo-leste
Anasko has joined #maemo-leste
Anasko has quit [Read error: Connection reset by peer]