| 00:11.41 | *** join/#maemo-ssu freemangordon (~freemango@46.249.74.23) |
| 00:56.21 | *** join/#maemo-ssu Snafu777 (~user@unaffiliated/snafu777) |
| 01:03.00 | *** join/#maemo-ssu sono (~sono@tucana.uberspace.de) |
| 01:30.16 | okias | well, it works with gcc 4.7.3, for next time: do not use 4.8.1 for PXA270! |
| 03:30.22 | wmarone | wow, pxa270 |
| 03:30.29 | Snafu777 | Question for the masses here: If you found dns servers that allowed zone transfers, how would u tell the sys admins? |
| 03:42.30 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 03:54.34 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
| 04:16.12 | *** join/#maemo-ssu varu|zZz (~whee@192.158.14.99) |
| 04:18.29 | *** join/#maemo-ssu thedead1440_ (~thedead14@unaffiliated/thedead1440) |
| 04:19.27 | *** join/#maemo-ssu g3kk3r_ (torrkull@lehtori.cc.tut.fi) |
| 04:29.45 | *** join/#maemo-ssu oldtopman (~oldtopman@unaffiliated/oldtopman) |
| 04:32.44 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
| 05:59.00 | *** join/#maemo-ssu Woody14619a (~Woody@Maemo/community/contributor/Woody14619) |
| 06:38.05 | *** join/#maemo-ssu FlameReaper (~assassin@183.171.164.136) |
| 06:54.56 | *** join/#maemo-ssu merlin_1991 (~merlin@merlin1991.at) |
| 07:03.11 | *** join/#maemo-ssu kolp (~quassel@212.255.243.78) |
| 07:11.29 | *** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 07:26.09 | *** join/#maemo-ssu luf (~luf@80.188.29.62) |
| 07:48.34 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 08:18.57 | *** join/#maemo-ssu Woody14619b (~Woody@2620:4:4000:11:c475:28ee:129b:a600) |
| 08:22.09 | *** join/#maemo-ssu sixwheeledbeast (~paul@cl-1547.lon-02.gb.sixxs.net) |
| 08:22.36 | *** join/#maemo-ssu freemangordon (~freemango@46.249.74.23) |
| 08:28.09 | *** join/#maemo-ssu arcean (~arcean@apn-31-1-238-78.dynamic.gprs.plus.pl) |
| 08:33.01 | *** join/#maemo-ssu arcean (~arcean@apn-77-113-26-120.dynamic.gprs.plus.pl) |
| 08:37.11 | *** join/#maemo-ssu freemangordon (~freemango@46.249.74.23) |
| 08:58.10 | *** join/#maemo-ssu trx (ns-team@212.200.198.106) |
| 08:58.10 | *** join/#maemo-ssu trx (ns-team@devbin/founder/trx) |
| 10:44.01 | DocScrutinizer05 | okias' story reminds me a lot at the fun we had with kernels for GTA02 at OM. It never really became clear whether it been race conditions or uninitialized vars or use of not properly allocated memory which sometimes just works and sometimes nukes other relevant data/code |
| 11:09.34 | *** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net) |
| 11:22.01 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
| 11:25.19 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-71-76.residential.rdsnet.ro) |
| 11:58.43 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
| 12:19.33 | sono | well |
| 12:19.52 | sono | these days we have vastly improved debugging capabilities in the kernel |
| 12:19.59 | sono | that alone is worth upgrading to mainline |
| 12:20.21 | sono | it's a bunch of work of course, but it's beneficial for all ports |
| 12:37.49 | *** join/#maemo-ssu M13 (~Miranda@83.149.35.51) |
| 12:40.33 | *** join/#maemo-ssu okias (~okias@berger.cust.centro-net.cz) |
| 13:07.33 | *** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 13:08.05 | *** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 13:28.38 | *** join/#maemo-ssu merlin1991 (~merlin@Maemo/community/cssu/merlin1991) |
| 13:40.55 | *** part/#maemo-ssu luf (~luf@80.188.29.62) |
| 13:50.02 | *** join/#maemo-ssu oldtopman (~oldtopman@unaffiliated/oldtopman) |
| 13:56.10 | *** join/#maemo-ssu arcean (~arcean@apn-31-2-38-73.dynamic.gprs.plus.pl) |
| 13:59.22 | *** join/#maemo-ssu Ken-Young (~kenyoung@wrls-67-134-207-230.wrls.harvard.edu) |
| 14:01.41 | Ken-Young | Is there a time of day during which traffic tends to peak on this channel? Is there any official meet-up time during which Fremantle porting issues are discussed? |
| 14:04.19 | merlin1991 | traffic peeks between 17 and 22 CET |
| 14:04.29 | merlin1991 | official meet up are non-existant |
| 14:05.29 | Ken-Young | merlin1991, Thanks! |
| 14:08.17 | merlin1991 | but in general, if you have ideas questions, ... just voice them, most people read the backscroll when they arrive |
| 14:10.16 | Ken-Young | OK. I'd like to work on the Fremantle Porting Project, but I really don't know where to start. I'm a decent C programmer (I think), I'm fairly familiar with Linux and I've written a few apps for the N900. |
| 14:10.44 | Ken-Young | But I dont know if I can do anything useeful for the porting project, or how to get started on it. |
| 14:11.21 | Ken-Young | Is the main effort to write new source code files to replace the closed-source libraries? |
| 14:11.36 | Ken-Young | If so, how do people typically do that? |
| 14:11.50 | merlin1991 | afaik it mostly replaceing the closed bits |
| 14:12.09 | merlin1991 | also freemangordon and Pali are working on getting a recent kernel to work with all the hw |
| 14:12.11 | Ken-Young | Do you try to find documentation on the functions the library supplies? Do you disassemble the library? |
| 14:12.19 | merlin1991 | everything |
| 14:13.00 | Ken-Young | Has anyone written up a description of how they successfully replaced a closed-source library? |
| 14:13.14 | merlin1991 | don't think so |
| 14:14.14 | Ken-Young | Is there coordination so that somebody is "assigned" a piece of the project to work on, so that there is not uncoordinated duplication of effort? |
| 14:15.17 | Ken-Young | Have the closed bits been prioritized in some way? SUrely not all the closed pieces are considered of equal importance... |
| 14:15.44 | merlin1991 | there's http://wiki.maemo.org/Fremantle_closed_packages |
| 14:16.57 | merlin1991 | regarding assinging, the people who work on stuff just pick what they want and most of the time announce it in here |
| 14:17.20 | merlin1991 | but since it's only Pali freemangordon and jonwil there was no real coordination necessary yet |
| 14:18.30 | merlin1991 | Raimu-X: yep there a problem with diffs on regular extras devel, the update interval makes no sense, a diff would always contain 1 added packge |
| 14:23.51 | Ken-Young | merlin1991, So is the color-coding on that web page Green=Done, Red=NotDone and White (no color)=NotStarted ? |
| 14:24.50 | merlin1991 | from the top of the page: |
| 14:24.51 | merlin1991 | Green color means that package is working and is fully API/ABI compatible with closed one which is available in SSU repository. It can be same version (opened by Nokia on gitorious) or new FOSS replacement. |
| 14:25.09 | merlin1991 | Red seem to be possible GPL violations |
| 14:26.27 | Ken-Young | No color = nothing done yet? |
| 14:27.17 | Ken-Young | It's hard to imagine that anyone will really bother working on, for example, amazon-installer. |
| 14:27.36 | merlin1991 | not really, ie jonwil worked on the csd bits alreay, but it still has no colour |
| 14:28.20 | merlin1991 | well the list is a complete list of what is in maemo, that's why there is a "Needed For N900" column |
| 14:28.35 | merlin1991 | sadly the Needed For Maemo column isn't filled in yet |
| 14:30.19 | Ken-Young | Is there a "fully open" distribution of Maemo available that one could download to a spare N900 and test out, to see what functionality is missing/broken? |
| 14:31.43 | Ken-Young | Has anyone tried to contact Nokia about the GPL code for which sources don't seem to be available? |
| 14:32.28 | merlin1991 | I think Pali contactetd nokia about all the GPL bits, a "fully open" distribution wasn't attempted yet |
| 14:32.32 | merlin1991 | would be interesting though |
| 14:33.37 | kolp | Isn't that what the debian-on-n900 project is after? |
| 14:33.43 | kolp | Not based on maemo, though... |
| 14:33.48 | Ken-Young | Yeah, if one had the current open version installed on a test N900, it might help clarify what remaining closed-bit parts are the most important conversion candidates. |
| 14:34.28 | Ken-Young | And it could be a starting point for the neo900 distribution. |
| 14:35.25 | merlin1991 | heh, I think I'll look into that, shouldn't be too hard to hack together |
| 14:38.23 | merlin1991 | just wonders how to set up the rootfs |
| 14:39.12 | merlin1991 | I guess all debs into a folder and dpkg --unpack over them is the fastest way |
| 14:42.11 | Ken-Young | merlin1991, Would it make sense to start with a very minimal Debian distribution, and then modify it towards Maemo? My impression is that everyone hates busybox anyway, maybe the rootfs should be built with real gnu utilities instead. |
| 14:42.54 | merlin1991 | yes everyone hates busybox, but in order to have that fancy distribution we need hw that supports it, untill then we do have the rootfs problem |
| 14:43.30 | merlin1991 | and then there is the idea of backwards compatability with n900 sw |
| 14:44.10 | merlin1991 | and also I'm no spokesmen for the neo900 project, I'm just repeating what I picked up |
| 14:44.41 | merlin1991 | actually I don't even know who's going to be the head of the neo900 distribution |
| 14:44.42 | Ken-Young | But I use real GNU utilities instead of busybox already on my N900, because I use EasyDebian. There's no porting that needs to be done to get real "ls" rather than busybox to work on an N900, is there? |
| 14:45.04 | merlin1991 | sure there is absolutely no porting that needs to be done |
| 14:45.10 | merlin1991 | but busybox is there because of size contrains |
| 14:45.24 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 14:45.51 | merlin1991 | hey Pali please read the backlog and correct me where I was wrong and/or add info :) |
| 14:46.14 | Ken-Young | Could the rootfs just contain the GNU utilities needed to boot the OS, and the rest of the GNU utilities could be put under /opt ? |
| 14:47.07 | merlin1991 | Ken-Young: it would be even possible to have a proper seperate /usr outside the rootfs |
| 14:47.46 | merlin1991 | only that since it is a phone it has to have functionality in a rootfs only case like emergency calls |
| 14:47.58 | merlin1991 | which esentially means 90% of the system must be able to boot from rootfs |
| 14:48.57 | merlin1991 | btw I once had the case where the eMMC broke in my n900, it boots perfectly fine all the way into hildon desktop, only can do almost nothing then thanks to no swap |
| 14:49.14 | merlin1991 | s/only can/only you can/ |
| 14:50.14 | Ken-Young | merlin1991, Thanks for the info. |
| 14:50.33 | merlin1991 | if you approach the problem from the view point that it just should work, then ofc you can slap all kinds of stuff into the system |
| 14:50.43 | merlin1991 | but it makes setting up a fresh install quite hard |
| 14:50.59 | merlin1991 | you'd have to somehow fill the eMMC with the stuff you need after you flashed the rootfs |
| 14:51.16 | merlin1991 | or you need to provide Images for both which then would erase user data on reflash |
| 14:51.29 | *** join/#maemo-ssu Martix_ (~martix@eduroam-104.fi.muni.cz) |
| 14:51.53 | merlin1991 | which was one of the coolest features in the n900, reflash the "full" system but only overwrite the rootfs in the process |
| 14:55.14 | Ken-Young | It would seem to me that it would be worth the effort to start trying to build our one flashable images, so that wee can start making fully open N900s, just for testing purposes. |
| 14:55.30 | Ken-Young | s/one/own/ |
| 14:56.16 | Ken-Young | Even if the resulting N900 was a brick, we might learn what needs to be done next. |
| 15:00.23 | merlin1991 | yeah, I'm currently running in circles how to achieve it, but my best bet is to adapt that script that exists in debian which you can use to build new sb2 targets |
| 15:00.26 | merlin1991 | I forgot the name though |
| 15:01.15 | merlin1991 | take that script, modify it to use the metapackge as base list for packages to install, and then run it against a copy of the ssu repo that is free only |
| 15:07.45 | Ken-Young | merlin1991, Has the Fremantle Porting Project specified what the project's product is supposed to ultimately be? Is it indistinguishable from CSSU, or are they trying to make a distribution that you would build yourself in the scratchbox environment, and then flash? |
| 15:10.48 | merlin1991 | the project as such does not really exist, it's just a name on top of all the individual efforts |
| 15:10.59 | merlin1991 | otherwise it would have at least a wiki page with some info :D |
| 15:11.53 | merlin1991 | Afaik the product is supposed to be a system that runs on a recent kernel on the neo900 hw and is backwards compatible to fremantle on the n900 |
| 15:12.02 | merlin1991 | DocScrutinizer05: is the above correct? |
| 15:12.17 | DocScrutinizer05 | mompl |
| 15:13.24 | merlin1991 | actually the thread title on tmo says it all 'the Fremantle Porting Task Force, or "how to run maemo on Neo900"' (see http://talk.maemo.org/showthread.php?t=91308 ) |
| 15:13.38 | merlin1991 | so I guess the "Produkt" will be a flashable image for the neo900 |
| 15:14.46 | DocScrutinizer05 | merlin1991: how far back I need to read backscroll? |
| 15:14.58 | merlin1991 | like 3 lines :) |
| 15:16.07 | DocScrutinizer05 | yes, correct |
| 15:16.31 | DocScrutinizer05 | FPTF is NOT targeting at a distinguished distro |
| 15:17.23 | DocScrutinizer05 | it's a sort of platform adaption package on top of fremantle stock, similar in operation principles to any other CSSU flavor |
| 15:18.03 | DocScrutinizer05 | plus it comes with its own kernel, which *so far* is unique for CSSU flavours |
| 15:18.43 | DocScrutinizer05 | userland and kernel API shall be 100% compatible |
| 15:19.27 | DocScrutinizer05 | the system may introduce some adaptions |
| 15:19.58 | DocScrutinizer05 | either in form of patched libraries, or in form of compatibility layers |
| 15:20.10 | Ken-Young | Would it make sense to start making a fully open Maemo distribution for a stock Beagleboard then, or have things already progressed further than that? |
| 15:20.28 | DocScrutinizer05 | yes, absolutely |
| 15:20.32 | DocScrutinizer05 | makes sense |
| 15:21.01 | Ken-Young | OK, Maybe *that's* where I could jump in and try to help. |
| 15:21.12 | DocScrutinizer05 | much appreciated |
| 15:21.17 | DocScrutinizer05 | :-) |
| 15:21.51 | Ken-Young | Gotta get me a Beagleboard... |
| 15:22.17 | merlin1991 | well I did like the idea of a flashable n900 image aswell |
| 15:22.33 | DocScrutinizer05 | try to get one with DM3730 and 1GB of RAM |
| 15:22.33 | merlin1991 | just sayin ;) |
| 15:22.40 | DocScrutinizer05 | *cough* |
| 15:22.45 | DocScrutinizer05 | 512MB RAM |
| 15:22.59 | Ken-Young | But if the real target is a neo900, then a Beagleboard is a better starting place, right? |
| 15:23.10 | Ken-Young | (better than N900) |
| 15:23.30 | DocScrutinizer05 | a DM3730 board is for sure the better starting point, in some regards |
| 15:24.10 | DocScrutinizer05 | in other regards the N900 is closer to the Neo900 than all the existing DM3730 boards |
| 15:24.31 | DocScrutinizer05 | particularly when it comes to display and most of the peripherals |
| 15:24.40 | Ken-Young | Obviously it would be of no use for the Camera bits, etc, but at least the basic OS, WiFi etc could be tested on a Beagleboard. |
| 15:24.56 | DocScrutinizer05 | yes |
| 15:25.11 | DocScrutinizer05 | though WiFi subject to change |
| 15:25.22 | DocScrutinizer05 | but that's marginal |
| 15:25.53 | DocScrutinizer05 | USB for example should be optimally testable on BB |
| 15:26.11 | DocScrutinizer05 | since we won't perpetuate N900 USB abomination |
| 15:26.24 | DocScrutinizer05 | we will use 100% BB design for USB |
| 15:26.26 | merlin1991 | but it was so great (not) |
| 15:27.17 | DocScrutinizer05 | sorry, afk, bbl (+5h) |
| 15:29.26 | DocScrutinizer05 | charging in BB is also more like Neo900 than N900's is |
| 15:31.25 | Ken-Young | OK, I guess I'll get a BB, and try to start making a distro that could ultimately be Maemo for the neo900. |
| 15:32.52 | Ken-Young | DocScrutinizer05, Do you know of a BB model number that would be closest to what will reside in the neo900, or are they all the same? |
| 15:33.11 | DocScrutinizer05 | sorry, nfc |
| 15:33.20 | DocScrutinizer05 | never looked closely into BB |
| 15:34.01 | Ken-Young | But isn't the neo900 essentially a BB put into an N900 case, or am I completely clueless here? |
| 15:34.16 | DocScrutinizer05 | but I heard they changed/upgraded design several times, from "like N900" to "like Neo900" |
| 15:35.01 | DocScrutinizer05 | the latest one supposed to have DM3730 afaik |
| 15:35.06 | Ken-Young | Would it be better to get a gta04, and start working from that base? |
| 15:35.22 | DocScrutinizer05 | and no, we gonna put a gta04 into a N900 case, not a BB |
| 15:35.48 | DocScrutinizer05 | yeah, that would be better, alas there are pretty few gta04 available |
| 15:35.59 | DocScrutinizer05 | all sold out ;-) |
| 15:36.19 | Ken-Young | gta04s are still listed on the Golden D. page - do you know if they really still have some to sell? |
| 15:36.46 | DocScrutinizer05 | but there are a few available that have "minor" defects, like WLAN, GSM, BT, whatever not functioning |
| 15:37.14 | Ken-Young | OK, I guess I should contact G.D., and see what they've got that they might sell me. |
| 15:37.19 | DocScrutinizer05 | gta04 listed but not "on stok" |
| 15:37.34 | DocScrutinizer05 | yeah, go ahead, by all means |
| 15:37.51 | Ken-Young | Thanks. That'll be a good starting point for me. |
| 15:38.07 | DocScrutinizer05 | tell Nikolaus I sent you ;-) |
| 15:38.15 | Ken-Young | Will do! |
| 15:39.24 | DocScrutinizer05 | state clearly you need the device for Neo900-targeted OS/fremantle development |
| 15:41.09 | Ken-Young | Yes, I'll try to explain exactly what I'm trying to do. Obviously I care nothing about the case, the display could be scratched or have bad pixels, etc. He's probably got a lemon like that somewhere. |
| 15:55.05 | *** join/#maemo-ssu M13 (~Miranda@83.149.37.27) |
| 16:05.22 | DocScrutinizer05 | there's a list with defective devices available iirc |
| 16:07.14 | Ken-Young | I sent Nikolaus a note... |
| 16:29.17 | *** join/#maemo-ssu NIN101 (~NIN@p5DD29D4F.dip0.t-ipconnect.de) |
| 16:33.01 | *** join/#maemo-ssu freemangordon (~freemango@46.249.74.23) |
| 16:33.25 | DocScrutinizer05 | merlin1991: do you think we should get infra (repos etc) for maemo-cssu/fremantle/porting/(gta04|neo900|n900) ? |
| 16:33.53 | DocScrutinizer05 | maemo-cssu/fremantle/porting/n900 would be the free fremantle for N900 |
| 16:34.12 | DocScrutinizer05 | neo900 and gta04 accordingly |
| 16:34.49 | freemangordon | DocScrutinizer05: what would be the difference between "free" and "non-free"? and what would be the "non-free" one? |
| 16:35.06 | DocScrutinizer05 | errrwut? |
| 16:35.37 | DocScrutinizer05 | non-free is stock fremantle |
| 16:35.52 | freemangordon | ah, I see |
| 16:36.10 | DocScrutinizer05 | and the difference is obviously all the blobs replaced or wrapped into compatibility layers |
| 16:37.11 | freemangordon | system blobs in CSSU? I don;t see a reason why we need yet another repo for that, -devel -testing -stable should be enough IMO |
| 16:38.20 | DocScrutinizer05 | yeah, porting/n900 is a bit... of lobotomy |
| 16:39.31 | DocScrutinizer05 | e.g we'd want to keep any bme-dummy or whatever in that, as well as mce, and we for sure would want to host a cmt/isi solution in there that's working with a USB dongle instead of the embedded BB5 modem |
| 16:40.05 | DocScrutinizer05 | basically think of porting/n900 as the backported porting/neo900 version |
| 16:41.06 | freemangordon | hmm, I'd rather take the other approach - take fremantle as it is (in cssu-thumb), put it on neo900 and add/replace whatever needed |
| 16:41.22 | DocScrutinizer05 | porting/* is a generic solution to run fremantle on arbitrary platforms. Since "arbitrary platforms" includes N900, we of course expect to see a version of porting-fremantle for neo900 |
| 16:41.37 | freemangordon | though... |
| 16:41.54 | freemangordon | maybe your way is better, I have to think about it for a while |
| 16:42.58 | DocScrutinizer05 | e.g your 3.19 kernel would live in porting/n900 |
| 16:43.44 | freemangordon | DocScrutinizer05: yeah, your approach is more generic than mine |
| 16:43.54 | DocScrutinizer05 | as well as any other hw platform specific adaptions to the basic fremantle (after stripping/patching it to kick out n900 specific proprietary stuff) |
| 16:44.07 | freemangordon | :nod: |
| 16:45.22 | freemangordon | DocScrutinizer05: but we will have to fin a way to distribute some "installer", be it generic or platform-dependant |
| 16:45.27 | freemangordon | *find |
| 16:45.59 | DocScrutinizer05 | yep |
| 16:46.03 | freemangordon | and we'll have to migrate CSSU to that infra :( |
| 16:46.25 | DocScrutinizer05 | didn't think about any such details yet |
| 16:46.39 | DocScrutinizer05 | we should discuss it, but not now, my GF kills me |
| 16:46.49 | freemangordon | heh |
| 16:47.18 | freemangordon | though I guess she is paitient enough, being your GF :P |
| 16:48.15 | freemangordon | Pali: do you want to debian package libcal? you know, if it is me to do it, I'll use autotools and you hate them :) |
| 16:48.40 | Pali | hm, why autotools? |
| 16:48.53 | DocScrutinizer05 | we need a way to build an image |
| 16:48.55 | Pali | for one easy oneline Makefile? |
| 16:49.19 | freemangordon | Pali: no particular reason, it is just what I prefer |
| 16:49.24 | freemangordon | not saying it is better |
| 16:49.25 | DocScrutinizer05 | obviously the flasher approach is not feasible |
| 16:49.29 | freemangordon | yeah |
| 16:50.12 | DocScrutinizer05 | ask dos1 how that works on GTA04 |
| 16:50.13 | freemangordon | DocScrutinizer05: hmm, wait, why flasher is not an option? |
| 16:50.41 | DocScrutinizer05 | afaik they install to uSD |
| 16:50.46 | freemangordon | we can flash a "minimal" fremantle, which supports wifi and install online |
| 16:50.56 | DocScrutinizer05 | yep :-) |
| 16:51.19 | DocScrutinizer05 | l8rs |
| 16:51.23 | DocScrutinizer05 | afk |
| 17:02.06 | sono | hm, the beaaglebone idea might be worth a shot, tho i only have a black at the moment, i could buy a regular one |
| 17:21.37 | *** join/#maemo-ssu Woody14619 (~Woody@Maemo/community/contributor/Woody14619) |
| 17:23.16 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-71-76.residential.rdsnet.ro) |
| 17:32.35 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-71-76.residential.rdsnet.ro) |
| 18:05.35 | *** join/#maemo-ssu Martix_ (~martix@dhcp-227-236.eduroam.muni.cz) |
| 18:12.41 | *** join/#maemo-ssu Ken-Young (~kenyoung@wrls-67-134-207-237.wrls.harvard.edu) |
| 18:40.17 | *** join/#maemo-ssu XDS2010 (sid1218@gateway/web/irccloud.com/x-nhpnngsfusjtyriq) |
| 19:06.18 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
| 19:09.28 | *** join/#maemo-ssu Woody14619 (~Woody@2620:4:4000:11:c475:28ee:129b:a600) |
| 19:11.29 | *** join/#maemo-ssu Woody14619 (~Woody@2620:4:4000:11:c475:28ee:129b:a600) |
| 19:12.35 | *** join/#maemo-ssu Woody14619 (~Woody@2620:4:4000:11:c475:28ee:129b:a600) |
| 19:15.54 | *** join/#maemo-ssu Woody14619 (~Woody1461@Maemo/community/contributor/Woody14619) |
| 19:24.37 | DocScrutinizer05 | Woody14619: wazzup? |
| 19:25.15 | DocScrutinizer05 | http://privatepaste.com/471a155a61 |
| 19:27.00 | Woody14619 | Sorry. Changing IRC clients and had to hop between a couple to get all the data... and of course they were all set to auto-connect by default. :P |
| 19:27.42 | DocScrutinizer05 | :-D |
| 19:27.59 | Woody14619 | Old client didn't do SASL... :P |
| 19:39.10 | *** join/#maemo-ssu Woody14619 (~Woody1461@Maemo/community/contributor/Woody14619) |
| 19:50.45 | *** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 19:53.22 | *** join/#maemo-ssu anYc_ (anyc@home.hadiko.uni-karlsruhe.de) |
| 20:01.04 | okias | Hey guys, when you ported nokia kernel to 2.6.38, I guess you didn't noticed switch from bootmem to LMB? |
| 20:01.14 | okias | 2.6.36-rc1 |
| 20:02.12 | okias | Pali: hey, for 2.6.35 it was broken gcc 4.8.1 :) and for 2.6.36 it's LMB change (not friendly to patch code) :) |
| 20:04.07 | *** join/#maemo-ssu chem|st_ (~chemist@svn.unix-ag.uni-kl.de) |
| 20:12.43 | Pali | I did not used 2.6.38 |
| 20:12.49 | Pali | so I do not know |
| 20:35.46 | *** join/#maemo-ssu unclouded (~neil@2001:4428:200:80fc:7e05:7ff:fe0d:d421) |
| 20:43.33 | *** join/#maemo-ssu oldtopman (~oldtopman@unaffiliated/oldtopman) |
| 20:54.28 | *** join/#maemo-ssu kolp_ (~quassel@212.255.234.27) |
| 21:19.33 | *** join/#maemo-ssu Woody14619 (~Woody1461@Maemo/community/contributor/Woody14619) |
| 21:53.28 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-177-125-59.net.upcbroadband.cz) |
| 22:00.50 | *** join/#maemo-ssu aap (~drew@cpe-174-101-232-161.cinci.res.rr.com) |
| 22:09.38 | *** join/#maemo-ssu drathir (~kamiljk8@s51.linuxpl.com) |
| 22:13.18 | *** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net) |
| 22:56.52 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 23:49.22 | *** join/#maemo-ssu obiwlan (~obiwlan@p5DC02FCB.dip0.t-ipconnect.de) |