<mighty17[m]>
sicelo ig u need power supply info from maemo as well? :p
diejuse has quit [Quit: Leaving.]
<parazyd>
mighty17[m]: Yeah that's what he's asking
diejuse has joined #maemo-leste
<mighty17[m]>
parazyd my question is different iirc he wanted pm comparison of Tab2 and droid4 as Tab2 has old uboot so dmesg says pm isn't available (pm = power management)
diejuse has quit [Read error: No route to host]
<uvos__>
no he wanted to kown if cat /sys/class/power_supply/*/charge_full_design has the right mAh value
<uvos__>
as this is your responsability to set in the battery driver
<uvos__>
either by dts bindings or the driver autodetecting it via nvram
diejuse has joined #maemo-leste
Pali has joined #maemo-leste
<parazyd>
freemangordon, Wizzup: Is also wpa_supplicant from devel supposed to go to stable?
<Wizzup>
no no no
<parazyd>
lol ok
<parazyd>
Just asking
<parazyd>
I'm going to promote what I can today
<uvos__>
btw parazyd we should maybe flip on charge-mode for devel
<parazyd>
uvos__: ok, let me clean devel up first and then do further tweaks
<uvos__>
ok
<parazyd>
I don't like it when there's too many packages there.
<parazyd>
uvos__: it's built because of matchbox also, your 49fbe681b34794cc6501d2a024870143abe41b21 patch
<parazyd>
> Fix fullscreen handling for fullscreen override redirect windows
<uvos__>
oh that
<uvos__>
yeah we can promote it
<parazyd>
Wizzup, uvos__: What about osso-systemui powerkeymenu/splashscreen/tklock ?
<Wizzup>
sorry, I can do this later but not right now
<Wizzup>
I think those are probably fine, though
<uvos__>
parazyd: yes those are needed bugfixes
xmn has quit [Quit: ZZZzzz…]
<uvos__>
related to the machbox change
<uvos__>
you must promote togehter
<parazyd>
uvos__: You mean systemui+matchbox?
<uvos__>
yes
<parazyd>
ACK
<parazyd>
Thanks
<parazyd>
uvos__: Are you using dsme on your devel device?
<uvos__>
parazyd: yes no
<parazyd>
ok, I mean, you haven't noticed any problems or something?
* parazyd
hasn't
<uvos__>
parazyd: no
<parazyd>
ok
<uvos__>
parazyd: but i changed several init scripts to remove dsmetool
<uvos__>
and i dont load the dsme mce module
<uvos__>
so dsme is pretty impotent on my device
<parazyd>
ok, this is unrelated
<uvos__>
idk if id notice if it breaks
<uvos__>
ok
<uvos__>
the kerecv change also looks fine
<parazyd>
*nod*
<uvos__>
byw you might want to keep osso-systemui-splashscreen in devel
<uvos__>
no one has tested this yet
<uvos__>
and its unfinished afaik
<parazyd>
True
<uvos__>
but we also dont use it
<uvos__>
hildon-input-method is fine
<uvos__>
this was just the utf8 change
<uvos__>
i thnk thats it
<parazyd>
mhm
<mighty17[m]>
either by dts bindings or the driver autodetecting it via nvram > okay, i will try a full charge and discharge first to get it calibrated
uvos__ is now known as uvos
<uvos>
mighty17[m]: this wont help if dts is wrong
<uvos>
probubly
<uvos>
any sane driver will reject a cal value so different from charge_full_design
<mighty17[m]>
i havent put any info in dts about battery size
<uvos>
your driver might not have dts bindigns for this
<uvos>
cpcap dosent for instance
<uvos>
isntead you might have to add your battery to the driver
<mighty17[m]>
max17042 fuel gauge ig
<mighty17[m]>
and my charger isnt in mainline :P
<uvos>
its about the fule gage
<uvos>
max17042 has some way to detect or gain the capacity
<uvos>
you have to figure out what it is and add your battery
<uvos>
cpcap dose this too but its not nesscarly the right way to do it
<uvos>
(might also be the only way .. read the driver)
<uvos>
nothing in leste dose this btw
<uvos>
2000000 is likely simply the default
<uvos>
on the drivers side
<mighty17[m]>
oh so most likely i have to specify it somewhere
diejuse has quit [Quit: Leaving.]
lioh has joined #maemo-leste
<lioh>
hi all. I am facing the issue that Maemo Leste boots fine on my N900 (I can see the boot messages) but I don't get a graphical interface.
<lioh>
It was working already but currently the screen just stays blank after boot
<parazyd>
Do you wait enough time? I tried a fresh flash yesterday and it took me a minute to show up.
<parazyd>
Like, actual 60-70 seconds
<lioh>
I have waited that time, but battery level is already in the lower part, so maybe it's related to that. I am going to charge now and try again.
<parazyd>
It might be. You can also boot to Fremantle and charge it normally.
<lioh>
I have flashed uboot so no fermantle anymore I guess
<lioh>
also I always have to type run sdboot after startup.
<lioh>
One time I got a selection Menu from uboot, but since then I have never seen it again and I don't know how to trigger it
<parazyd>
Boot with the keyboard opened
<parazyd>
This'll get you to u-boot
<parazyd>
If it's closed then it automatically boots to fremantle iirc
<lioh>
Which does not seem to be available anymore after running sudo ./0xFFFF -m u-boot-2013.04-2.bin -f
<lioh>
Is there a way to flash both? on the internal storage fermantle and leste on the sd-card?
<lioh>
Maybe even using 0xFFFF?
<parazyd>
Pali: Maybe you know? ^
<parazyd>
On mine I installed u-boot through fremantle, not with 0xffff so I'm not sure.
<parazyd>
In any case, you might also be able to charge it while it's powered off. It's just that sometimes when you plug in, the phone powers on.
<uvos>
its just the appended kernel missing
<parazyd>
I don't know if charging works in u-boot
<uvos>
so you should be able to somehow append the kernel
<uvos>
idk why we dont just have a image for people to install
<uvos>
that has the freemantle kernel appended
<parazyd>
Because there are different kernels for fremantle
<uvos>
sure but the latest/last one should work fine with anything right?
<uvos>
or dose pvr get in the way?
<uvos>
its static anyhow no?
<lioh>
so you thing fermantle is still on the emmc and should still be bootable?
<lioh>
hmm if i select internal emmc on uboot menu it is unable to find the relevant partitions
<Wizzup>
parazyd: this is the second report of this happening recently I think
<Wizzup>
I can test the latest image on mine and see what hapens
<Wizzup>
also, we should probably figure out what log files are most relevant
<parazyd>
mtg now, bbl
<Wizzup>
openrc can also log
<Wizzup>
:p
<Wizzup>
lioh: I'll try to reproduce this today or tomorrow at latest (also in mtg atm)
venji10[m] has quit [Quit: Bridge terminating on SIGTERM]
ajr has quit [Quit: Bridge terminating on SIGTERM]
mighty17[m] has quit [Quit: Bridge terminating on SIGTERM]
tvall has quit [Quit: Bridge terminating on SIGTERM]
scops has quit [Quit: Bridge terminating on SIGTERM]
tvall has joined #maemo-leste
scops has joined #maemo-leste
ajr has joined #maemo-leste
venji10[m] has joined #maemo-leste
mighty17[m] has joined #maemo-leste
lioh has quit [Remote host closed the connection]
lioh has joined #maemo-leste
<lioh>
is there a way to increase screen brightness on boot?
<parazyd>
In u-boot? Don't think so.
<parazyd>
Booting normally with the power button should enable backlight
<mighty17[m]>
`PVRMMapRemoveRegisteredArea: psOffsetStruct 0xdb27724a for memory area 0x0x6051b23f is still mapped; psOffsetStruct->ui32Mapped 1 [1754, rivers/gpu/drm/pvrsgx/1.9.2253347/services4/srvkm/env/linux/mmap.c` hm?
<mighty17[m]>
also also `iptables/1.8.2 Failed to initialize nft: Protocol not supported` happened when i installed anbox, ig we need CONFIG_NFT_COMPAT in defconfig
<parazyd>
If your device is locked, this might be the reason desktop isn't showing up
<parazyd>
Wizzup knows the intricacies of this on Leste
<lioh>
desktop is showing again after putting it to charge
<sicelo>
If you have lock code issues, you might have easier time if you first fix your Fremantle ... there are ways to recover it. Search tmo (talk.maemo.org)
<lioh>
device lock is currently disabled
<sicelo>
Ah, ok
<lioh>
yes, but if i understood you right, i should only need to add fermantle to the bootloader right?
<lioh>
Or does it chain-boot?
<lioh>
Loading the Fermantle bootloader from the emmc using u-boot?
<lioh>
Because just selecting 'boot from emmc' in the uboot menu does not work as mentioned
<lioh>
and reflashing Fermantle is really a mess. At least on a recent x86_64 system. I have already found an old debian live image containing flasher. maybe I could give this one a try
<Wizzup>
lioh: so did you manage to make leste rende rok on boot, or is there still a problem with the image?
<uvos>
"[13:46] <lioh> desktop is showing again after putting it to charge"
<uvos>
not sure why the device would hang somewhere before hildon when the battery is low
<uvos>
instead of eg. powering back off
<parazyd>
tbh it might be powering off
mrkrisprolls has quit [Remote host closed the connection]
Oksana has quit [Ping timeout: 268 seconds]
diejuse has joined #maemo-leste
mrkrisprolls has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
Danct12 has joined #maemo-leste
Danct12 has quit [Changing host]
xmn has joined #maemo-leste
Daanct12 has joined #maemo-leste
Daanct12 has quit [Changing host]
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 268 seconds]
_whitelogger has joined #maemo-leste
<sicelo>
I don't think reflashing Fremantle is really a big mess :-)
<sicelo>
Anyway, since lock code isn't active, you don't have a big need to get into Fremantle
<Wizzup>
I think getting an upgraded fremantle with cssu is painful
<Wizzup>
tbh
* uvos
tried that and failed
<uvos>
or gave up anyhow
<sicelo>
You don't need cssu to fix lock code though. Anyhow,
<sicelo>
Anyone knows if N9 & N950 use cal?
<sicelo>
Or it's only N900?
<Pali>
lioh: parazyd: you need to generate combined.bin image, not to flash u-boot.bin only
<Pali>
use script u-boot-gen-combined to generate combined.bin binary from u-boot.bin and uImage kernel
<Pali>
to unpack fiasco, use: 0xFFFF -M zimage.fiasco -u
<Pali>
parazyd: u-boot does not support battery charging
<freemangordon>
Pali: do I get it right, that this guy wants me to post an one-liner patch?
<Pali>
freemangordon: seems to
<freemangordon>
ok :)
<Pali>
put it into reply to that email
<freemangordon>
sure
<Pali>
thx!
<tmlind>
uvos: hey cool, looks like on mz609 this works now: sudo fastboot flash utags utags-mz609-32-mmcblk1p6-boots-mmcblk1p18-kexecboot.bin
<freemangordon>
Pali: sent
<tmlind>
uvos: that is after flashing the allow-mbmloader-flashing-mbm.bin from the "Xoom2 ME.rar" package like you suggested
<uvos>
tmlind: yaay :)
<freemangordon>
oh, seems I don;t need moderator approval anymore :)
<uvos>
tmlind: great now we can avoid to bricking the things
<tmlind>
uvos: maybe you forgot to do fastboot reboot bootloader, or your writes were not working
<uvos>
my wirtes where not working
<tmlind>
uvos: ok
<uvos>
i rebooted multiple times after that
<uvos>
and its still at the version number from honycomb
<uvos>
(fastboot version)
<tmlind>
uvos: we can also probably now use some other partition other than cache partition for kexecboot
<uvos>
depends on what mbm cares about
<uvos>
but now you can expierament without accedentaly bricking the thing
<tmlind>
hmm we should try to find the allow-mbmloader-flashing-mbm.bin also for the 10" tablets
<uvos>
tmlind: yeah
<uvos>
tmlind: btw have a cdt.bin for mz609 or dose it not use that?
<uvos>
looks like motoboot.img mentions it
<uvos>
looks kinda like motoboot maybe contains a bunch of stuff compressed or soemthing
<tmlind>
uvos: did not flash that one, i think that's really only used for boot time checks
<uvos>
right but it includes cdt.bin in its header
<uvos>
but no cdt.bin
<tmlind>
uvos: i believe cdt.bin does not matter for allow-mbmloader-flashing-mbm.bin, it might make a difference after flashing something and rebooting though
<uvos>
ok
<tmlind>
well that's just my gut feeling based on experiments
<tmlind>
so maybe mz615 european model had a different number and we need to search for that firmware?
<Wizzup>
freemangordon: Pali: looks like tom didn't respond to the point about having to port to dts
<Wizzup>
not sure if he got that or not
<Pali>
Wizzup: I really do not know... if you think that you can re-phrase freemangordon's email that there is missing response to dts, please do it
<Pali>
I'm really lost now :-(
<Wizzup>
he wrote an email 7 minutes ago which I think is a bit more clear
<Pali>
I see "provide a linkable but not runnable"
<Pali>
so just provide fake stubs for those functions which are missing at linker time?
<Pali>
so linking step passes?
<Pali>
I do not know
crab has quit [Quit: WeeChat 2.3]
diejuse has quit [Quit: Leaving.]
Daanct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
Danct12 has joined #maemo-leste
Danct12 has quit [Changing host]
<freemangordon>
Wizzup: could you please step in as it seems for some reason my explanations about DTS are not clear to Tom.
<Wizzup>
ok
<freemangordon>
and no, his last mail is not clear to me, in terms that I don;t understand how can I create linkable binary without enabling OF_CONTROL
<freemangordon>
well, I can tweak Makefiles here and there, but is it what he wants me to do
belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 244 seconds]
belcher_ is now known as belcher
<Pali>
createing empty stubs in rx51 board code for "missing" of functions may produce linkable binary
<Pali>
this is probably the easiest way
mardy has quit [Quit: WeeChat 2.8]
diejuse has joined #maemo-leste
<Wizzup>
freemangordon: ping
<freemangordon>
Wizzup: pong
<Wizzup>
freemangordon: just one second, I'd like you to read the email I will send to u-boot ml and confirm
<freemangordon>
ok
<freemangordon>
in the meanwhile, I was just able to hack uboot to link without OF_CONTROL enabled