=== _LibertyZero is now known as LibertyZero === _LibertyZero is now known as LibertyZero_ [12:48] * apw yawns === yofel_ is now known as yofel [15:01] pgraner: Hi Pete [15:01] * lag mpoirier Hi Mathieu [15:02] Lol [15:02] mpoirier: Hi Mathieu [15:02] lag: I'll get back to you in 5 minutes. [15:02] No problem [15:04] hi lag and mpoirier [15:04] how's going, [15:05] Hey cooloney [15:05] Good thanks buddy, and you? [15:05] Are you safely home? [15:05] lag: i am still in Boston with ericm|ubuntu and minipanda [15:06] lag: working from our lexington office [15:06] Ah, is apw there too? [15:06] And rtg? [15:07] lag: sure, we are together [15:07] How romantic [15:08] lag: they are in a meeting. i think [15:12] lag, howdy [15:12] Hey Pete [15:12] Are you in Lex too? [15:12] lag, no I'm home [15:12] pgraner, hope everything is OK with your house now? [15:13] ericm|ubuntu, no house left, but we are all fine [15:13] pgraner: Did you manage to find somewhere nice to stay in the mean time? [15:14] pgraner, sad to hear but glad you are all good [15:14] lag, currently at my inlaws, looking for a rental house [15:14] ericm|ubuntu, thanks [15:16] lag, irc meetings start up again tomorrow, you still going to report out ARM status? [15:20] bjf: I don't believe I am [15:21] bjf: You'll need to speak to pgraner for a replacement ARM spoke person [15:21] lag, maybe we'll just skip ARM this cycle [15:21] bjf: :) [15:22] * lag feels a weight lifted [15:25] hey ! [15:25] bjf: no, actually, i will still work on ti-omap4 [15:25] dare you [15:25] :) [15:25] ogra: heh, big brother you are here [15:25] sure i am ... someone said arm :) [15:26] * ogra hopes the kernel team can answer his questions on the ubuntu-devel ML [15:26] bjf and pgraner, i will join the meeting this week. since I am still in Boston. [15:27] cooloney, great glad to have you [15:27] cooloney, maybe while you are together in boston you can pick a regular victim for the weekly irc meeting? [15:28] cooloney, or you can just send the status to me and I can just report it out [15:28] pgraner: thx. np for me. glad your family are good. [15:28] cooloney, thanks [15:31] bjf: i will be in the meeting. and thanks for lag [15:32] he sent out the email for collecting ARM status [15:32] ericm|ubuntu: will you join the IRC meeting? [15:32] cooloney, no problem - as long as you guys are OK [15:33] cooloney, you'll be in the meeting every week? [15:33] cooloney: I did this week, but probably won't do it again [15:33] cooloney: Take a copy of it and remember to send it out to the ARM Kernel folks every week [15:33] bjf: we will join the meeting this week. [15:34] bjf: and how about we sent status to your every week later [15:34] cooloney, that works [15:34] bjf: thanks, man [15:35] * cooloney feels good when working from office [15:40] cooloney, you been house boy for so long time === jdstrand_ is now known as jdstrand [16:23] jjohansen: hey - do you know if there is any trick i need to do, other than putting a bare git tree under /srv/git..../git/serge/, to have it show up in gitweb on kernel.ubuntu.com? [16:23] (i looked at yours as example, didn't see any export-ok or anything like that) [16:25] hallyn: did you change the commit hook? [16:26] nope [16:26] i can git-clone it, fwiw [16:28] hallyn: hooks/post-update [16:30] hm, created that, no listing yet [16:31] right, you need to run it manually [16:31] https://wiki.ubuntu.com/Kernel/Dev/KernelGitGuide [16:31] the bottom of it [16:31] git update-server-info [16:32] doh [16:32] hrmm, it seems I am using a slightly different hook in natty [16:39] hm, still nothing. i guess i'll start from scratch later and try again [16:42] hallyn: hrmm, that should work, the post-commit hook is only needed to update the web when new commits are made, [16:42] hallyn: just follow the wiki, it has worked for me everytime [16:46] jjohansen: the wiki page you pointed me to doesn't list --bare, which someone was telling kees to use [16:46] think i had used --bare, so i'll try without [16:46] hallyn: right just add --bare [16:46] hm, tha'ts what i had done then :) ok [16:46] hallyn: the whole move the .git out of the checkout is what --bare does [16:48] ok, will try that workflow verbatim and then push my patches from externally, thanks [16:53] jjohansen: oh, i just looked at index.README - i think my problem was actually just combination of not having originally called it 'name.git', and then not waiting an hour for the cronjob :) (bc i thought the git update-server-info cmd would do it) [16:53] will check later if cronjob did its thing -thx [16:54] hallyn: ah yeah that makes sense === bjf is now known as bjf[afk] === lifeless_ is now known as lifeless [20:27] apw, ping - so any chance ubuntu-lucid-lbm could be made to work on ARM and how? === bjf[afk] is now known as bjf [20:45] * ogasawara lunch [21:02] apw, copying over the rt28* from lbm works for me just perfectly [21:02] apw, thanks man === Hedge|Ho1 is now known as Hedge|Hog [21:46] apw, could you take a look at this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/668554 [21:46] Launchpad bug 668554 in linux (Ubuntu) "Blank display at startup in Sony Vaio CW series (affects: 1) (heat: 464)" [Undecided,New] [21:47] apw, there should be a fix in 2.6.36 (finding out which is just a matter of git bisect) but it's more like a feature than a fix for SRU? [21:48] ericm|ubuntu, is not a blank screen a pretty obviously a bug thing ? [21:48] apw, cool - then I'll try figure out the patch and get it backported [23:14] hi guys, can we attribuate a specific processor for a process in unix ? if yes how ? [23:16] lighta: http://www.cyberciti.biz/tips/setting-processor-affinity-certain-task-or-process.html [23:17] thanks =) [23:18] lighta: you're welcome [23:26] sconklin, may I ask how should I attribuate a % usage now ? [23:27] lighta: if you mean te get a process to run on a particular CPU some % of the time, I don't know whether you can do that. [23:28] hmm ok thx, i'll continue dig info then [23:29] "processor affinity" is probably the most useful search term for this topic [23:31] lighta: in general, the types of problems solved by setting processor affinity would mean that you want to leave a task locked to one processor forever [23:32] yes, because it's long task but wasn't develop to run on multithread