Daanct12 has quit [Read error: Connection reset by peer]
Daanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 264 seconds]
Daanct12 has joined #maemo-leste
Daanct12 has quit [Changing host]
Daanct12 has joined #maemo-leste
belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 264 seconds]
dos1 has quit [Ping timeout: 248 seconds]
cockroach has quit [Quit: leaving]
diejuse has quit [Quit: Leaving.]
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 264 seconds]
pagurus has quit [Ping timeout: 252 seconds]
DocScrutinizer has joined #maemo-leste
joerg is now known as Guest226
DocScrutinizer is now known as joerg
Daanct12 has joined #maemo-leste
Daaanct12 has quit [Ping timeout: 264 seconds]
<tmlind>
mighty: i'd use the known working android mux setting, not sure what the difference. see also the gpio-hog for msecure-hog in arch/arm/boot/dts/omap5-board-common.dtsi, maybe something similar works for you too
<tmlind>
mighty: i think you just want to keep msecure high for twl access, so muxing it into gpio mode and using a gpio hog should do it
<freemangordon>
Wizzup: nice, just LMK why it doesn't work through the wizard when it comes to it
<freemangordon>
Wizzup: not sure, I think it is only eapd that's implemented, but won't argue much
<Wizzup>
freemangordon: wpa supplicant does everything on the wireless side, I can't imagine what wlancond did
<Wizzup>
(not arguing btw :p)
<freemangordon>
because, from what I understand, wlancond implements what icd2 plugin requires in terms of caching and stuff like hidden wlan and wps and adhoc
<freemangordon>
IIUC it is a kind of a proxy
<Wizzup>
wpa_supplicant caches Bss info
<Wizzup>
I don't know much about icd2 caching though
<Wizzup>
but wpa_supplicant is also a 'proxy' in many ways, you can do some of the same things with a lower level interface, but then you rely on (sometimes) buggy kernel drivers, etc
<freemangordon>
as I am going to implement it as soon as I know how :)
<Wizzup>
See fi.w1.wpa_supplicant1.Interface.Scan
<Wizzup>
SSIDsaayArray of SSIDs to scan for (applies only if scan type is active)No
<freemangordon>
but, you said this shall be called after 'disconnect', no?
<Wizzup>
It might interact with our icd2 module, but I can maybe work around that
<freemangordon>
exactly
<Wizzup>
not in that way
<freemangordon>
this is my point about wlancond acting as a proxy
<Wizzup>
the disconnect is not relevant, the icd2 module can handle that
<Wizzup>
I am providing you the replacement dbus code, I would write the easy wlan stuff differently I think
<Wizzup>
I think all you need it already in the IAP data that gets created from icd2
<freemangordon>
ok, lets not discuss that now as I have to go. Will think about it a bit more, please, you do too.
<Wizzup>
ok
<freemangordon>
bbl
^-^hi has joined #maemo-leste
<Wizzup>
hi
* ^-^hi
<^-^hi>
Wizzup: if you have implemented and tested the battery use improvements on n900, why don't you incorporate them?
<Wizzup>
^-^hi: sorry, what exactly are you talking about? Got a link/reference?
<sicelo>
I suppose he means the tweet about N900 doing off mode
<Wizzup>
sicelo: I realised, but I'd like context :)
<^-^hi>
you sent a tweet somewhere saying that n900 battery now lasts much longer. i come every few months and ask if the battery use improvements are already included and hear no.
<Wizzup>
^-^hi: I see, ok
<^-^hi>
is it included already?
<Wizzup>
^-^hi: so the answer is that it's not just a question of 'merging in some code', it's a decent amount of research work, let me explain
<Wizzup>
Our current Linux on the N900 is 5.1 with some patches, some of our own, some powervr patches, for omapfb and powervr. The tweet was plain mainline (5.8 or so?) with no maemo leste loaded - minimal userspace, showing that it is possible to enter those idle/off modes
<Wizzup>
What needs to be done to get it all in place and merged is: (1) move from kernel 5.1 to a newer/latest kernel - this is being blocked by some of us not knowing how to port to 5.2 and forward due to some kernel change
<Wizzup>
(2) is then loading up minimal userspace, hitting off mode with the powervr driver loaded but not used, and then booting maemo bits one at a time, and see what can prevent OFF mode from being hit
<Wizzup>
(3) making n900 on maemo play nice with off mode once (1) and (2) are done
<Wizzup>
We're not doing (1) at the moment because we want to switch to another, newer, powervr userspace + kernel driver so that we're using the same one on all devices, but that driver needs some more work to get X11 going with hildon-desktop
<Wizzup>
If we can get the new driver working, we can skip (1) outright, and since we want to do that anyway, it's better to aim for the newer driver rather than having to redo the work we just did to begin with
<Wizzup>
A shortcut to start on (2) and (3) is to load the latest kernel without powervr on the n900 and start working on OFF mode, without 3d acceleration, this can be useful, but it won't result in a useful phone until it's once again equipped with the 3d driver
<Wizzup>
One other shortcut is that maybe it is possible to try to hit off mode on kernel 5.1, but if we can't, we cannot report bugs since everyone (rightfully so) will tell us: does it work with latest kernel? as first question
<Wizzup>
Hope this clarifies it a bit, please let me know if you have more questions
<^-^hi>
any way to run new software on fremantle without compiling everything and its dependencies?
* ^-^hi
's English is degrading
<Wizzup>
If you fremantle you mean the ancient kernel and ancient userspace, then likely only chroot will be easy, but even that will likely have trouble with really old kernel
<sicelo>
Not really enough useful ways for that.
<^-^hi>
didn't linux have a policy of "don't break userspace"?
<Wizzup>
Maybe if you also go for arm eabi, and use the space x11 driver ported to latest xorg server and using eabi in the chroot, you could get something going, but that by itself is probably more effort than the work required to get decent PM on leste
<sicelo>
^-^hi: if you want to help with the off mode issue (and get some use out of the device in the meantime), maybe look at running plain devuan with i3 or similar light UI (no 3d required). Should make it easier to play with kernel, and still use device to some extent
<^-^hi>
i know C but don't know anything about kernel and such stuff
<sicelo>
If you know C, you're already halfway :-)
<sicelo>
I don't know C, but already 'fixed' something for the LED driver ... so you should do even better. Also, the PM stuff doesn't necessarily need you to do actual dev. Testing, reporting, testing some more, etc. is still a good start
<Wizzup>
sicelo: I'm not sure if that helps that much (with i3), it's mostly kernel stuff really
<Wizzup>
Don't mean to discourage, but I think if folks want to contribute without the powervr stuff, then picking the last path I outlined is helpful: latest mainline linux without powervr, and making things play nice then
<Wizzup>
you could do that with i3, but might as well do it with maemo tbh
<Wizzup>
freemangordon: seems like I already implemented the wlancond caps in icd2 since it's part of the api :)
<Wizzup>
freemangordon: and src/wlan.c's wlan_search_network_added_cb uses network_attrs = wpaicd_bssinfo_to_network_attrs(info);
<Wizzup>
so at least icd2 is already perfectly aware of this
<Wizzup>
so if you can get access to the IAP you need to connect to for the hidden wlan, you can already know the capabilities and the entire scan is redundant
<Wizzup>
parazyd: various things there do depend on gtk2 patches like the filter_event
<Wizzup>
in GtkIMContextClass
<Wizzup>
debian/patches/hildonize-gtk-imcontext.diff is particularly relevant
<Wizzup>
parazyd: so this would go into our gtk3 patch set I think
<Wizzup>
The hildongtkinputmodes we can maybe base on the GtkInputPurpose enums as listed above
<Wizzup>
but the other stuff requires more significant changes
<Wizzup>
We can look at dropping it maybe, but it seems quite relevant
inky has quit [Ping timeout: 264 seconds]
_inky has joined #maemo-leste
inky_ has joined #maemo-leste
_inky has quit [Read error: No route to host]
inky has joined #maemo-leste
dos1 has joined #maemo-leste
<parazyd>
ftr
<parazyd>
15:43 <parazyd> I'm not sure what exactly hildonize-im-context.patch really does, but if the idea was: "hide the input method on focus change or on windowing system state change", then it should not be necessary
<freemangordon>
Wizzup: I'll debug to see what exactly data we have in connui dialogs
<Wizzup>
freemangordon: ok
<Wizzup>
parazyd: I don't think it was about focus tracking
<Wizzup>
parazyd: it is a way to force-raise the IM it looks like
inky_ has quit [Read error: No route to host]
_inky has joined #maemo-leste
<freemangordon>
Wizzup: it seems we have some caps, whether they are correct is another story
<Wizzup>
freemangordon: they should be I think
<Wizzup>
freemangordon: if they are not please let me know
<Wizzup>
freemangordon: we render them in the UI based on those caps (the lock, etc)
<freemangordon>
ok, will just comment trhe code that scans and will se how it will pan out
<freemangordon>
*the
<Wizzup>
ok, I need to push some code from my side as well but I don't have the control interface part yet
<freemangordon>
Wizzup: hmm, won;t work, because you may have more than one hidden wifi around, and in the menu only one entry seems to be shown
<freemangordon>
which is the case here
<Wizzup>
freemangordon: I don't know how that can ever be made sensible UX tbh
<freemangordon>
I guess that's why Nokia did it like that - no matter how many hidden nets you have around, only one entry is shown. Once you click it, you enter ssid and caps for that ssid are retreived
<freemangordon>
or, we can group in the UI by caps
inky has quit [Ping timeout: 264 seconds]
<freemangordon>
hmm, no, not a good idea
[TheBug] has quit [Ping timeout: 252 seconds]
<Wizzup>
can't people use the cpa?
<Wizzup>
(serious question)
<freemangordon>
Wizzup: the more I think, the more I agree with how nokia did implement it
<Wizzup>
it seems to be a better way to implement it
<freemangordon>
status menu is way more intuitive
[TheBug] has joined #maemo-leste
<freemangordon>
also, we know how to do it, well, lets do it then
_inky has quit [Ping timeout: 244 seconds]
<freemangordon>
Wizzup: you may expose dbus interface from wpa plugin to be called by the dialog to get the caps
<Wizzup>
freemangordon: I need to check if wpa_supplicant can scan for ssid without proving key_mgmt
<freemangordon>
not sure what you mean, but ok
<Wizzup>
but if it does, I suggest that you use icd2 dbus api to just issue another scan and then wait
<Wizzup>
you can add a 'temporary' IAP and scan
<Wizzup>
no need for more dbus apis iiuc
<freemangordon>
I think at that point we already have temporary iap
<freemangordon>
we just need its caps so UI to know which dialogs to show
<Wizzup>
then just issue another icd2 scan, as when I push my code the thing should show up upon rescan if it's present as temporary
<freemangordon>
hidden wlans are not shown unless you add them
<freemangordon>
you == wpa plugin
<Wizzup>
freemangordon: yes, the new code does that (local)
<Wizzup>
I already connected to hidden wlan at home
<Wizzup>
and it shows up in the scan dialog
<Wizzup>
I just need to add the control interface and send "DISCONNECT" at the right time
<freemangordon>
but how to issue another scan from the UI?
<freemangordon>
I don't think that is going to work, not reliably
<Wizzup>
How does it do the first one? ;)
<freemangordon>
doesn;t matter, we are already in a different state
<freemangordon>
also, I am not sure icd2 will reissue a scan before the cache is expired
<freemangordon>
so that would mean that we will have cache expiry timeout+scan time for the new entry to appear
<freemangordon>
more that 30 seconds, which is very bad UX imo
<freemangordon>
not to say that you have to now that you have to search for the SSID you have just entered in the list and click it
<freemangordon>
*know
<Wizzup>
a new ssid showing up doesn't matter to the cache
<Wizzup>
afaik
<freemangordon>
afaik, no new scan to the plugin is issued while the cache is still valid
<freemangordon>
so plugin won;t have the chance to update the list with that temporary iap, if we assume it is created
<Wizzup>
freemangordon: maybe allow cache to be invalidated rather than new api?
<freemangordon>
Wizzup: why you don't like the idea?
<freemangordon>
also, how exactly is UI supposed to invalidate icd2 cache?
<Wizzup>
freemangordon: I am not sure if I don't like it, but adding more interfaces when we already have interfaces to (1) add a network to that is is scanned (2) issue another scan seems unnecessary
inky has joined #maemo-leste
<Wizzup>
s/to that is/so that it/
<freemangordon>
but, we don;t really want another full scan, no?
<freemangordon>
we just want details for a single SSID
<Wizzup>
that's still a scan
<freemangordon>
yes, but not full
<freemangordon>
btw, what is the problem to call wpa_supplicant?
<freemangordon>
do you think it will connect?
<freemangordon>
also, how it is going to connect without a key?
<Wizzup>
I don't think there is one, as long as the libicd-network-wpasupplicant's callbacks for scan results do not confuse icd2
<Wizzup>
freemangordon: wait, why are we talking about connect?
<Wizzup>
freemangordon: oh, sorry
<freemangordon>
because you said (at least that's what I understood) is that issuing scan for ssid will also connect it
<Wizzup>
freemangordon: no, it should be fine to call wpa_supplicant
<Wizzup>
freemangordon: yes, but I found a workaround for that (with meridions help)
<freemangordon>
unless you call 'disconnect'
<freemangordon>
hmm?
<Wizzup>
I can try to describe it here, but if you didn't, can you read my post on the gh issue first?
<Wizzup>
so the tl;dr is we can prevent wpa_supplicant for from acting on it's own by:
<Wizzup>
(1) if we are not connected to any APs, call 'DISCONNECT' on the ctrl interface
<Wizzup>
(2) if we are connected to something else, we don't need to do anything
<Wizzup>
If we are not connected, calling 'DISCONNECT' just has the effect of setting the 'reassociate' variable in wpa_supplicant to 0 which means it will *not* try to connect on its own
<Wizzup>
so I think it's fine if the easy-wlan calls out to wpa_supplicant over dbus to do a scan of a single ssid, I will just need to teach the libicd-network-wpasupplicant code to deal properly with scans it did not initiate
<freemangordon>
and that's why we need a separate daemon to control that, because UI has no clue (or at least should not care) whether we are connected or not
<Wizzup>
freemangordon: easy-wlan will not need to issue 'DISCONNECT'
<Wizzup>
libicd-network-wpasupplicant will take care of all of that
<freemangordon>
sure? ok, then it is fine
<Wizzup>
yes
<freemangordon>
I have no issue to call wpa_supplicant from the UI
<Wizzup>
ok, then maybe that's the best solution
<Wizzup>
Should we split out wpaicd to some shared lib?
<freemangordon>
yes, this is what code currently does, albeit it calls wlancond and not wpa_supplicant :)
<Wizzup>
I have some more local code, but I'm currently at my parents place and already started on the wine, so I'm worried that if work too much on it now I'll create more work for myself tomorrow :p
<freemangordon>
no, connui has pretty much very good dbus support already
<Wizzup>
ok
<freemangordon>
Wizzup: take your time, I'll try to replace wlancond with wpa_supplicant calls
<freemangordon>
BTE, UI runs as user, is that a problem in regards to dbus security?
<freemangordon>
*BTW
<Wizzup>
I would have to check, good question
<Wizzup>
wpa_supplicant runs on system I think
<freemangordon>
also, tomorrow I'll be MIA the whole day, so you'll have plenty of time to implement whatever changes are needed in the plugin :p
<freemangordon>
maybe we shall check the dbus service
<Wizzup>
ok
<Wizzup>
I know what I need to implement from my side, and tomorrow morning I'll be home with the hidden ap again
<freemangordon>
great
<Wizzup>
I'll push all the code to make auto connect and configured-via-cpa to work
<freemangordon>
I'll try to finish UI part today
<Wizzup>
and then we can test the other code when you get back
<freemangordon>
mhm
<freemangordon>
deal
<freemangordon>
Wizzup: one more thing - which interface I shall use to issue the scan?
<Wizzup>
freemangordon: wlan0 currently, that's also the assumption in libicd-network-wpasupplicant
<Wizzup>
I imagine that eventually we want to get rid of that, but for now ... eh
<freemangordon>
I meant dbus, I guess it is fi.w1.wpa_supplicant1.Interface