| *** lizardo has quit IRC | 00:04 | |
| *** flailingmonkey has joined #maemo-ssu | 00:07 | |
| *** trbs has quit IRC | 00:44 | |
| *** m0use has quit IRC | 00:54 | |
| *** m0use has joined #maemo-ssu | 00:55 | |
| *** user0 has joined #maemo-ssu | 01:37 | |
| user0 | so theres stable and testing... | 01:37 |
|---|---|---|
| user0 | but i see only one changelog | 01:37 |
| user0 | MohammadAG : http://wiki.maemo.org/Community_SSU/Changelog <--- for test? | 01:38 |
| Kaptenen | Where do you find the stable one? | 01:38 |
| user0 | ^ | 01:38 |
| Kaptenen | Its not green, i guess its means its really nothing there | 01:40 |
| flailingmonkey | it is a little confusing | 01:40 |
| flailingmonkey | but the Stable link gives you a changelog of what each release of CSSU has | 01:40 |
| flailingmonkey | and the Testing link gives you install to install CSSU | 01:40 |
| user0 | makes no sense, i know. | 01:40 |
| flailingmonkey | no real "Stable" vs. "Testing" releases, at least now | 01:40 |
| Kaptenen | The link have always been there btw | 01:40 |
| user0 | http://repository.maemo.org/community-testing/community-stable-fremantle.install - Not Found | 01:42 |
| flailingmonkey | I suppose the notion was to have a Stable release after some Testing releases? just moving the changelog link to a more specific icon would make sense | 01:42 |
| user0 | i'll be install the testing release then | 01:43 |
| user0 | that list is too long to ignore | 01:43 |
| flailingmonkey | lol yeah | 01:43 |
| user0 | installing* | 01:43 |
| MohammadAG | there's to stable community repo yes | 01:43 |
| MohammadAG | yet* | 01:44 |
| MohammadAG | if it was it'd be on http://repository.maemo.org/community/ btw | 01:44 |
| user0 | :) | 01:44 |
| MohammadAG | the .install file there is for diablo, ignore it | 01:44 |
| user0 | im so sleepy i didnt even notice the /community-testing/ in the link | 01:44 |
| user0 | regardless , thanks for the info MohammadAG | 01:45 |
| user0 | i'll be reporting any bugs i notice | 01:45 |
| user0 | if any | 01:46 |
| user0 | well im sure there is, but im just trying to be optimistic :P | 01:46 |
| flailingmonkey | MohammadAG: I can try to find some sort of icon specifically for a "Changelog" link to sit next to Stable and Testing. how does that sound? | 01:49 |
| MohammadAG | actually, stable shouldn't point to the changelog | 01:51 |
| flailingmonkey | should it point to a placeholder, saying Stable hasn't been released yet? | 01:52 |
| *** andre___ has quit IRC | 01:58 | |
| *** Jade has quit IRC | 01:59 | |
| MohammadAG | flailingmonkey, that would be best imo | 02:00 |
| user0 | :S | 02:01 |
| user0 | just flashed the device | 02:01 |
| user0 | now its asking me for a lock code | 02:02 |
| user0 | i should assume the flashing finished, correct? | 02:02 |
| flailingmonkey | done | 02:02 |
| flailingmonkey | MohammadAG: made a placeholder page, and pointed the Stable icon to that page. | 02:03 |
| MohammadAG | flailingmonkey, thanks :D | 02:05 |
| MohammadAG | user0, I thought the device doesn't ask for a code after flashing | 02:05 |
| flailingmonkey | MohammadAG: I know what it's like, people often making suggestions, but always expecting "someone else" to do it :p | 02:05 |
| MohammadAG | the default code is 12345 but flashing doesn't reset that | 02:06 |
| user0 | so what now? | 02:10 |
| user0 | any idea? | 02:10 |
| flailingmonkey | it's not the pin lock code is it? | 02:11 |
| user0 | no | 02:11 |
| flailingmonkey | or last 4 digits of phone number | 02:11 |
| user0 | no | 02:12 |
| MohammadAG | flash the fiasco again, I'm pretty sure that clears the gconf key | 02:13 |
| MohammadAG | or boot some recovery image and crack the key from /dev/mtd2 | 02:13 |
| MohammadAG | sorry, mtd1 | 02:14 |
| user0 | recovery image? | 02:15 |
| user0 | where do i get that? | 02:15 |
| *** M4rtinK has quit IRC | 02:16 | |
| *** gregoa has quit IRC | 03:05 | |
| *** gregoa has joined #maemo-ssu | 03:09 | |
| *** I-C-Wiener has quit IRC | 03:14 | |
| *** user0 is now known as user0-away | 03:20 | |
| *** arcean has quit IRC | 03:21 | |
| *** user0-away is now known as user0 | 03:41 | |
| flailingmonkey | MohammadAG: ping | 04:52 |
| *** user0 has quit IRC | 05:19 | |
| *** GonzoTheGreat has joined #maemo-ssu | 06:31 | |
| *** flailingmonkey has quit IRC | 07:02 | |
| *** DocScrutinizer has quit IRC | 07:31 | |
| *** DocScrutinizer has joined #maemo-ssu | 07:31 | |
| Stskeeps | so which one of you is woody14619? ;) | 07:32 |
| DocScrutinizer | Stskeeps: errrm who? | 07:54 |
| Stskeeps | guy from tmo :P | 07:54 |
| DocScrutinizer | ouch | 07:54 |
| DocScrutinizer | I doubt many guys here are big on tmo | 07:55 |
| Stskeeps | yeah.. but this one was about commmunity involvement, improving what we have with SSU side so this seemed like a natural side ;) | 07:55 |
| Stskeeps | side=place | 07:55 |
| Stskeeps | else you have a good candidate for dragging in for hacking on stuff there :) | 07:56 |
| DocScrutinizer | seen some similar posts occasionally | 07:56 |
| DocScrutinizer | hmm, hope he'll show up eventually | 07:56 |
| DocScrutinizer | got a link to his tmo profile? | 07:56 |
| Stskeeps | http://talk.maemo.org/member.php?u=28026 | 07:57 |
| DocScrutinizer | thanks | 07:57 |
| Stskeeps | (i do read tmo, i just don't post there) | 07:57 |
| Stskeeps | login erased, password forgotten, etc | 07:57 |
| DocScrutinizer | wtf?! >> Sticky: Poll: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?<< | 07:59 |
| DocScrutinizer | tmo is such a steaming pile of hosesh*t, I get angry every other time I look at there | 08:00 |
| Stskeeps | it is, but there seems to be sentiment against even publishing any info about meego on there as it's a 'maemo' forum.. | 08:00 |
| Stskeeps | at this point, i miss internettablettalk | 08:00 |
| DocScrutinizer | idiots | 08:01 |
| Stskeeps | but anyway i was looking for woody to address some of his issues as he's the first one approaching issues in a constructive manner in about a year :P | 08:01 |
| DocScrutinizer | who says that's a "maemo forum"? | 08:01 |
| Stskeeps | even when it comes with a misunderstanding that the "OM driver" bug report means "accelerometer doesn't work" | 08:02 |
| DocScrutinizer | there's a bug report about it? | 08:05 |
| DocScrutinizer | on meegobugs? | 08:05 |
| DocScrutinizer | or where? | 08:05 |
| Stskeeps | yeah | 08:05 |
| Stskeeps | sec | 08:05 |
| DocScrutinizer | btw I'm member of internettablettalk, not any "maemo forum" ;-D http://forums.internettablettalk.com/member.php?u=35572 | 08:06 |
| Stskeeps | ah, so it's not that bug | 08:08 |
| Stskeeps | about:blank | 08:08 |
| Stskeeps | er.. | 08:08 |
| Stskeeps | https://bugs.meego.com/show_bug.cgi?id=15957 | 08:08 |
| povbot | Bug 15957: was not found. | 08:08 |
| Stskeeps | isn't that vaguely similar to what you described? | 08:08 |
| DocScrutinizer | otoh there seems to be a general resentment against meego-arm coming from a possibly false perception of meego-arm trying to lure highly competent folks away from supporting maemo, which isn't exactly what most of the N900-USING fols like to see. For sure not until all their apps got ported to meego so they could switch painlessly | 08:09 |
| Stskeeps | :nod: | 08:10 |
| Stskeeps | in open source, everyone lures though :P | 08:10 |
| Stskeeps | i mean, we have ssu, nitdroid and meego plus the misc hack projects | 08:11 |
| DocScrutinizer | ssu is about continuity :-) | 08:12 |
| DocScrutinizer | (15957) sounds about right, yes | 08:12 |
| Stskeeps | i use ssu myself, personally | 08:12 |
| DocScrutinizer | missing lots of details, but right | 08:12 |
| DocScrutinizer | actually I'd rather expect it to spam new values all the time, when actually it's supposed to act like a "relative" input device that only delivers *new* data. But yes, it's roughly hitting the point about the driver being crap basically, and odd behaviour is to be expected | 08:15 |
| Stskeeps | :nod: | 08:15 |
| Stskeeps | i guess we should all just go back to coding instead of discussing on tmo all the time ;) | 08:15 |
| DocScrutinizer | I stopped checking *any* new threads on TMO, actually never did much. | 08:16 |
| DocScrutinizer | I look there just when sb is pointing me at sth | 08:16 |
| Stskeeps | if you're interested, i have wayland working on N900, should be usable on other distros using modern kernels :P | 08:17 |
| Stskeeps | (btw) | 08:17 |
| DocScrutinizer | hmm, still don't know what to think bout wayland. My conservative nature feels it must be a bad thing ;-P | 08:17 |
| DocScrutinizer | My mind says "they better had improved X11" | 08:18 |
| Stskeeps | they've been trying to for 20 years :P | 08:18 |
| DocScrutinizer | my sarcastic alter ego says "if it's not X11 it's not linux" | 08:19 |
| Stskeeps | X11 can run as a client under it, which is probably best solution :P | 08:20 |
| DocScrutinizer | in my book easy portability of arbitrary apps from desktop to target platform is much higher a priority than eyecandy ala wayland | 08:20 |
| Stskeeps | that's the funny part actually, wayland's hardly eyecandy ;) it's buffer management as such | 08:21 |
| Stskeeps | and surface management | 08:21 |
| DocScrutinizer | so if X11 is running under wayland, I probably don't give a f* about it | 08:21 |
| RST38h | Wayland is just a way to get rid of X | 08:22 |
| RST38h | Havoc Pennington of Redhat tried to do that for years now. Got his wish, finally. | 08:22 |
| DocScrutinizer | sounds like another L.P. masterplan then :-(( | 08:22 |
| * DocScrutinizer thinks old school linux devels always tried to converge to a unified UNIX and looked at other *nix flavours to keep compatible as much as possible. The young new wildes are more like "we own Unix and we know better" - nothing I'd appreciate at all | 08:26 | |
| *** psycho_oreos has joined #maemo-ssu | 08:26 | |
| DocScrutinizer | typical instance: andridiot | 08:27 |
| DocScrutinizer | (wayland) then there's rasterman and I think I hear his words about wayland which were like "you can't create anything better than X11 plus associated stuff, no matter if you call it wayland or whatever. You'll end with re-inventing X11, and either you stop halfway to perfection of X11 and say >it's lean and small and that counts<, or you get sth that just looks and feels and behaves like X11 but without the maturity" | 08:33 |
| DocScrutinizer | there's no hybrid between framebuffer concept like QtMoko once been, and a true windows manager like X | 08:35 |
| DocScrutinizer | once you start to implement all the stuff needed to your framebuffer thingie, you end where X11 is now | 08:36 |
| *** flailingmonkey has joined #maemo-ssu | 08:36 | |
| RST38h | Doc: Programmers just want to have fun! | 08:36 |
| * RST38h cackles diabolically | 08:36 | |
| DocScrutinizer | yeah, and I hate them for that | 08:37 |
| RST38h | Actually, no, X11 is not really a frame buffer. | 08:37 |
| RST38h | VNC and RDP are, in a way | 08:37 |
| DocScrutinizer | they can have as much fun as they like, but please in their snadbox | 08:37 |
| flailingmonkey | i just read about maliit going on their own, good for them | 08:37 |
| DocScrutinizer | X11 is a way to handle your videobuffer stuff | 08:37 |
| RST38h | X11 is a way to draw stuff with primitives | 08:38 |
| DocScrutinizer | that too | 08:38 |
| RST38h | It was never very good at videobuffering, hence Havoc'shate | 08:38 |
| RST38h | X11 was created with remote acess and slow links in mind | 08:39 |
| DocScrutinizer | meh, discuss it with raster. It's his domain of competence, not mine | 08:39 |
| flailingmonkey | wondering if maliit would work as an alternative for maemo5 vkb, such that CSSU could yank out proprietary one... | 08:39 |
| DocScrutinizer | flailingmonkey: CSSU *is not* I repeat NOT about janking out anything! | 08:40 |
| DocScrutinizer | GRRR | 08:40 |
| flailingmonkey | DocScrutinizer: yeah i know :p | 08:40 |
| flailingmonkey | DocScrutinizer: some proprietary stuff is getting replaced though, mostly status-applets | 08:40 |
| flailingmonkey | DocScrutinizer: besides, fastsms is already available, no reason to muck with something that works well enough already | 08:41 |
| DocScrutinizer | I'm starting to believe I got this wrong, as everybody starts to "yank out" things like standard camera-ui, standard mediaplayer, standard vkbd | 08:41 |
| RST38h | ...as frustration is setting in. | 08:41 |
| RST38h | anyways, work | 08:41 |
| DocScrutinizer | pfff status applets. You're not talking about that mindbogglingly broken implementation of battery applet? | 08:42 |
| *** flailingmonkey has quit IRC | 08:43 | |
| *** flailingmonkey has joined #maemo-ssu | 08:44 | |
| flailingmonkey | there was the status applet for fm transmitter | 08:45 |
| flailingmonkey | i guess someone would be working on re-implementing the battery applet. did you look at the new one, or just commenting on the original being broken? | 08:46 |
| GonzoTheGreat | yanking mediaplayer is sensible for the lack of portrait mode, but portrait mode is for these young'uns ;-) | 08:46 |
| flailingmonkey | I thought the only redeeming virtue of reimplementing media player was that it would get re-used in meego stuff | 08:47 |
| GonzoTheGreat | mafw in meego? | 08:47 |
| Stskeeps | btw, no idea if this has benefit for you guys, but https://meego.gitorious.org/meego-device-adaptation/n900_libbme/trees/master | 08:47 |
| flailingmonkey | libbme... o_O | 08:48 |
| GonzoTheGreat | stskeeps: this is a maemo forum ;-) | 08:48 |
| Stskeeps | GonzoTheGreat: i know, but occasionally we drop useful code for maemo too ;) | 08:48 |
| flailingmonkey | Stskeeps: I got called an "stskeeps spokesperson" on tmo, it was very amusing | 08:50 |
| Stskeeps | flailingmonkey: heh, funny, considering i'm no real spokesperson ;) | 08:50 |
| Stskeeps | but meh, time to code | 08:51 |
| DocScrutinizer | flailingmonkey: I referred to some new implementation of battery applet that used e.g a kernel driver that's known to break bme and basically will fsckup whole system | 08:51 |
| flailingmonkey | DocScrutinizer: that sounds like adventerous programming =P | 08:51 |
| Stskeeps | the bq* conflicts with bme? :P | 08:51 |
| DocScrutinizer | yes | 08:51 |
| DocScrutinizer | sure | 08:51 |
| Stskeeps | why? :P | 08:52 |
| DocScrutinizer | exclusive allocation of chip's I2C bus | 08:52 |
| Stskeeps | hmm | 08:52 |
| DocScrutinizer | so bme can't access anymore | 08:52 |
| Stskeeps | i'm thinking of the battery meter, not the charging stuff | 08:52 |
| DocScrutinizer | old story | 08:52 |
| DocScrutinizer | bme is accessing the bq27200 battery gauge chip | 08:53 |
| DocScrutinizer | and it is reported to segfault when that kernel driver got loaded | 08:53 |
| flailingmonkey | libbme> "BME IPC function interface" | 08:54 |
| Stskeeps | DocScrutinizer: interesting, don't think we've seen that on meego | 08:54 |
| DocScrutinizer | that's why bme sucks, and that's why loading this bq27200.ko sucks | 08:54 |
| DocScrutinizer | Stskeeps: depends on load order afaik | 08:54 |
| DocScrutinizer | load kernel module, restart bme -boom | 08:54 |
| Stskeeps | i'll ask around a bit.. that might be an issue we see | 08:55 |
| DocScrutinizer | fsck bme | 08:55 |
| DocScrutinizer | it's an implementation that can't work on a clean system | 08:55 |
| flailingmonkey | DocScrutinizer: I lost track of jrbme, was it a disaster? | 08:56 |
| DocScrutinizer | btw I seem to recall bq27200.ko being a rather poor implementation with a borked non-comprehensive API as well | 08:57 |
| DocScrutinizer | the desaster is jrbme is also conflicting with bme and the weird ways this crap interacts with half the system | 08:57 |
| *** akikhaw has joined #maemo-ssu | 08:57 | |
| DocScrutinizer | I'd not like to implement a copy of such BS, and I don't think I could implement a replacement of bme, hal-addon-bme, dsme, whatnot else | 08:58 |
| DocScrutinizer | also charging honestly belongs into kernel basically | 08:59 |
| DocScrutinizer | http://talk.maemo.org/showpost.php?p=1023445&postcount=823 http://talk.maemo.org/showpost.php?p=1006716&postcount=806 | 09:01 |
| DocScrutinizer | Stskeeps: ^^^ might be interesting for you too | 09:01 |
| flailingmonkey | DocScrutinizer: thanks, I had read the first post before, but not the second | 09:04 |
| Stskeeps | DocScrutinizer: ta | 09:04 |
| flailingmonkey | Stskeeps: does libbme covers all bme "external api" or just part of it? | 09:05 |
| Stskeeps | flailingmonkey: part of it, i think | 09:05 |
| flailingmonkey | i didn't realize it had such diverse "features" like getting a timestamp that isn't affected by system time changes.. | 09:06 |
| DocScrutinizer | bme? | 09:09 |
| DocScrutinizer | it's awful | 09:09 |
| DocScrutinizer | bme even stores crap and cruft to CAL | 09:09 |
| DocScrutinizer | a completely insane thing | 09:10 |
| flailingmonkey | usually things end up like that when some program is accessing low level components so that it's in a position to be "able" to do stuff | 09:10 |
| flailingmonkey | so it ends up doing everything | 09:11 |
| DocScrutinizer | sth along the lines "I'll make a note to myself about battery status, so next time I get booted I can retrieve this info from there" | 09:11 |
| flailingmonkey | usually a sign that the design needs to be re-evaluated, but that takes billable hours :p | 09:11 |
| DocScrutinizer | flailingmonkey: during analysis of what bme does I've learned just from what it does that it is FUBAR literally | 09:12 |
| flailingmonkey | DocScrutinizer: I've always enjoyed reading your analysis posts, because they reveal all the dirty programming sins commited behind closed-source | 09:13 |
| DocScrutinizer | I mean accessing register 0x38 of a chip that has registers 0x0..0x4 is... :-x | 09:13 |
| DocScrutinizer | I don't need any further indications about competence of devels who did that as well as quality of the code | 09:14 |
| flailingmonkey | you should take a peek at libbme, for fun ;) | 09:14 |
| DocScrutinizer | *cough* | 09:14 |
| DocScrutinizer | dunno if I really wuld like to do that | 09:15 |
| DocScrutinizer | got better ways to ruin my day | 09:15 |
| flailingmonkey | well, it's more about reading messages from socket communication w/ bmeeee | 09:16 |
| DocScrutinizer | :nod: | 09:17 |
| DocScrutinizer | so probably from what's *not* there you could tell what meego-bme-botch still is doing in a wrong way that spoils things for all who prefer the clean way | 09:18 |
| *** s3cz0n3 has quit IRC | 09:20 | |
| DocScrutinizer | I'm really amazed Stskeeps and meego-arm at large are willing to deal with this botch and the incredibly stubborn way Nokia is handling this issue | 09:20 |
| DocScrutinizer | I mean it's proven that we can charge battery without bme, and we don't nuke the house by doing it. It's also evident bme is a piece of crap that doesn't hold *any* IP that deserves that label. And you run into all sorts of trouble by the nasty things bme does to system to accomplish his silly tasks | 09:23 |
| flailingmonkey | what is it bme is supposed to stand for? | 09:27 |
| flailingmonkey | wait... they're using bme in meego, because they don't want to develop anything "new" to do charging? | 09:28 |
| psycho_oreos | battery management entity | 09:29 |
| flailingmonkey | battery managment encumberance | 09:30 |
| psycho_oreos | s/management/mangling/ | 09:30 |
| GonzoTheGreat | Botched Mangled Erratic | 09:31 |
| *** GonzoTheGreat has quit IRC | 09:36 | |
| DocScrutinizer | flailingmonkey: (anything 'new') ask Stskeeps | 09:39 |
| DocScrutinizer | Stskeeps: unlike maemo, meego *had* the chance to start from scratch regarding charging and battery status reporting | 09:40 |
| flailingmonkey | my guess is that bme continues because of harmattan work | 09:41 |
| Stskeeps | DocScrutinizer: we've actually done that for battery status reporting, but charging .. let me answer that when i don't have a splitting headache | 09:41 |
| flailingmonkey | but hopefully that's not the reason | 09:41 |
| DocScrutinizer | flailingmonkey: seems confidence into a crappy stinking blob's ability to do a proper job is higher than confidence in my expertise how to manage the charging chip and LiIon cells | 09:42 |
| flailingmonkey | Stskeeps looks pretty busy over in#meego-arm | 09:43 |
| flailingmonkey | DocScrutinizer: it makes perfect sense... but only from project management viewpoint :p | 09:44 |
| DocScrutinizer | flailingmonkey: depends on the foundation paradigms of your 'project' - and who's paying your bagles | 09:48 |
| flailingmonkey | but with CSSU, it would be possible to do proper kernel approach with a bq24150 module, like you talk about in that second link | 09:48 |
| flailingmonkey | to handle apps which call into bme, would need a fake bme server which receives messages over that socket like libbme describes using | 09:49 |
| DocScrutinizer | it would - if CSSU was about breaking new ground and not about staying conservative and keep maemo alive | 09:49 |
| DocScrutinizer | flailingmonkey: yes, that's mainly the hal-addon-bme thing afaik | 09:50 |
| flailingmonkey | yeah, it's not in line with CSSU goals, but would be useful for N900 beyond maemo as well | 09:50 |
| DocScrutinizer | I didn't say it's impossible to replace bme for CSSU / jrbme, I just said it means a lot of work and the willingness to break with compatibility for quite a bit of stuff that's mostly blobs | 09:51 |
| flailingmonkey | with "bme proxy" blobs, etc would not know bme wasn't there | 09:52 |
| DocScrutinizer | flailingmonkey: see, Stskeeps *did* a hal-addon-bme for mer on N8x0 afaik. I'm not eager to do that, but you're free to ask him to join the CSSU project with his competence and to contribute, so we could finally move ahead with bme-free OS topic ;-) | 09:53 |
| flailingmonkey | "bme" just wouldn't be doing what bme does now. handling the weird extras that apps called on bme for is probably tricky | 09:53 |
| DocScrutinizer | flailingmonkey: there are also termal management magic between dsme and bme, and I got NFC if all that is properly managed in this libbme you mentioned | 09:54 |
| DocScrutinizer | the question is what else we'd need to take care of... | 09:55 |
| DocScrutinizer | OTOH if we don't start to use a jrbme on a wider user base, we'll never learn ;-) | 09:56 |
| flailingmonkey | how did you watch socket packets sent to and from bme? | 09:56 |
| DocScrutinizer | somebody built a special kernel tracing the packets to syslog | 09:56 |
| *** chainsawbike_ has joined #maemo-ssu | 09:57 | |
| DocScrutinizer | stracing bme seems prone to reboot system | 09:57 |
| *** trbs has joined #maemo-ssu | 09:57 | |
| DocScrutinizer | though otoh you might succeed to strace bme when you start it directly, not under surveilance of dsme | 09:58 |
| flailingmonkey | well, if bme communications all happen through socket, maybe write a fake bme, with same api, which records packets before handing them off to real bme, and same in opposite direction | 09:58 |
| *** chainsawbike has quit IRC | 09:58 | |
| *** chainsawbike_ is now known as chainsawbike | 09:58 | |
| DocScrutinizer | flailingmonkey: I basically just lost interest in (jr)bme as obviously meego doesn't want it and evidently H-E-N doesn't need it | 09:59 |
| flailingmonkey | and TMO makes people want to claw their eyes out | 09:59 |
| claw | :) | 10:00 |
| DocScrutinizer | flailingmonkey: that's a feasible approach, but we'd also need to trace all the direct filehandles | 10:00 |
| DocScrutinizer | flailingmonkey: as mentioned in that tmo post, shadowjk has written a rather nice script for charging, based on my draft and a lot of chats between the two of us. This script "just works" for all that matters to me here, and the benefit of replacing bme in maemo is questionable at best | 10:02 |
| flailingmonkey | would your (draft) proposed bq24150 module be doing the same work? | 10:04 |
| DocScrutinizer | if we'd define "getting close to meego compatibility" as a goal of equal right besides "keep maemo alive", I could see a possible benefit of getting a clean full-FOSS charging - only if meego would go same path and not try to recycle bme shitball | 10:05 |
| DocScrutinizer | flailingmonkey: basically yes. You'd still need or at least want some userland "driver", basically a initscript doing some "echo foo >/sys/bq24150/bar" stuff, maybe a bit more, e.g. to handle PC hosted USB charging | 10:06 |
| flailingmonkey | with the renewed lack of Nokia influence, I suspect that it would be accepted | 10:07 |
| flailingmonkey | lol, the topic of charging came up over on #meego-arm | 10:09 |
| flailingmonkey | <Stskeeps> lamikr: i'm wondering if our odd issues with charging / battery metering has to deal with that BME tries to gain exclusive access to the i2c bus and this one is taken by bq*, DocScrutinizer raised that issue as having seen it in maemo | 10:10 |
| *** m0use has quit IRC | 10:16 | |
| *** andre__ has joined #maemo-ssu | 10:33 | |
| *** Jade has joined #maemo-ssu | 10:45 | |
| *** Jade has joined #maemo-ssu | 10:45 | |
| *** lardman|gone has quit IRC | 10:50 | |
| *** BCMM has joined #maemo-ssu | 10:53 | |
| *** m0use has joined #maemo-ssu | 11:08 | |
| *** lardman has joined #maemo-ssu | 11:45 | |
| *** lardman has quit IRC | 11:45 | |
| *** lardman has joined #maemo-ssu | 11:45 | |
| *** BCMM has quit IRC | 11:49 | |
| *** zaleb has joined #maemo-ssu | 12:08 | |
| *** arcean has joined #maemo-ssu | 12:12 | |
| *** flailingmonkey has quit IRC | 12:47 | |
| *** M4rtinK has joined #maemo-ssu | 12:55 | |
| *** PoOky_ is now known as vStone | 13:12 | |
| *** lizardo has joined #maemo-ssu | 13:48 | |
| *** wmarone has joined #maemo-ssu | 14:31 | |
| *** wmarone__ has quit IRC | 14:32 | |
| *** M4rtinK has quit IRC | 14:33 | |
| *** wmarone_ has joined #maemo-ssu | 14:35 | |
| *** wmarone has quit IRC | 14:35 | |
| *** the_lord has joined #maemo-ssu | 15:16 | |
| *** david__ has joined #maemo-ssu | 15:17 | |
| *** the_lord has quit IRC | 15:21 | |
| *** TurboVomit has joined #maemo-ssu | 15:21 | |
| *** Damnshock has quit IRC | 15:37 | |
| *** Damnshock has joined #maemo-ssu | 15:39 | |
| *** david__ has quit IRC | 16:05 | |
| *** the_lord has joined #maemo-ssu | 16:05 | |
| psycho_oreos | DocScrutinizer, lol found a working IMEI code for N900, you wouldn't believe where it was | 16:06 |
| DocScrutinizer | hmm, maybe on one of my pictures? | 16:08 |
| DocScrutinizer | or on a picture Nokia published? | 16:09 |
| DocScrutinizer | inside N9 "prototype"? | 16:09 |
| DocScrutinizer | psycho_oreos: where was it? | 16:09 |
| DocScrutinizer | probably on the outside of your box | 16:10 |
| psycho_oreos | DocScrutinizer, pm? :) | 16:10 |
| psycho_oreos | nope, found it online | 16:10 |
| DocScrutinizer | go ahead | 16:10 |
| *** the_lord has quit IRC | 16:32 | |
| *** psycho_oreos has quit IRC | 16:50 | |
| *** TurboVomit has quit IRC | 17:03 | |
| *** WellMux has joined #maemo-ssu | 17:25 | |
| *** m0use has quit IRC | 19:32 | |
| *** Facaa has quit IRC | 20:00 | |
| *** Facaa has joined #maemo-ssu | 20:02 | |
| *** lardman has quit IRC | 20:09 | |
| *** BCMM has joined #maemo-ssu | 21:03 | |
| *** BCMM has quit IRC | 21:24 | |
| *** I-C-Wiener has joined #maemo-ssu | 21:48 | |
| *** lardman has joined #maemo-ssu | 22:10 | |
| *** lardman has quit IRC | 22:10 | |
| *** lardman has joined #maemo-ssu | 22:10 | |
| thp | what happened to the hildon-desktop switcher? awesomeness in terms of show landscape apps in portrait switcher? | 22:25 |
| thp | nice! | 22:25 |
| *** lcuk2 has joined #maemo-ssu | 22:55 | |
| *** lardman|home has joined #maemo-ssu | 22:58 | |
| *** lcuk has quit IRC | 22:58 | |
| *** lardman has quit IRC | 23:01 | |
| *** BCMM has joined #maemo-ssu | 23:23 | |
| *** peetah_ has quit IRC | 23:44 | |
| *** peetah has joined #maemo-ssu | 23:46 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!