**** BEGIN LOGGING AT Tue Sep 07 02:59:57 2010
Sep 07 07:15:17 <daniele_athome> morning
Sep 07 10:08:38 <daniele_athome> what about a maintainer program?
Sep 07 10:08:54 <daniele_athome> so anyone maintaing a package in shr (such as me) can bump the version by himself
Sep 07 10:09:07 <daniele_athome> of course with previous permission, e.g. by login token
Sep 07 10:09:31 <daniele_athome> bitbake recipe update, and so on...
Sep 07 10:09:54 <daniele_athome> it can be done with a simple web interface in the buildhost
Sep 07 10:27:42 <mickey|office> morning folks
Sep 07 10:41:23 <vanous> morning....morning? :)
Sep 07 10:54:06 <daniele_athome> hi vanous 
Sep 07 10:55:47 <vanous> daniele_athome: hi
Sep 07 11:02:03 <CIA-59> freesmartphone.org: 03mickey 07cornucopia * r31024b0a5b86 10/fsotdld/src/plugins/provider_location_freegeoip/plugin.vala: fsotdld: provider_location_freegeoip: use full keynames
Sep 07 11:02:06 <CIA-59> freesmartphone.org: 03mickey 07cornucopia * r50f2e5df2e72 10/fsotdld/src/plugins/provider_gps_nmea/plugin.vala: fsotdld: provider_gps_nmea: use full keynames
Sep 07 11:06:02 <vanous> mickey|office: are there changes coming regarding to the gps handling in fso? (gypsy) will apps require updating?  
Sep 07 11:07:05 <mickey|office> vanous: good question. it depends on whether developers are going to follow my API or want to insist on gpsd
Sep 07 11:07:16 <mickey|office> FSO2 will have support for two APIs
Sep 07 11:07:19 <mickey|office> a native FSO-location API
Sep 07 11:07:22 <mickey|office> and gspd
Sep 07 11:07:31 <mickey|office> gypsy will most likely not appear
Sep 07 11:07:31 <vanous> ok
Sep 07 11:08:04 <vanous> i like the gypsy signalling on bearing/position changes, rather then polling myself...
Sep 07 11:09:57 <vanous> but of course maintaining only one code for freerunner and regular debian would be easier... 
Sep 07 11:10:07 <vanous> i mean in user apps
Sep 07 11:10:22 * vanous means his app, therefore the debian ref. :)
Sep 07 11:11:21 <mickey|office> sure thing
Sep 07 11:11:33 <mickey|office> the DBus API will support location updates with signals first
Sep 07 11:11:36 <mickey|office> it already does, btw.
Sep 07 11:11:54 <mickey|office> eventually i might propose an agent model rather than sending so many signals
Sep 07 11:16:24 <DocScrutinizer> lo mickey|office 
Sep 07 11:16:52 <mickey|office> hey DocScrutinizer! how are things?=
Sep 07 11:16:59 <DocScrutinizer> :-/
Sep 07 11:17:09 <DocScrutinizer> DHL are **MORONS**
Sep 07 11:17:10 <mickey|office> that doesn't sound good, what'sup?
Sep 07 11:17:29 <DocScrutinizer> sending things to Russia they don't get their own shit sorted
Sep 07 11:17:39 <mickey|office> grrr
Sep 07 11:17:51 <mickey|office> PaulF still missing his package? :/
Sep 07 11:18:07 <lindi-> mickey|office: hey, did you look at my wishlist bug for gpsd?
Sep 07 11:18:10 <DocScrutinizer> paul's package is on "clearance delay" since Friday
Sep 07 11:18:46 <DocScrutinizer> today Henrietta tells Paul that DHL needs tax number of addressee company
Sep 07 11:19:12 <DocScrutinizer> as if DHL couldn't tell henrietta or even paul in advance, as both asked for shipping details
Sep 07 11:19:42 <mickey|office> fun
Sep 07 11:19:51 <mickey|office> lindi-: no, do you have a link handy?
Sep 07 11:22:54 <lindi-> mickey|office: https://developer.berlios.de/bugs/?func=detailbug&bug_id=17431&group_id=2116
Sep 07 11:22:59 <DocScrutinizer> mickey|office: any API specs yet for FSO location service?
Sep 07 11:23:08 <lindi-> mickey|office: I think this would benefit both non-fso and fso users
Sep 07 11:23:48 <DocScrutinizer> mickey|office: got some 20 lines flashing up in my head in a matter of a second
Sep 07 11:24:44 <DocScrutinizer> §1: strictly differential
Sep 07 11:24:56 <mickey|office> DocScrutinizer: atm. only org.freesmartphone.Location.PositionUpdate( a{sv} ) and org.freesmartphone.Location.GetPosition() -> a{sv}. Containing information depending on the location providers' capabilities. Eventually you will be able to register for location updates with a requested accuracy
Sep 07 11:25:04 <GNUtoo|laptop> hi mickey|office 
Sep 07 11:25:08 <mickey|office> differential? 
Sep 07 11:25:12 <mickey|office> hi GNUtoo|laptop 
Sep 07 11:25:14 <mickey|office> please explain :)
Sep 07 11:25:18 <GNUtoo|laptop> btw are you really sure I would be more usefull on palm-pre than n900?
Sep 07 11:26:07 <GNUtoo|laptop> mickey|office, the explain was for me?
Sep 07 11:26:23 <mickey|office> GNUtoo|laptop: i can't be really sure, no one can :) at the end of the day, it depends on your likings, really. IMO both have roughly the same status, with their own dark spots here and there
Sep 07 11:26:36 <GNUtoo|laptop> ok
Sep 07 11:26:50 <GNUtoo|laptop> basically maybe tomorrow I'l have some time to buy it,not sure
Sep 07 11:27:14 <GNUtoo|laptop> I prefer n900
Sep 07 11:27:23 <GNUtoo|laptop> hardware is better
Sep 07 11:27:26 <mickey|office> hmm
Sep 07 11:27:29 <mickey|office> well
Sep 07 11:27:30 <GNUtoo|laptop> that's the issue
Sep 07 11:27:31 <mickey|office> :)
Sep 07 11:27:37 * mickey|office prefers the Pre
Sep 07 11:27:44 <mickey|office> especially now that i have an n900 to compare with
Sep 07 11:27:47 <DocScrutinizer> register_for_location_update input_hint=(lon,lat) input_service_type=[list_of_allowed_services] input_granularity=min_delta_for_new_update
Sep 07 11:27:49 <GNUtoo|laptop> so in the balance I've beeing more usefull or getting better hardware
Sep 07 11:28:00 <GNUtoo|laptop> ah?
Sep 07 11:28:04 <GNUtoo|laptop> why ?
Sep 07 11:28:21 <mickey|office> DocScrutinizer: go ahead, i'm listening.
Sep 07 11:28:49 <mickey|office> GNUtoo|laptop: formfactor, touchscreen.
Sep 07 11:28:59 <GNUtoo|laptop> touchscreen?
Sep 07 11:29:19 <mickey|office> GNUtoo|laptop: yes, i have become a major supporter of capacitive touchscreen technology now.
Sep 07 11:29:29 <GNUtoo|laptop> ok
Sep 07 11:29:31 <mickey|office> it's hard to go back to resistive for me
Sep 07 11:29:38 <GNUtoo|laptop> it's not capacitive on n900?
Sep 07 11:29:42 <mickey|office> nope
Sep 07 11:29:44 <GNUtoo|laptop> ok
Sep 07 11:29:48 <DocScrutinizer> query_avail_service_types return_list_of_services[(name, properties)]
Sep 07 11:29:49 <mickey|office> you have to apply much pressure
Sep 07 11:29:53 <GNUtoo|laptop> ok
Sep 07 11:30:01 <DocScrutinizer> err
Sep 07 11:30:12 <DocScrutinizer> query_avail_service_types return_list_of_services[(name, [properties])]
Sep 07 11:30:15 <GNUtoo|laptop> strange for a phone targeted towards general public
Sep 07 11:30:33 <GNUtoo|laptop> 2 things bother me in pre:
Sep 07 11:30:37 <GNUtoo|laptop> resolution
Sep 07 11:30:41 <GNUtoo|laptop> and capacity
Sep 07 11:31:03 <GNUtoo|laptop> (and keyboard orientation + keyboard itself)
Sep 07 11:31:30 <GNUtoo|laptop> and wifi is unknown
Sep 07 11:31:53 <GNUtoo|laptop> I don't see any unknowns yet in n900
Sep 07 11:32:11 <mickey|office> hmm, k
Sep 07 11:32:11 <GNUtoo|laptop> but capacitive screen is an argument
Sep 07 11:32:21 <mickey|office> for me everything is unknown unless i have seen it working with my code
Sep 07 11:32:28 <GNUtoo|laptop> ok lol
Sep 07 11:32:32 <GNUtoo|laptop> such as alsa
Sep 07 11:32:35 <GNUtoo|laptop> for htcdream
Sep 07 11:32:41 <mickey|office> yes
Sep 07 11:32:59 <DocScrutinizer> register_for_location_update implies start_location_reporting
Sep 07 11:33:05 <mickey|office> given our integration nightmares, i think that's the most safe approach. 
Sep 07 11:33:09 <GNUtoo|laptop> lol, I was already very suspicious but now I'm even more
Sep 07 11:33:10 <GNUtoo|laptop> ok
Sep 07 11:33:11 <DocScrutinizer> deregister_for_location_update implies stop_location_reporting
Sep 07 11:33:14 <mickey|office> features are unknown unless proven otherwise :)
Sep 07 11:33:36 <GNUtoo|laptop> basically before buying the htcdream I looked at the sources and made someone test playwav2
Sep 07 11:33:46 <GNUtoo|laptop> but I bet that's was not enough
Sep 07 11:34:30 <mickey|office> DocScrutinizer: sounds very powerful. it's along my lines of what I want to see (perhaps a bit more powerful than i would export)
Sep 07 11:34:45 <DocScrutinizer> start_location_reporting handle=handle_of_registercall ; sends instant notification of accuiring location in process with details, sends a first location update no matter which granularity was set
Sep 07 11:35:33 <DocScrutinizer> stop_location_reporting  temporaraily disables reporting and powers downs subsystems, while keeping 'handle' ntact
Sep 07 11:36:38 <mickey|office> GNUtoo|laptop: at the end of the day, noone can be sure what nightmares we will account. we should though start to concentrate on one or two models otherwise we'll be kept in the nothing-works-everywhere state forever
Sep 07 11:36:48 <mickey|office> s/account/encounter/
Sep 07 11:36:48 <apt> mickey|office meant: GNUtoo|laptop: at the end of the day, noone can be sure what nightmares we will encounter. we should though start to concentrate on one or two models otherwise we'll be kept in the nothing-works-everywhere state forever
Sep 07 11:37:05 <DocScrutinizer> depending on input_service_type=[list_of_allowed_services] input_granularity=min_delta_for_new_update, FSO can decide to watch celltower changes, accelerometers for movements, etc pp, and power down whenever due
Sep 07 11:38:22 <GNUtoo|laptop> indeed
Sep 07 11:38:29 <GNUtoo|laptop> lol
Sep 07 11:40:46 <DocScrutinizer> first (unconditional) report of a location (after register or start) will be sent not prior to accuracy of "fix" is better than requested granularity
Sep 07 11:43:04 <DocScrutinizer> don't forget about 4th dimension: speed
Sep 07 11:43:22 <DocScrutinizer> also 5th which is vector direction
Sep 07 11:43:34 <mickey|office> yep, course and speed is a must
Sep 07 11:43:56 <DocScrutinizer> so you could basically do things like "signal app when user doesn't keep walking north"
Sep 07 11:44:52 <DocScrutinizer> so hint is 3dim, while granularity and return_location are 5dim
Sep 07 11:46:21 <DocScrutinizer> nah, make hint also 5dim, for speed and direction the values are the initial reference from which delta is calculated modulo_granularity
Sep 07 11:51:02 <DocScrutinizer> add input_min_period=seconds_to_next_report to register_for_location_update, so by setting input_granularity to 0 you can get polling, with a period of aforementioned
Sep 07 11:55:11 <DocScrutinizer> register_for_location_update parameters can be updated for an already allocated registartion, by resending the call, but adding a handle!=0 which refers to prev registration, similar to the way it is done for start/stop_location_reporting
Sep 07 11:58:39 <DocScrutinizer> careful consideration is needed, which cases of update of register_for_location_update parameters actually imply a start_location_reporting so a new initial location report is sent unconditionally
Sep 07 12:00:00 <DocScrutinizer> aah, if I forgot to mention, start_location_reporting can be sent arbitrary time as often as needed, to trigger a new unconditional reporting
Sep 07 12:01:13 <DocScrutinizer> i.e. it's no error to send start_location_reporting twice without in between sending stop_location_reporting
Sep 07 12:02:55 <DocScrutinizer> if location update reply for first start_location_reporting isn't sent yet during 2nd start_location_reporting comes in, FSO clears the second request on sending reply for first one
Sep 07 12:04:15 <DocScrutinizer> notification about acquiring 'fix' and status however is sent immediately and instantly for every start_location_reporting 
Sep 07 12:08:14 <DocScrutinizer> (<mickey|office> you have to apply much pressure) for N900? Duh, it's the most sensitive r-ts I ever used. can literally operate at the touch of a feather, about one magnitude better than FR or OMNIA
Sep 07 12:11:56 <DocScrutinizer> and while the little bit of force needed to operate a r-ts may be a minor annoyance to some users (others really prefer that to accidental touch events, possibly even on approaching c-ts screen to 1 .. 0.5mm without real touch at all), otoh the missing precision and general incompatibility of c-ts with pointer devices, fingernails, etc is a real showstopper for several usecases
Sep 07 12:27:21 <DocScrutinizer> I'm really wondering what you both are talking about. For N900 there *IS* a working open source *linux* kernel, so things like ALSA are definitely _no_ unknowns, they are proven to work, on linux, with source available
Sep 07 12:30:14 <DocScrutinizer> well, if you think you need to pull off your very own anti-vendor port against a device with a kernel that even mainly gone upstream and continues to do, well that's your own hobby then. Just doesn't make sense to me
Sep 07 12:33:12 <lindi-> DocScrutinizer: are you advocating the use of maemo, meego or debian and discouraging the use of shr on n900? or is this about ophono?
Sep 07 12:34:37 <DocScrutinizer> lindi-: don't you think there's a difference between userland and core system?
Sep 07 12:35:16 <GNUtoo|laptop> DocScrutinizer, indeed my opinion is that there are no unknowns too
Sep 07 12:35:43 <GNUtoo|laptop> that's also why it looks so attractive
Sep 07 12:36:18 <GNUtoo|laptop> lindi-, he is telling that source is there so it's easier for us to port SHR
Sep 07 12:36:44 <lindi-> DocScrutinizer: I'm trying to ask you :)
Sep 07 12:36:44 <DocScrutinizer> there are meanwhile like 6 different distris running on N900, which 2 of them (at least) can do phonecalls now, and almost every other subsystem also is working in at least 2 
Sep 07 12:37:45 <DocScrutinizer> things like ALSA work ootb on maemo and most of the other ports
Sep 07 12:38:41 <GNUtoo|laptop> altough you need the free pulse plugin for phonecalls right?
Sep 07 12:38:41 <DocScrutinizer> there's just 2 closed areas yet, gfx 3d-accel and battery charging. Where charging has been mainly hacked by me
Sep 07 12:39:48 <GNUtoo|laptop> indeed it's so great
Sep 07 12:39:48 <GNUtoo|laptop> because 3d is optional
Sep 07 12:39:48 <GNUtoo|laptop> bootloader is proprietary too I bet
Sep 07 12:39:56 <DocScrutinizer> GNUtoo|laptop: I'm not exactly aware how meego did the calls, as they achieved in that just one week ago, but it's on the way and it works, without closed blobs or RE
Sep 07 12:40:10 <DocScrutinizer> yep, bootloader is proprietary
Sep 07 12:40:30 <DocScrutinizer> though open in a sense of being able to cainload e.g uBoot
Sep 07 12:40:34 <lindi-> DocScrutinizer: can you just answer my question please? ;)
Sep 07 12:40:34 <GNUtoo|laptop> but I heard that there was a free tool that can talk to it
Sep 07 12:40:35 <GNUtoo|laptop> 0xFFF
Sep 07 12:40:35 <GNUtoo|laptop> or something like that
Sep 07 12:41:38 <DocScrutinizer> that's correct, for flashing there's 0xFFFF, and probably meego project will come up with something eventually
Sep 07 12:41:47 <GNUtoo|laptop> ok
Sep 07 12:42:38 <DocScrutinizer> anyway though the flasher is closed source, it is still able to flash feee images
Sep 07 12:43:09 <GNUtoo|laptop> maybe it's time to respond to lindi- 's question
Sep 07 12:43:19 <DocScrutinizer> the toolchain to create a socalled fiasco image is documented
Sep 07 12:43:24 <GNUtoo|laptop> ok
Sep 07 12:44:05 <DocScrutinizer> lindi-: I don't see any question I haven't answered yet
Sep 07 12:44:21 <lindi-> < lindi-> DocScrutinizer: are you advocating the use of maemo, meego or debian and discouraging the use of shr on n900? or is this about ophono?
Sep 07 12:44:41 <DocScrutinizer> lindi-: don't you think there's a difference between userland and core system?
Sep 07 12:44:48 <lindi-> DocScrutinizer: that's a question :)
Sep 07 12:45:08 <DocScrutinizer> nevertheless it's my answer to your question
Sep 07 12:45:15 <lindi-> DocScrutinizer: and I'm not quite sure what you mean by that
Sep 07 12:45:26 <DocScrutinizer> as am I about your question
Sep 07 12:45:29 <lindi-> DocScrutinizer: are you advocating meego + fso for phone stuff?
Sep 07 12:45:36 <lindi-> (wildly guessing here)
Sep 07 12:45:41 <DocScrutinizer> why should I
Sep 07 12:45:43 <DocScrutinizer> ?
Sep 07 12:46:04 <lindi-> DocScrutinizer: I don't know, I was just trying to understand what you are trying to say
Sep 07 12:47:11 <lindi-> i mean, is this "anti-vendor port" shr? or fso?
Sep 07 12:47:27 <DocScrutinizer> I'm trying to say "it's all out there, you just need to cherrypick. There's no sense in claiming N900 has too many unknown areas, esp in comparing with adridiot and webos"
Sep 07 12:48:02 <DocScrutinizer> (is this shr or fso) it seems to me nobody is clear about that
Sep 07 12:48:52 <DocScrutinizer> just saying "I believe in my own code only" is a bit umm... weird in a FOSS context
Sep 07 12:49:05 <lindi-> DocScrutinizer: well surely from my perspective n900 has unknown areas :) I just heard that phone calls are possible today from you :P
Sep 07 12:49:44 <lindi-> n900 people should advertise these more here :)
Sep 07 12:52:33 <DocScrutinizer> why should they, as it seems nobody cares. Otherwise you'd /join #maemo /join #meego /join #meego-arm (the N900 'backport' proj for meego), /join #nitdroid , join n900debian qt-meego and whatnot. Why should anybody from there bother to report here?? o.O
Sep 07 12:53:20 <lindi-> DocScrutinizer: I did join #maemo but they keep recommending me non-free software
Sep 07 12:53:35 <DocScrutinizer> too bad
Sep 07 12:53:56 <DocScrutinizer> what particularly?
Sep 07 12:55:27 <GNUtoo|laptop> I bet the 3d stuff?
Sep 07 12:56:11 <DocScrutinizer> lindi-: btw I had an argue with luke-jr in #maemo yesterday, and all of a sudden I noticed certain identical details in mindset and way of posting arguments/statements between him and you - both being gentoo iirc
Sep 07 12:56:49 <misc> and both of them being human being too :p
Sep 07 12:56:54 <DocScrutinizer> you should ping him and ask about his progress to port gentoo to N900
Sep 07 12:57:04 <GNUtoo|laptop> lol about humain
Sep 07 12:57:15 <DocScrutinizer> for sure he won't suggest non free to you
Sep 07 12:57:50 <lindi-> DocScrutinizer: gentoo?
Sep 07 12:58:16 <lindi-> DocScrutinizer: I avoid gentoo because it makes it easy to accidentally use non-free software :)
Sep 07 12:58:21 <GNUtoo|laptop> I was suggested non-free 3d in #maemo last time I went there
Sep 07 12:58:29 <GNUtoo|laptop> indeed
Sep 07 12:58:30 <lindi-> DocScrutinizer: probably it was gentoo that they recommended yes :-)
Sep 07 12:58:43 <GNUtoo|laptop> lindi-, that's why I quited gentoo
Sep 07 12:59:26 <GNUtoo|laptop> lindi-, and with USE flag it's very easy
Sep 07 12:59:26 <GNUtoo|laptop> for instance one day I found out that a use flag bringed xv, the non free gimp-like program
Sep 07 12:59:37 <DocScrutinizer> sorry dudes, I don't follow, and I don't care
Sep 07 12:59:37 <GNUtoo|laptop> lol
Sep 07 13:00:26 <lindi-> GNUtoo|laptop: very easy? really?
Sep 07 13:00:42 <lindi-> GNUtoo|laptop: ah, you mean it's very easy to accidentally get non-free stuff. agreen
Sep 07 13:00:47 <lindi->  s/n$/d/
Sep 07 13:01:30 <misc> couldn't this be solved by using another use flag ?
Sep 07 13:01:34 <lindi-> DocScrutinizer: but yeah, I rejoined #maemo in the hope of getting some news on how to use n900 with free software
Sep 07 13:02:13 <lindi-> misc: the problem is that ebuild maintainers don't pay enough attention into making sure the information is correct. no amount of extra technical features really can solve that
Sep 07 13:02:41 <misc> lindi-: well, then all you have is to fill bug 
Sep 07 13:02:53 <lindi-> misc: I did
Sep 07 13:03:02 <lindi-> misc: it's severity was lowered to "trivial"
Sep 07 13:03:10 <lindi-> misc: in debian it'd be a release critical bug
Sep 07 13:03:15 <misc> lindi-: so next step is to use a knee breaking hammer to change the severity :)
Sep 07 13:03:16 <lindi-> s/it's/its/
Sep 07 13:03:19 <lindi-> but now away...
Sep 07 13:06:34 <gnutoo> ok fifirst attempt with package mask: failed because or stuff like perl license
Sep 07 13:06:34 <gnutoo> the ||
Sep 07 13:06:35 <gnutoo> then I used something with correct license gestion
Sep 07 13:06:36 <gnutoo> but then I found out that hmmm....all x11 packages were masked
Sep 07 13:06:36 <gnutoo> because it's under foo license 
Sep 07 13:10:42 <GNUtoo|laptop> lindi-, oops again disconnected by the vpn+wifi, I'm on 3g now, are you interested in gentoo details on why license filtering don't work under gentoo
Sep 07 13:10:51 <GNUtoo|laptop> s/don't work/isn't usable
Sep 07 13:11:04 <GNUtoo|laptop> I've a big problem
Sep 07 13:11:06 <GNUtoo|laptop> mickey|office, 
Sep 07 13:11:15 <GNUtoo|laptop> do you understand french
Sep 07 13:11:22 <GNUtoo|laptop> the sfr palm pre website says:
Sep 07 13:11:31 <GNUtoo|laptop> "Mobile utilisable exclusivement sur les réseaux GSM/GPRS/UMTS de SFR"
Sep 07 13:11:36 <GNUtoo|laptop> it seem so simlock to me
Sep 07 13:11:40 <GNUtoo|laptop> that's not possible for me
Sep 07 13:12:07 <GNUtoo|laptop> I've to check it out
Sep 07 13:16:48 <GNUtoo|laptop> hi, are there some french people that have a palm pre here?
Sep 07 13:16:59 <GNUtoo|laptop> maybe I should ask on webos-internals
Sep 07 13:18:57 <mickey|office> my french is not existing. i'd be surprised if there was a simlock, i don't think any operator has 'em for the pre, best bet is to ask on #webos-internals
Sep 07 13:19:42 <GNUtoo|laptop> ok thanks
Sep 07 13:20:18 <GNUtoo|laptop> <swisstomcat> i think the SFR phones are locked
Sep 07 13:21:31 <playya_> GNUtoo|laptop, i know that austrian people have some problems using the pre
Sep 07 13:21:34 <GNUtoo|laptop> ok
Sep 07 13:21:41 <playya_> ask jesusmccloud for details
Sep 07 13:21:46 <GNUtoo|laptop> playya_, wha's the issue?
Sep 07 13:21:56 <GNUtoo|laptop> something like CME error 100?
Sep 07 13:22:01 <GNUtoo|laptop> or CME error 30
Sep 07 13:22:08 <GNUtoo|laptop> the network equivalent I mean?
Sep 07 13:22:42 <GNUtoo|laptop> where can I find jesusmccloud
Sep 07 13:22:43 <GNUtoo|laptop> ?
Sep 07 13:22:49 <playya_> afair he had to use webos doctor to flash a patched image
Sep 07 13:23:07 <GNUtoo|laptop> ok
Sep 07 13:23:09 <playya_> ,seen jesusmccloud
Sep 07 13:23:18 <GNUtoo|laptop> my target countries are:
Sep 07 13:23:26 <GNUtoo|laptop> italy,france,belgium
Sep 07 13:23:38 <GNUtoo|laptop> and maybe USA 
Sep 07 13:24:35 <playya_> jesus should be here from time to time
Sep 07 13:37:50 <mickey|office> digitec sells it in Switzerland simlock free
Sep 07 13:39:16 <mickey|office> 	err... switzerland... let me check french
Sep 07 13:40:49 <mickey|office> "In France, SIM locks are not prohibited. However, the mobile operator must inform the consumer of the existence of a SIM lock. The subscriber has the right to request that the SIM lock be removed at any time. No later than 6 months prior to the conclusion of the contract, the mobile operator must "systematically and free of charge" provide the subscriber with a procedure to deactivate the SIM lock. Operators m
Sep 07 13:40:52 <mickey|office> ay charge a fee for removing the SIM lock prior to the 6-month deadline."
Sep 07 13:41:10 <misc> systematically == you need to call them 
Sep 07 13:41:10 <mickey|office> so... just ask :)
Sep 07 13:45:41 <lindi-> GNUtoo|laptop: I think the problem is just that they don't value free software that much. i am not sure if any technical improvement can help
Sep 07 13:46:08 <GNUtoo|laptop> indeed
Sep 07 13:46:10 <GNUtoo|laptop> that's the issue
Sep 07 13:46:19 <GNUtoo|laptop> I just wanted to show how bad it is
Sep 07 13:46:56 <GNUtoo|laptop> mickey|office, ok thanks a lot
Sep 07 13:47:35 <mickey|office> if it has a lock, it might be more sane to get someone to buy it from vodafone and set it to you
Sep 07 13:47:47 <mickey|office> s/set/send/
Sep 07 13:47:49 <apt> mickey|office meant: if it has a lock, it might be more sane to get someone to buy it from vodafone and send it to you
Sep 07 13:50:34 <GNUtoo|laptop> mickeyl, ok I wont't get a palm pre...it costs too much
Sep 07 13:50:37 <GNUtoo|laptop> 769E
Sep 07 13:50:51 <GNUtoo|laptop> in every SFR shop
Sep 07 13:51:00 <GNUtoo|laptop> on internet it's 429E 
Sep 07 13:53:18 <misc> *ouch*
Sep 07 13:54:55 <mickey|office> ok, that's bad. ebay?
Sep 07 13:55:07 <mickey|office> i'm sure people are selling new ones there as well
Sep 07 14:03:38 <GNUtoo|laptop> ok
Sep 07 14:03:49 <GNUtoo|laptop> n900 + ebay palm-pre
Sep 07 14:03:52 <GNUtoo|laptop> maybe ....
Sep 07 14:05:47 <mickey|office> yeah
Sep 07 14:10:48 <dos1> GNUtoo|laptop: with xim keyboard works well with GTK+ apps too :)
Sep 07 14:10:50 <dos1> thanks
Sep 07 14:12:15 <GNUtoo|laptop> nice
Sep 07 14:12:25 <GNUtoo|laptop> dos1, so what you have to do is:
Sep 07 14:12:36 <dos1> GNUtoo|laptop: http://patchwork.dev.bearstech.com/project/SHR/list/ - are those two patches for frameworkd-config-shr already commited?
Sep 07 14:12:41 <GNUtoo|laptop> create a /etc/profile.d/gtk-immodule.sh
Sep 07 14:13:08 <dos1> GNUtoo|laptop: already did that ;)
Sep 07 14:13:15 <GNUtoo|laptop> dos1, no, commit that in priority:
Sep 07 14:13:18 <dos1> though we need some sane way to include it in image
Sep 07 14:13:22 <GNUtoo|laptop> [Shr-Devel,1/2] frameworkd-config-shr: fix htcdream's config CLRF issue
Sep 07 14:13:30 <GNUtoo|laptop> dos1, look in:
Sep 07 14:13:40 <daniele_athome> dos1, hello
Sep 07 14:13:43 <GNUtoo|laptop> recipes/gtk+/gtk+_yourversion.bb
Sep 07 14:13:49 <dos1> daniele_athome: hi
Sep 07 14:13:49 <daniele_athome> <daniele_athome> what about a maintainer program?
Sep 07 14:13:50 <daniele_athome> <daniele_athome> so anyone maintaing a package in shr (such as me) can bump the version by himself
Sep 07 14:13:50 <daniele_athome> <daniele_athome> of course with previous permission, e.g. by login token
Sep 07 14:13:50 <daniele_athome> <daniele_athome> bitbake recipe update, and so on...
Sep 07 14:13:50 <daniele_athome> <daniele_athome> it can be done with a simple web interface in the buildhost
Sep 07 14:13:56 <daniele_athome> please read this dos1 :)
Sep 07 14:14:31 <dos1> daniele_athome: hmm... maybe on buildhost yes, but it won't be commited to OE then
Sep 07 14:14:41 <dos1> i don't think they allow automatic commits in their policy ;)
Sep 07 14:15:13 <dos1> but others should look at that, i don't even have OE rw access
Sep 07 14:15:24 <daniele_athome> dos1, ok buildhost is a first step, then SHR staff could review the commits and push it to OE
Sep 07 14:16:38 <daniele_athome> but this could be a very major step in making the shr guys work less hard
Sep 07 14:23:11 <CIA-59> SHR: 03GNUtoo 07shr-themes * r41871d1c920b 10/frameworkd/frameworkd-config-shr/htcdream/frameworkd.conf: frameworkd-config-shr: disable ogpsd in htcdream's frameworkd.conf
Sep 07 14:23:20 <CIA-59> SHR: 03GNUtoo 07shr-themes * rc094cf50154c 10/frameworkd/frameworkd-config-shr/htcdream/frameworkd.conf: frameworkd-config-shr: fix htcdream's config CLRF issue
Sep 07 14:38:24 <GNUtoo|laptop> thanks
Sep 07 14:38:38 <GNUtoo|laptop> dos1, how does someone get commit access to the config repos of SHR?
Sep 07 14:39:17 <dos1> GNUtoo|laptop: just send your ssh key to someone who can give you access ;)
Sep 07 14:39:23 <GNUtoo|laptop> ah ok
Sep 07 14:39:31 <dos1> GNUtoo|laptop: mrmoku for sure can, i think JaMa and TAsn too
Sep 07 14:39:34 <GNUtoo|laptop> ok
Sep 07 14:39:44 <GNUtoo|laptop> because it took a very long time to push theses patches
Sep 07 14:39:56 <GNUtoo|laptop> and for instance the ogpsd stuff could change
Sep 07 14:40:22 <GNUtoo|laptop> I mean I could have to re-enable it
Sep 07 14:40:31 <GNUtoo|laptop> after commiting its support in fso
Sep 07 14:40:55 <dos1> GNUtoo|laptop: well, you could ping me, i just notices those patches accidentally ;)
Sep 07 14:42:07 <dos1> GNUtoo|laptop: but with having direct access pushing changes is for sure much faster and easier
Sep 07 14:47:56 <GNUtoo|laptop> indeed
Sep 07 14:49:30 <GNUtoo|laptop> I'll go bye
Sep 07 15:39:57 <CIA-59> SHR: 03seba.dos1 07shr-settings * r36305a2602b5 10/shr_settings_modules/shr_firmware.py: [firmware] add new wizard module
Sep 07 15:42:02 <CIA-59> SHR: 03seba.dos1 07shr-wizard * r43e51663262d 10/python/shr-wizard.py: python: add firmware module to inform about non-free firmwares needed to use some devices
Sep 07 15:47:09 <dos1> GNUtoo|laptop: hey, could you post /proc/cpuinfo from HTC Dream?
Sep 07 15:47:35 <GNUtoo|laptop> yes
Sep 07 15:47:49 <GNUtoo|laptop> if you want to know it's trout
Sep 07 15:47:55 <GNUtoo|laptop> but I'll post the full thing
Sep 07 15:49:34 <dos1> GNUtoo|laptop: i need "Hardware" field
Sep 07 15:49:43 <GNUtoo|laptop> http://pastebin.com/YD03GXWW
Sep 07 15:49:52 <GNUtoo|laptop> as I said it's trout
Sep 07 15:50:07 <dos1> ok :)
Sep 07 15:51:03 <GNUtoo|laptop> dos1, what do you want to do with trout?
Sep 07 15:51:09 <CIA-59> SHR: 03seba.dos1 07shr-settings * r4308de8a1c67 10/shr_settings_modules/shr_firmware.py: firmware: display firmware module also on HTC Dream
Sep 07 15:51:16 <GNUtoo|laptop> ok nice
Sep 07 15:51:25 <dos1> ;)
Sep 07 15:51:27 <GNUtoo|laptop> thanks a lot
Sep 07 15:51:55 <dos1> GNUtoo|laptop: it's just informative page on shr-wizard
Sep 07 15:52:04 <GNUtoo|laptop> ok nice
Sep 07 16:09:09 <DocScrutinizer> ~seen mrmoku|away 
Sep 07 16:09:21 <apt> mrmoku|away is currently on #maemo #oe #meego #openmoko #openmoko-cdevel, last said: 'PaulF: I updated to current FSOREV yesterday and did quite a few calls since then... so far without any problems'.
Sep 07 17:43:01 <leviathan> hmm
Sep 07 17:43:03 <leviathan> nice
Sep 07 17:43:24 <leviathan> GNUtoo|laptop: can you please ask the tuxbrain guy
Sep 07 17:43:30 <leviathan> when the phone should arrive?
Sep 07 17:43:47 <GNUtoo|laptop> leviathan, he's tuxbrain in #qi-hardware
Sep 07 17:43:54 <leviathan> ahh, ok
Sep 07 17:43:55 <leviathan> :-)
Sep 07 17:43:57 <leviathan> thx
Sep 07 17:56:22 <CIA-59> freesmartphone.org: 03seba.dos1 07cornucopia * rb4b7a49743fc 10/fsodeviced/ (4 files in 3 dirs): fsodeviced: introduce proximity_n900 plugin
Sep 07 18:12:29 <TAsn> dos1, I don't have. JaMa and mrmoku|away have.
Sep 07 18:35:09 <ChristW_> Hi, I've almost succeeded in building SHR images on my computer, but... http://pastebin.com/3YZwDyFt
Sep 07 18:35:20 <ChristW_> The images for GTA-01 do seem to build just fine...
Sep 07 18:49:02 <dos1> mickeyl: with newest cornucopia: | src/plugins/dbus_service/plugin.vala:40.5-40.32: error: The type name `FreeSmartphone.GSM.VoiceMail' could not be found
Sep 07 19:24:07 <CIA-59> freesmartphone.org: 03seba.dos1 07cornucopia * r1fcaa7b61e8f 10/fsodeviced/src/plugins/proximity_n900/plugin.vala: proximity_n900: add debug message
Sep 07 19:34:45 <dos1> mickeyl: is proximity_palmpre supposed to work?
Sep 07 19:36:52 <playya> iirc yes
Sep 07 19:38:53 <playya> hmm. imho proximity_n900 and proximity_palmpre should be renamed to keep name consitency
Sep 07 19:40:04 <playya> maybe palmpre_powersupply and openmoko_powercontrol should be less work
Sep 07 21:34:44 <[Rui]> hi all
Sep 07 23:22:20 <playya> hi [Rui] 
Sep 08 00:57:46 <[Rui]> playya: hi!
Sep 08 00:58:40 <playya> i just updated whole efl a few hours ago and elmdentica only show an empty screen :(
Sep 08 00:59:05 <[Rui]> pldelete db
Sep 08 00:59:28 <[Rui]> I'm doing a lot of under the hood changes
Sep 08 00:59:59 <[Rui]> icons are almost fixed back but currently unviewable
Sep 08 01:00:04 <playya> ok
Sep 08 01:00:46 <[Rui]> but loading timelones should
Sep 08 01:01:01 <[Rui]>  be a lot more stable
Sep 08 01:01:40 <[Rui]> when will this baby sleep *sigh*
Sep 08 01:04:07 <playya> btw. what's the gag feature?
Sep 08 01:04:30 <playya> maybe the baby wants another bottle to drink?
Sep 08 01:05:16 <[Rui]> put a pcre regex and  if match on name, screen name or text, don't display bubble
Sep 08 01:05:52 <[Rui]> still hasn't finished the current bottle
Sep 08 01:06:32 <playya> does pcre support [[:japanese:]]+ ? :P
Sep 08 01:07:05 <[Rui]> glib pcre, possibly
Sep 08 01:07:24 <[Rui]> not like tha, oc
Sep 08 01:08:28 <[Rui]> very good if you're like me and need help to avoid engaging trolls.
Sep 08 01:10:22 <playya> the you can ignore them
Sep 08 01:11:16 <[Rui]> playya: yeah, but I'm a bit temperamental, so if I can have magic veil hiding their bait... all for the better :)
Sep 08 01:11:26 <playya> ok :)
Sep 08 01:12:03 <playya> btw. remember my wrong indented patch which added some small features?
Sep 08 01:12:08 <[Rui]> seems like he's finally falling asleep... I should be in bed two hours ago, but I can't leave it all on the missus :)
Sep 08 01:12:13 <playya> or at least a skeleton for it?
Sep 08 01:12:25 <[Rui]> playya: yeah, but some have already been implemented
Sep 08 01:12:33 <playya> ok. then you should go to bed, too.
Sep 08 01:12:51 <[Rui]> playya: btw, it now can view context statuses
Sep 08 01:12:59 <[Rui]> shit woke up
Sep 08 01:13:06 <playya> :(
Sep 08 01:13:58 <playya> what is a context status?
Sep 08 01:14:02 <[Rui]> 3w old and already a terrorist
Sep 08 01:14:27 <[Rui]> what someone replied to
Sep 08 01:14:34 <playya> congrats!!
Sep 08 01:14:46 <[Rui]> thanks :)
Sep 08 01:15:15 <[Rui]> hard to type w 1 hand
Sep 08 01:16:20 <playya> hehe. the stop typing
Sep 08 01:32:11 <trev2> Hello everyone! I have to implement the following function: "static u8 get_address (struct usb_gadget *g)" which returns the address of the usb device. So I have to copy code from the s3c2410_udc.c file from latest andy tracking (the driver). It seems like I can get the address by "udc_read(S3C2410_UDC_FUNC_ADDR_REG)" but this returns an u32 and I have no clue how to get the u8 address out of it. I already took a look at the s3c2410
Sep 08 01:32:11 <trev2>  manual but I just don't get it. Can anyone please help me?
Sep 08 01:34:33 <trev2> so basically I want to know how to get my address out of the function address register (S§C2410_UDC_FUNC_ADDR_REG)
Sep 08 01:36:45 <trev2> in the manual it says FUNC_ADDR_REG (Function address register). Offset: 0x140(L) / 0x143(B)
**** ENDING LOGGING AT Wed Sep 08 02:59:59 2010