IRC log for #maemo-ssu on 20121016

00:07.50*** join/#maemo-ssu andre__ (~andre@wikimedia/aklapper)
00:24.42*** join/#maemo-ssu gri (~gri@muhkuh.net)
02:32.21*** join/#maemo-ssu M13 (~Miranda@83.149.34.203)
02:41.22*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
03:04.22*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
05:49.58*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
06:20.25*** join/#maemo-ssu luf (luf@nat/ibm/x-ykmhllizgkxziuep)
06:50.46*** join/#maemo-ssu Jade (~jade@modemcable021.180-203-24.mc.videotron.ca)
06:50.46*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
07:20.29*** join/#maemo-ssu fw190 (~fw190@user-31-174-75-197.play-internet.pl)
09:23.52*** join/#maemo-ssu iDont (~iDont@j138215.upc-j.chello.nl)
09:33.47*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
09:59.56*** join/#maemo-ssu iDont (~iDont@j138215.upc-j.chello.nl)
10:00.10*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
11:08.14*** join/#maemo-ssu FlameReaper (~assassin@203.82.92.94)
11:33.03*** join/#maemo-ssu guly (~why@shivaya.guly.org)
12:10.53*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-gylqhbdkjlxwzkjf)
12:23.51*** join/#maemo-ssu xmlich02 (~imlich@2001:67c:1220:80c:0:d0:186:fdfd)
12:34.21*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
12:44.10freemangordonPali: ping
12:55.56Palifreemangordon, pong
13:04.24*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
13:06.48*** join/#maemo-ssu fw190 (~fw190@user-188-33-22-221.play-internet.pl)
13:42.10freemangordonPali: CAL lib is ready, now what?
13:42.16freemangordonboth read/write
13:43.53freemangordonPali: https://gitorious.org/cal/cal
13:45.10Palifreemangordon, ok
13:55.02freemangordonPali: feel free to package it :D
13:55.25Palifreemangordon, ok :-)
13:55.29freemangordon(if needed)
13:56.07Palinow I'm trying to solve this problem, but without luck :-( https://www.spoj.pl/problems/NETADMIN/
13:56.14PaliI will look at cal later...
13:56.58luffreemangordon: how low is the bluez-4.99 on your todo? I'm working on stabilization of bluez as tons of memleaks and wrong pointer operations fixed in git ....
14:14.11merlin1991btw luf how ready is obdex by now?
14:14.26merlin1991in other words should I package the current git for the new -testing?
14:15.12lufmerlin1991: I think you can. No bug report and several fixes.
14:16.00lufmerlin1991: Please don't forgot to include also librtcom-eventlogger1-async (fixed dependency).
14:20.56lufmerlin1991: when do you want to realease the new -testing?
14:40.25*** join/#maemo-ssu FlameReaper (~assassin@175.140.19.140)
14:43.15freemangordonluf: hmm, is bluez ready for prime-time? I mean is it stabel enough so I can put it on my primary device?
14:43.40freemangordonas I can't think on other way to test it
14:46.02luffreemangordon: Hmmm it should be ok. But better to wait after I finish with bugfixing (I'm at number around 90 now).
14:48.07freemangordonluf: ok. As I actually use BT on my everyday n900 often (HF connected all day long) I will wait you to gimme a green light
14:49.21luffreemangordon: Keep in mind that even green light should makes you a trouble ;)
15:13.37merlin1991luf: I suppose somewhere around next week
15:14.01merlin1991we've reach critical mass regarding updated packages and it's about time stuff goes into the wild again :)
15:20.12lufmerlin1991: good :)
15:42.40*** join/#maemo-ssu CepiPerez (~Matias_Pe@186.22.11.243)
15:42.43*** join/#maemo-ssu NIN101 (~NIN@p5DD28A28.dip0.t-ipconnect.de)
16:38.13keriowait, bug 90? D:
16:38.14povbotBug https://bugs.maemo.org/90 Make hildon-widget macro names to use GLib standard
16:38.17kerioi'm running a buggy bluez? D:
16:38.24keriono, you silly povbot, i'm talking about bluez
16:43.53merlin1991kerio: nope.jpg
16:44.08merlin1991er well yes if you installed it by hand
16:44.12merlin1991otherwise no
16:45.24keriomerlin1991: of course i did
16:45.29keriothe bluez *you* ship is old!
17:17.57*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
17:19.40lufkerio: unfortunately yes. 90 is now the count of patches for bluez-4.99.
17:20.06kerioluf: i trusted you!
17:20.10kerioalso gimme a new binary plskthx
17:20.22lufkerio: no new binary yet.
17:20.37keriobut i want a binary D:
17:20.54lufkerio: :D Yes I see
17:34.22*** join/#maemo-ssu Woody14619a (~Woody@66-162-186-66.static.twtelecom.net)
17:34.22*** join/#maemo-ssu Woody14619a (~Woody@Maemo/Community/council/Woody14619)
17:44.02*** join/#maemo-ssu Woody14619 (~Woody@66-162-186-66.static.twtelecom.net)
17:44.02*** join/#maemo-ssu Woody14619 (~Woody@Maemo/Community/council/Woody14619)
17:46.43*** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se)
17:49.19freemangordonluf: I am well aware of that, but I prefer to test *after* there are no known regressions :P
17:50.26keriofreemangordon: pff, coward
17:50.48kerioluf: to be fair i had to restart bluetoothd in a couple of occasions
17:50.52kerioall related to A2DP in weird conditions
17:51.02keriolike A2DP during wifi monitor mode
18:05.19luffreemangordon: someone has to find the regressions first ;)
18:06.50lufkerio: There are several patches for A2DP :)
18:07.18kerioyay
18:26.54*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
18:31.19*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
18:43.08keriofeature request: fix /bin/login so it doesn't require the login shell to be listed in /etc/shells
18:45.40*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
19:25.07*** join/#maemo-ssu _rd (~rd@p57B48337.dip0.t-ipconnect.de)
19:38.09lufkerio: WTF? I vote againist this "fix"
19:40.33keriowhy?
20:05.09lufBecause it's nice unix like :) And it's wasting of time to remove such thing. You can add you favorite shell to the file.
20:15.17*** join/#maemo-ssu chainsawbike (~chainsawb@unaffiliated/chainsawbike)
20:28.14DocScrutinizer05luf: cssu-testing is not meant for THAT type of testing. Finding regressions is a process devels shall *finish* with in their local testbed, before a package goes to cssu-testing. The tesing in CSSU is meant in a sense of verification, not as in development
20:29.26DocScrutinizer05re ((<luf> freemangordon: someone has to find the regressions first ;) ))
20:31.52lufDocScrutinizer05: I didn't talk about cssu-testing ...
20:33.27lufDocScrutinizer05: If I didn't miss something we (kerio, me and free) talk about bluez-4.99. And I don
20:33.38DocScrutinizer05ok
20:33.40luf... I don't propose bluez-4.99 for cssu.
20:33.56DocScrutinizer05I might have gotten sth wrong
20:33.59kerioi propose bluez-4.99 for DocScrutinizer
20:35.02lufkerio: Be patient. It's very time consuming to go through all bluez patches since March.
20:35.20keriocan't you grab the latest upstream?
20:35.45lufI don't think so.
20:36.00lufAnd I don't want.
20:36.07*** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua)
20:37.15keriomaybe has too much faith in the upstream
20:37.37lufkerio: There is removed unix socket and alsa support and it's not tested in any well-known linux distros.
20:37.55lufAt least in test env.
20:38.06DocScrutinizer05it's a common misconception that upstream was suitable for embedded
20:38.36kerioDocScrutinizer05: the n900 kinda blurs the line between embedded and desktop though
20:38.38*** join/#maemo-ssu MrPingu (~MrPingu@86.92.226.97)
20:38.45DocScrutinizer05not really
20:39.04DocScrutinizer05the hw clearly is defined by all the known embedded properties
20:39.26keriowhich properties?
20:40.02DocScrutinizer05irq event driven, no polling, speed to idle, zeroclock, proprietary "peripherals", etc...
20:40.32keriobut apart for the proprietary peripherals, those would be good things on a desktop, too
20:41.12DocScrutinizer05sure, but "desktop" devels are largely ignorant to the change in thinking that introduces
20:41.50DocScrutinizer05and it already hurts mer
20:42.13DocScrutinizer05with their sensorfw evidently not designed according to those rules
20:43.23*** join/#maemo-ssu ZogG (~zoggrules@bzq-79-177-195-89.red.bezeqint.net)
20:43.24*** join/#maemo-ssu ZogG (~zoggrules@funtoo/user/ZogG)
20:43.39keriowhat's sensorfw?
20:43.57DocScrutinizer05the middleware between sensors and apps
20:44.13DocScrutinizer05replacement for stuff like mce, liblocation etc
20:45.19DocScrutinizer05and it has no proper concept for irq event driven processing
20:45.51DocScrutinizer05at least last time I checked
20:46.25ShadowJKThe first I heard of zeroclock and race to idle was actually in connection with intel's lesswatts.org project :)
20:46.35DocScrutinizer05it's like "app -[poll]->sensorfw-[poll]->peripheral
20:46.56DocScrutinizer05"
20:48.55kerioDocScrutinizer05: hey, at least it's not a busyloop!
20:49.12DocScrutinizer05ShadowJK: yeah, intel is aware of those concepts, but not many of the so called "kernel hackers" contributing to mainstream are. That's why basically every embedded device is using a private fork of kernel and lowlevel system libs
20:50.20*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
21:06.27DocScrutinizer05intel's lesswatts initiative been originated from poor battery runtime in laptops, so basically more close to embedded at large, than to 'classic' UNIX which not even had concepts for suspend-to-ram or intermittant network connectivity
21:40.03*** join/#maemo-ssu MrPingu (~MrPingu@86.92.226.97)
22:12.53*** join/#maemo-ssu jon_y (~enforcer@175.144.235.97)
22:49.23*** join/#maemo-ssu Woody14619 (~Woody@2620:4:4000:1:4547:ec61:72:7831)
22:49.23*** join/#maemo-ssu Woody14619 (~Woody@Maemo/Community/council/Woody14619)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.