<uvos>
Wizzup: yes i know, i was hopping this was the problem, but seemingly omapdrm refuses to even try and activate the dsi signal with the bridge as the endpoint
<uvos>
dont know why atm
<uvos>
mighty17[m]: sure but really you should try and find out where 170666667 comes from
<uvos>
mighty17[m]: its proubly something its caluclating from your pannel timeings or something like that
<uvos>
just trace it backwards
<mighty17[m]>
So you're saying that I'll have to patch things in kernel possibly?
<uvos>
maybe not, could be something in your dts if you have the timeings there - or your pannel driver if you have one (you should)
<uvos>
point is idk where it gets the rate from - i think it calculates it from the timeings, so to figure out where it comes from you have to read the code in the backtrace
<uvos>
(thats whats its for after all)
<mighty17[m]>
uvos: It's simple panel, maybe I need to upstream the original one?
<uvos>
no simple pannel should work in theory (but a pannel driver is perferd afaik) but idk how often im supposed to say it, read the code to the functions in the backtrace to figure out where the rate comes from....
<uvos>
or run the pannel at the "correct" rate
<uvos>
where it dosent work
<uvos>
and compear the reigster state with android
<uvos>
to figure out whats wrong
<mighty17[m]>
Yea yes, I get the part about backtrace, it's just that I'm being lazy at times for it :(
<uvos>
then you can go backwards from there
<uvos>
yeah i mean theres no free lunch im afraid
<mighty17[m]>
uvos: Rwmem right?
<uvos>
yeah
<uvos>
rwmem can ready any register if you know the address to it
<mighty17[m]>
i dunno the address in android tho
<uvos>
the TRM tells you
<uvos>
and ofc the registers addresses are the same on any os
<mighty17[m]>
<uvos> "mighty17: right @trm i would..." <- `-ash: ./rwmem: Permission denied`
<mighty17[m]>
even as sude
<mighty17[m]>
sudo*
<uvos>
on mainline?
<mighty17[m]>
yeah
<uvos>
theres a kernel config option that resetrcs access to /dev/mem to certain addresses iirc
<mighty17[m]>
hm will check
<mighty17[m]>
uvos: regarding android, does it need busybox and stuff to run? or just TWRP will be fine?
<mighty17[m]>
also `make_standalone_toolchain.py --arch arm --force --api 21 --stl gnustl --install-dir=$(SOME_PATH)` api matters here? as in will i have to use api21 rom on device as well
<mighty17[m]>
`export CROSS_COMPILE=$(SOME_PATH)/binary` binary doesnt exist in `$(SOME_PATH)`
<Wizzup>
so thumb2 builds are not possible with omap2plus_defconfig since armv6/omap2 doesn't do thumb, let's disable it for our builds
<uvos>
we allreday disable omap2
<Wizzup>
maybe, not in the droid4-linux that I have atm
<Wizzup>
sre seems to be MIA mostly btw, he was usually so quick to respond :)
<uvos>
mighty17[m]: the $(SOME_PATH) isent to be taken literally ofc
<uvos>
he as allways been MIA for as long as i have been around at least
<buZz>
Niklas[m]: but i'd love to hear how far you can get :D
<uvos>
the option i would reccomend is install devuan normaly, add our repos to your sources and install hildon-meta
<buZz>
ah, yes good point
<Niklas[m]>
And if I convert them to a ISO,can I boot them on real hardware?Does it support UEFI (this stupid thing has no legacy boot -.-)
<buZz>
but are there x86 packages in repo then?
<uvos>
buZz: yes
<buZz>
you cant convert a .vdi to .iso
<uvos>
amd64
<buZz>
uvos: sweet
<buZz>
Niklas[m]: so grab a devuan iso , install distro with uefi or whatever you want
<uvos>
we dont build x86-32 tho
<uvos>
so depends on how old his tablet is
<buZz>
then add repo and install hildon-meta
<buZz>
32bit only would be >15yo, i guess?
<Niklas[m]>
The CPU supports 64bit,but the UEFI is 32bit-only
<uvos>
some atom processors where pretty recent
<buZz>
Niklas[m]: ah one of -those-
<buZz>
lol
<uvos>
your uefi dosent support bios emulation?
<Niklas[m]>
Nope
<buZz>
those are quite a hell to work with :P
<uvos>
great
<uvos>
:P
<buZz>
i know fedora actively supports this 32bit-uefi-64bit-rootfs setup
<buZz>
or used to at least, i think fedora is over
<Niklas[m]>
I mean,it has like a dozen times more settings than the BIOS of my laptop,but legacy boot is not among them :/
<Niklas[m]>
I have Arch Linux installed currently.It supports 32bit UEFI with 64bit OS just fine,but since some updates ago I haven't been able to use a GUI because desktop environments getting more and more bloated and 1GB of RAM (not upgradeable) is too few for them
<Niklas[m]>
And it never ran smoothly.I hope Maemo can do better,as it still supports the Nokia N900 for example which has even less
<buZz>
Niklas[m]: why not just install fluxbox , openbox , blackbox , windowmaker , whatever
<uvos>
i mean if you get away from kde/gnome arch has no issues with 1gb on lxqt or something like i3, sway
<buZz>
any of the <10MB ram using window managers
<buZz>
twm , dwm
<Niklas[m]>
Yeah,but this thing has no hardware keyboard.GNOME is the only one which works quite well with touchscreen-only and a 7 inch screen
<uvos>
the benifit i gues is that we have a touch frendly ui