/srv/irclogs.ubuntu.com/2010/02/25/#ubuntu-arm.txt

=== ApOgEE__ is now known as ApOgEE
persiaNoisi: Hey.  Did you not get an answer about your mysqlclient question yesterday?09:47
Noisionly go to #sql , but i got no answer there09:49
persiaBother.09:50
persiaSorry I didn't answer you then: I ended up falling asleep.09:50
persiaSo my memory is that you had a cross-compile environment but you wanted to try binaries without needing to compile them, is that correct?09:50
mikeulogra, it looks like you made all the necessary changes to RootfsFromScratch that we discussed yesterday.09:54
ogramikeul, yes, sorry, i didnt want users to run into problems09:54
mikeulno problem, that makes sense.09:54
mikeulI'll just have to find another problem I guess.09:55
persiamikeul: What kind of problem do you like?09:56
mikeulI'm not really looking for problems, they usually find me.09:57
persiaOK.  I usually have a reserve of issues available if you're looking for something :)09:59
persiaAlso, we're having a mini-sprint on Thumb2 porting in about an hour, if you'd like to participate.10:00
asaco/10:58
ograhmm, all languages are gone from our images again10:59
ograthat wasnt the plan :/10:59
ogra* Languages: es xh pt de fr bn11:01
ogra* language-pack-${Languages} [i386 amd64 powerpc]11:01
ograoh, sigh11:01
dyfethmm...yea...11:01
ograStevenK, ^^^ can you change that post freeze ?11:02
asacok ... X is crashing badly on me :/11:03
asacon x86 luckily ;)11:03
ograon armel or x86 ?11:03
ograah11:04
ograin what way ?11:04
asaci hit ctrl+enter -> boom11:04
asacbut only sometimes11:04
ograweird11:04
* asac upgrades and hopes there was a fix11:04
dmartHi guys11:05
ograhrm, a rootstock build of ubuntu-netbook hangs reliably in "unpacking iso-codes"11:05
asachey dmart11:05
* ogra wonders why that is11:05
ograhi dmart11:05
dmartHi there, sorry I'm late--- got sucked into a discussion about gdb11:06
asacogra: did we figure why ooo is pulled in for us now?11:06
ograall fixed and gone :)11:06
asaccooool11:06
ograseems someone added language-support-$lang for all languages and all arches above11:06
ograthe -support packages pull in thesaurus and packages that in turn pull in oo.o11:07
asachmm11:07
looldmart: You mean you hanged in a discussion with gdb11:07
ograusually we only have -pack and -pack-gnome11:07
asaclol11:07
dmartlool: ?11:08
looldmart: hanging... gdb...11:08
looloh well11:08
dmartlool: well, segfaulting11:08
* lool tried to do silly jokes11:08
loolI suspect asac has pity for my jokes11:08
* dmart was slow on the uptake11:09
dmartAnyone ready to take a look at https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList11:09
dyfetwe can step you through it...11:09
asacso ...11:10
asaci think it would be time to add a column for the current status there11:10
asacor move all the fixed/invalid bugs to a separate table11:10
loolJust drop them?11:10
loolThere's wiki history, we don't need to clutter the page for fixed bugs do we11:11
asacnot sure11:11
looldmart: Got blocked on the gcc atomic builtins qemu changes by their ppc maintainer who objects to using them in general, and for ppc in particular; need to redo the patch to only use these for arm/thumb    :-(11:11
asachaving a page that shows what was done isnt that bad either11:12
asacare there instructions how to do that without gcc atomics? ... /me checks11:12
dmartI added some info on https://wiki.ubuntu.com/ARM/Thumb2PortingHowto11:13
dmartStill a bit high-level, but better than nothing (hopefully)11:14
lool<< On ARMv7, there is a DMB instruction which performs this operation. There is also an MCR p15, ... operation which is backwards-compatible the earlier architecture versions.  >>11:14
loolFrankly, I much prefer getting the code to use atomic builtins in, even if only for arm/thumb in my case11:14
dmartIf you use the atomics, you shouldn't need to use these low-level barriers.11:15
dmart...which are obviously totally arch-specific and non-portable.11:15
loolI think it would help portability to use them by default, but apparently the ppc qemu maintainer prefers holding to comments from 2005 to judge of their usefulness11:15
dmartDid you understand why the qemu guys were resistant>?11:15
looldmart: Yeah we're on the same line11:15
looldmart: No; let me find the thred11:15
loolhttp://lists.gnu.org/archive/html/qemu-devel/2010-02/msg01142.html11:16
dmartAlso, it's easier to write buggy atomics code than almost any other sort of code... so the KISS principle definitely applies ;)11:16
loolI checked with another qemu maintainer what he thought of it, and that's the person who suggested I should ask for benchmarks11:16
looldmart: I'm also pretty sure the code is getting abused in the case of qemu11:17
dmartWhat are atomics used for in qemu anyway?11:17
loolHeck, I could have proposed a patch to use pthread mutxes, that would have been fun11:17
looldmart: locks11:17
loolWhich actually sucks11:17
StevenKogra: That's a silly change, sigh11:17
dmartDoes qemu use multithreading to emulate high-level processes, or something?11:18
ograStevenK, yeah, agreed11:18
looldmart: Hmm good question, it can emulate two CPUs though11:18
loolI suppose that's only possible with threading or multiple processes, but suspect they use something closer to threading to share memory11:18
lool(it actually uses multiple hosts CPUs when emulating multiple guests CPUs)11:19
dmartRight.  Well, you can certainly implement fast spinlocks using exclusives and barriers if it's really needed, but that's probably in issue to worry about when the spinlocks are found to be a bottleneck?11:19
looldmart: Interestingly, the gcc atomics doc recommends not to use them for spinlocks11:19
dmartReally, I missed that11:20
asacto not use what? the gcc built ins11:20
* dmart looks11:20
asac?11:20
loolHmm actually I can't find that reference any more11:20
asac;)11:20
dmartCertainly you should use __sync_lock_* for spinlocks (and not the other funcs)11:20
asaclool: he seems to be fine to use those for thumb2 ... so whats the problem?11:21
looldmart: Sorry, got confused by this comment http://sourceware.org/ml/libc-alpha/2005-06/msg00132.html11:21
dmartThey (can) have reduced barriers which make them less of an overhead.11:21
looldmart: ack, that's what I used11:22
looldmart: There's no technical problem here, it's mostly politics11:22
loolthe ppc maintainer didn't even say which part of the 2005 discussion he was referring to11:22
asacright.11:22
asacbut do we care about ppc11:22
looli.e. performance, should be in libc or whatever11:22
asacthey seem to be fine if we submit that for arm11:22
dmartNot sure about the comment there--- certainly if you try to take a spinlock and find it's contended, then you can't just loop, because the kernel does not know to schedule the lock holder.11:22
loolasac: Yes, only choice I have for that bug11:22
asaci dont see that beging a problem11:23
asacif folks are happy with their current ppc solution etc.11:23
dmartYou need to do a thread yield (and even that's inefficient--- the kernel still doesn't know what to schedule next)11:23
asacthen let them keep that11:23
dmartIf we can use the GCC atomics for arm as a first step, that's probably the best approach.  They can be optimised later if this looks like a significant benefit.11:24
dmartThis is certainly no worse than arch-specific implementations in general.11:24
loolI wonder whether they would accept a configure flag to use them11:25
dmart#ifdef __arm__ ?11:25
loolI was thinking #ifdef ppc, use_gcc_atomics=no11:26
lool:-)11:26
loolAnyway, it's politics; I will eventually sort it out with upstream11:26
dmartMaybe.  The other arches might have a view on this though.11:26
loolthere's no complexity here11:26
dmartok11:26
loolI wanted to share the discussion with you because of the comments on gcc atomics11:26
dmartSure, that's useful, thanks.11:26
dmartThe main reason for emphasising the atomics is we want to quickly port to an implementation which works with v7 and Thumb-2, without everyone needing to understand the low-level details (which make my brain hurt a bit ;) )11:27
dmartBut anything can be optimised in the future11:28
dmart...11:28
dmartasac, all: Should we review through the status of items on https://wiki.ubuntu.com/ARM/Thumb2PackageReviewList ?11:29
dmartWe should identify unfixed or blocked packages.11:29
asacyes11:29
asacso erlang11:29
asacis TODO11:30
asacand gmp still11:30
asacdyfet: ^^11:30
asacwe already discussed gmp last time, so we dont need to do that11:30
asacnot sure if we want to go through ffmpeg11:30
asacmaybe that would make sense11:31
persiaerlang has code-generation.  As does parrot.  That might be an interesting set of topics.11:31
asaclibmad is another candidate11:31
dmartffmpeg has optimised assembler, but that was already dealt with11:31
asacffmpeg is done?11:31
asacoh right11:31
asacits in the last column11:32
dmartIt would be good to note on this page whenever something is resolved11:32
asac12:10 < asac> i think it would be time to add a column for the current status there11:32
asac12:10 < asac> or move all the fixed/invalid bugs to a separate table11:32
asacso yes11:33
dmartWould it make sense to trawl quickly through the issues with bugs raised to classify them?11:33
dmartI can add a resolved column11:33
asacyes11:33
asacok i can cancel my edit11:33
dmartOh, ok11:33
asaceither you say which packages are still not resolved11:33
asacor the other way around ;)11:33
dmartShall we work through?  Probably won't take long.11:33
asacok boost*11:34
asacis done11:34
* asac updates the wiki if thats ok11:34
dmartok, if you want11:34
asaccacao-source?11:34
asacthats still open11:34
dmarthang on11:34
asacbugwise11:34
persiacacao was recently removed in Debian.  Do we need it?11:34
dmart boost1.38 is not resolved, what happened to that?11:34
persiaShould have been dropped from the archive.11:35
dmartAlso, the boost1.41 source package was not changed (or this isn't documented in the bug)11:35
asacdmart: its not in the archive anymore11:35
asachttps://edge.launchpad.net/ubuntu/+source/boost1.41/+changelog11:35
asacboost is fixed11:35
asacexcept 1.38 ... but thats not in the archive anymore (too old)11:36
dyfet38 was dropped, 40/41 was patched11:36
dmartAh, ok, I didn't scroll far enough up the bug.11:36
dmartasac, can you note those?11:36
asacyes11:36
asacalready done ;)11:36
dmartok, thanks!11:37
=== DavidBz is now known as berco
asacdjvulibre11:37
asac-> done (we checked that last week and evven added a safety belt)11:37
asacerlang11:37
asac-> not done11:37
asacevolution-data-server -> done11:37
asacffmpeg resolved11:38
asacgcc-4.4 -> was never considered an issue, e.g. is probably right (11:39
dmartgcc-4.4 is under continuous maintenance, so we can mark that an not needing specific action here.11:39
asacack11:39
asacglib2.0 -> done (atomics by dmart ;))11:39
dmarthmmm, I remember now11:39
asacgmp -> not yet done ... discussed last time; dyfet is on it and i was told he bumped prioritiy now11:40
dyfetthere is an upstream issue with configure tests...11:40
asacfor glib?11:40
dyfetgmp11:40
asacah11:40
dmartpolitics or technical? ;)11:40
dyfetyeah...11:41
dyfetthey want never to do try_compile tests, and use the tripplet to identify archs only...11:41
asacthey are dumb ;)11:41
dyfetof course armv7/thumb2 is still "arm" as far as target arch's go...11:41
asactry_compile isnt that bad11:41
asactry_run is bad11:41
dmartHmmm, that only works on x86 where the triplet identifes the arch version...11:41
dyfeta bit like lool's issue in qemu ;)11:41
asaci dont see that we can do it without try_compile, can we?11:42
dmartJust checking the GCC version number might be considered adequate.  But try_compile felt more reliable...11:43
asaci agree with dmart11:43
dyfetme too11:43
asacdmart: what version number is lower bound?11:43
asac4.1.0?11:43
dmartI'm assuming lucid GCC is the bound (i.e. 4.4.3)11:43
dmartThis is not quite true, but it's a reasonable approximation11:44
asachmm11:44
asacanyway.11:44
asaci think we can use try_compile and just patch it11:44
asacpush it to debian11:44
asacand let democracy decide at some point11:44
asacmost likely other distros will pick it up too and then upstream is alone ;)11:45
dmart(by "reasonable approximation" I mean "safe approximation")11:45
dyfetokay11:45
dmartYou might also run nm on libgcc.a.  But there's no guarantee the functions won't turn fully into builtins in the future...11:45
asacdyfet: lets just get the work done first and then care about politics11:46
asacalso CC me on upstream discussion ;)11:46
dyfetwell, we need to know in this case if we are thumb2 or not otherwise we break debian on armv4, etc...11:46
dyfetso try_compile seems the safest way by far11:46
asac_right11:46
asac_reconnect ;)11:46
dmartok, so gmp is in progress11:47
asac_dyfet: so you have the patch?11:47
dyfetI did not do a try_compile patch, but I can do so quickly after the sprint11:47
asac_give it to me ... also forward me upstream discussion you had so far ... so i can poke them too ;)11:47
asac_ok11:47
asac_seems gmp will be fixed today11:47
asac_i think the next two are all not-for-us (klibc, libgc)11:48
asac_then we have libmad11:48
asac_which isnt fixed11:48
asac_and llvm11:49
asac_both not fixed11:49
dmartWho is handling klibc?11:49
asac_dmart: i thought it was toolchain/kernel folks11:49
asac_actually i thought there are no real issues there.11:50
* asac_ grabs the filtered files11:50
dmart ./klibc-1.5.15/usr/klibc/arch/arm/setjmp.S:    mov     pc, lr11:51
dmart ./klibc-1.5.15/usr/klibc/arch/arm/setjmp.S:    mov     pc, lr11:51
dmart ./klibc-1.5.15/usr/klibc/arch/arm/setjmp.S:    mov     pc, lr11:51
dmart ./klibc-1.5.15/usr/klibc/arch/arm/setjmp.S:1:  mov     pc, r311:51
dmart ./klibc-1.5.15/usr/klibc/arch/arm/vfork.S:     mov     pc, lr11:51
dmart ./klibc-1.5.15/usr/klibc/arch/arm/vfork.S:     mov     pc, lr11:51
dmartI'd need to look at the source package to see whether that matters.11:51
asacyeah11:52
asaci think it matters11:52
dmartProbably we should raise a bug on this one.11:53
asacwe should use BX lr11:53
asacunless i am mistaken ;)11:53
asacdmart: right11:53
dmartYes... though I also see #ifndef __thumb__ ... #ifdef __thumb__ ; I don't know which one is actually built11:54
dmart(in setjmp.S)11:54
asachmm11:55
asacbug 52772011:55
ubot4Launchpad bug 527720 in klibc (Ubuntu) "thumb2 porting issues identified: klibc uses mov.*pc (affects: 1)" [Undecided,New] https://launchpad.net/bugs/52772011:55
asac_dmart: even for thumb it uses #else /* __thumb__ */11:57
asac_mov pc, lr11:57
asac_line 7811:57
dmartYes, that's probably bad (actually, worse than using it in ARM)11:58
asac_feels like its safe to use bx lr there11:58
dmartProbably yes.  I'm wondering whether anyone builds this for Thumb-111:59
dmartduh11:59
dmartthat doesn't matter, ignore me ;)11:59
asac_mov     pc, r311:59
asac_thats just bx r3?11:59
asac_dmart: ?11:59
persiaYes.12:00
dmartProviding r3 is derived from a return address12:00
dmart(I think that's the case here)12:00
saeedlatest lucid-netbook-armel+dove doesn't aultomatically login, any idea which user&password should I use?12:00
asac_ok let me do the patch then12:00
loolsaeed: ubuntu no password12:00
persiadmart: Why wouldn't bx r3 work for an arbitrary branch address?12:00
saeedlool: thanks12:01
dmartpersia: generally, yes.  But if the address is detemined by some arithmetic or something the thumb bit (0) might not be set correctly12:01
persiaAha.  Thanks for the explanation.12:02
asac_http://launchpadlibrarian.net/39762158/klibc-thumb.patch12:02
asac_attached to bug 52772012:02
ubot4Launchpad bug 527720 in klibc (Ubuntu Lucid) (and 1 other project) "thumb2 porting issues identified: klibc uses mov.*pc (affects: 1)" [High,Triaged] https://launchpad.net/bugs/52772012:03
dmartWe still need to check this code isn't built with -marm12:03
* dmart greps for -marm12:04
dmartnot found, probably OK12:04
dmart...12:04
asac_dmart: the patch only touched ifdef __thumb__12:04
dmartAh, actually there is a problem12:04
asac_so it should be safe even if we build with -marm ;)12:05
asac_dmart: what problem ?12:05
dmartThe assembler always defaults to ARM12:05
asac_right12:05
asac_so we build with arm here ;)12:05
asac_but we could build with __thumb__ now12:05
asac_using this fix12:06
dmartThis is preprocessed assembler, to __thumb__ will be defined (by the GCC defaults)12:06
dmart*so12:06
dmartSo I think we're OK12:06
dmartActually the functions will get assembled as Thumb because they both have the .thumb_func firective.12:06
dmart*directive12:06
dmartSo this is probably fine.12:07
asacok12:07
asacso ... i think we are set with this patch?12:07
* asac thinks someone should try that out12:07
dmartvfork.S needs patching too12:07
asacdmart: i patched that ;)12:08
asaccheck the patch12:08
asac13:02 < asac_> http://launchpadlibrarian.net/39762158/klibc-thumb.patch12:08
asacoh12:08
asaci even failed ;)12:08
dmart-er- I mean setjmp.S needs patching12:09
asacyes12:09
asaci just failed to produce a patch ;)12:10
asacnew patch attached12:10
asachttp://launchpadlibrarian.net/39762270/klibc-thumb.patch12:10
dmartYes I think that looks OK.12:10
persiaUm, not all the changes in vfork.S from the first patch appear in the second patch.12:11
asac_persia: ?12:11
dmartI think the second half of the first patch is a headerless non-unified diff of setjmp.S (or something)12:11
asac_persia: forget the first patch ... not sure why it was busted12:11
asac_right ... what dmart said12:11
asac_i am sure i had >> for the second part12:12
asac_but apparently i missed -u12:12
* dmart is just making it up really12:12
persiaAh.12:12
persiaYes, that does look right (if confusing)12:12
asac_so lets continue (i marked it as "has patch" in table12:13
asac_libgc is next12:13
asac_that one is doko business12:13
asac_doko: fixed in 6.8-1.2ubuntu112:13
asac_so now to libmad12:14
asac_what are the hits?12:14
* asac_ checks filtered files12:14
dmartLooks like an attempt to address an inline data or jump table -- should be a simple fix12:15
dmart ./libmad-0.15.1b/imdct_l_arm.S:    add     r2, pc, #(imdct36_long_karray-.-8)12:15
* asac_ looks at porting page12:15
asac_so just adr r2, pc ?12:16
asac_hmm12:16
asac_nope12:16
asac_adr r2, imdct36_long_karray-.-812:16
asac_err12:16
asac_adr r2, imdct36_long_karray12:16
dmartThe trouble is that the pc is a bit unpredictable depending on the code alignment12:16
persiaAnd this is likely to be an alignment issue, right?12:17
dmartSearch the porting page for "getting the address of local data in the text section"12:17
asac_right12:17
asac_i think we already discussed that last week ... and i remembered that adr is the right way ;)12:17
dmartLooking at it though, I don't know what the data is doing in .text12:18
dmartMaybe it would be better to push it into .rodata12:18
dmart(it's not code)12:18
asac_#define K14  0x0cb1934612:19
asac_if thats used it means we have preprocessed assembler?12:19
asac_e.g. we can use #ifdef __thumb__ ?12:19
dmartThis is really a cleanup change, so we probably don't even need that: we just want to switch from a less portable to a more portable way of addressing the data.12:20
asac_are we sure the data isnt modified?12:21
dmartI don't think it will be.  It's in .text which is not usually made writable12:21
dmartMy guess is this is a table of precomputed data to speed up the imdct calculation.12:22
asac_right12:22
dmartThe simplest option is to leave it where it is and use adr to address it.12:22
asac_heh ;)12:23
asac_would be interested in how to do it with rodata though too12:23
asac_anyway let me do the patch ... one moment12:23
asac_oh .. adr is #ifdef __thumb__ or > armv4t ?12:24
asac_dmart: ?12:24
dmartI suggest no #ifdef.  adr really is the same instruction (just via a pseudo op which makes sure it's really correct)12:24
dmartOh, hang on a minute... this code is built as ARM (as default behaviour again)12:25
dmartI suggest to do the adr patch anyway; it's cleaner12:25
asac_yeah12:26
dmartOr if you want we could try building it in Thumb with12:26
asac_ok12:26
asac_one sec12:26
dmart#ifdef __thumb__12:26
dmart.code 1612:26
dmart#endif12:26
asac_.code 16?12:26
dmart(Or .thumb, it's a synonym)12:26
asac_ah12:26
asac_let me first do the adr patch12:26
asac_dmart: adr exists since a certain gcc/assembler version or what?12:27
dmartI'll work on the other, since I did not explain myself well...12:27
asac_http://pastebin.com/M6V3aqiW12:27
asac_that would be the libmad adr patch12:27
asac_ ;)12:27
asac_let me attach that to the bug unless you shout12:28
dmartasac_: I think adr has been there for a long time; unless someone is using really ancient tools it should work12:28
asac_yeah12:28
asac_cool12:29
asac_ok attached12:29
asac_next is llvm12:30
* asac_ goes and greps12:30
asac_hmm. that seems to be more extensive ;)12:30
dmartThere is an ongoing bug thread conversation for this one.  Basically, the jumping in/out of JITted is not interworking aware.12:30
asac_http://paste.ubuntu.com/383646/12:30
asac_:/12:31
asac_ok ... so is on the poirting page what to do for this kind of jump in/out from arm to thumb and vv.12:31
asac_?12:31
dmartI think so; I pointed Xerxes RÃ¥nby at this, but I haven't had feedback yet.12:32
dmartProbably modifications are only needed in a few places, but it will take someone familiar with llvm to know where12:32
asac_hmm12:33
dmartProbably best to label this as under discussion for now.12:34
dmartDo we know the priority of llvm?  Does much depend on it?12:34
asac_so12:35
asac_needs investigation; potential code gen; doko: only used in openjdk-6-jre-zero when using shark12:35
asac_thats the comment12:35
asac_doko seems to think its ok12:35
asac_oh12:35
asac_well not sure if one can interpret that out of the comment12:35
dmartI think it's not used for openjdk-6 by default (some separate, Thumb EE based JIT is now contributed)12:36
dmart...in openjdk-612:36
asac_according to our table llvm has zero rdepends12:36
asac_(priority)12:36
asac_i think we can move on and come back to llvm later12:38
asac_mono ... i have the cherry pick staged on my disk12:38
asac_the one we discussed the other day ... besides that we found to be fine?12:39
asac_or still "needs more investigation" ?12:39
dmartI can't remember the discussion now... was there interworking stuff to fix (in addition to the atomics)?12:41
asacdmart: we had discussion in #mono ... with vargez ... from what i recall we found one more patch12:42
asacbut besides from that the outcome was that it should be ok wrt to interworking12:42
dmartoh yeah, I'd forgotten that was about the same topic...  yes I agree12:42
asaci have that patch locally ... waiting for a3 freeze to be lifted12:42
asacthat hd isnt wired up, so i can show it right now12:43
dmartOK, I'm happy to wait :)12:45
dmartNext package?12:45
asac_15:43 < dmart> <vargaz>Ihttp://lists.ximian.com/pipermail/mono-patches/2010-February/166945.html12:46
asac_thats the patch ;)12:46
asac_yes12:46
asac_bug 51423212:46
ubot4Launchpad bug 514232 in newlib (Ubuntu Lucid) (and 1 other project) "[arm] needs porting to thumb2 (affects: 1)" [High,Triaged] https://launchpad.net/bugs/51423212:46
asac_" investigate if its used - affected code is on places like crt0.S where it may not be a problem (dmart)"12:46
* asac_ apt-get source newlib12:47
asac_dmart: why do you think its not used?12:48
asac_oh12:48
asac_seems that it uses ifdef _-thumb__12:48
asac_like:12:48
asac_#if defined(__thumb__) || defined(__thumb2__) blx   r312:48
asac_#else mov     lr, pc mov     pc, r312:48
asac_#endif12:48
asac_.LC24:12:48
asac_in ./libgloss/arm/crt0.S for example12:48
asac_so ./libgloss/arm/crt0.S definitly is fine ... checked all uses of mov12:48
dmartYes, this package generally looks like Thumb-2 was thought about by someone.12:49
asac_then we have ./libgloss/arm/redboot-crt0.S: ... which probably is marm12:49
asac_but even that has thumb ifdefs12:49
asac_so ... cool. lets scratch it12:49
* asac_ marks it invalid and drops comment in bug12:49
dmartOK12:50
asac_next is ocaml12:50
asac_bug 51423512:50
ubot4Launchpad bug 514235 in ocaml (Ubuntu Lucid) (and 1 other project) "[arm] needs porting to thumb2 (affects: 1)" [High,Invalid] https://launchpad.net/bugs/51423512:50
asac_i marked that as invalid already12:50
asac_so the assembly isnt used it seems12:51
asac_i think i checkd build system and also even added bogus code to the asembly that would trigger a build failure ... to no result12:51
dmartok12:51
ogradid you note that a full new ocaml eneterd from debian yesterday ?12:51
ogra*entered12:51
asac_ogra: new upstream?12:51
ograbug #52607312:52
* ogra checks12:52
ubot4Launchpad bug 526073 in xstr (Ubuntu) (and 51 other projects) "[OCaml 3.11.2 transition][round 3/6] Please rebuild packages involved in OCaml transition (universe) (affects: 1)" [Undecided,Fix released] https://launchpad.net/bugs/52607312:52
asac_they do a transition during freeze?12:52
asac_thtas annoying12:52
ograah12:53
ograits the same ocaml12:53
asac_ok ;)12:53
ograjust the depending packages12:53
persiaPlease check with sgnb about that.12:53
ograsorry for the noise :)12:53
persiaIt's on hold right now.  james_w is expecting to do the next round of syncs once the freeze lifts.12:53
asac_ocaml-3.11.2$ find | xargs grep arm.S12:53
asac_./asmrun/arm.S:/* $Id: arm.S 8823 2008-02-29 14:21:22Z doligez $ */12:53
asac_so there is no match for that arm.S file that has the code12:54
asac_not sure if i am missing something12:54
ograoh, wait, i'm wrong12:54
ograa new ocaml came in of feb 15th12:54
ograsilly version numbers12:54
persiaAnd the transition is in process, and the transition team is working to make sure it builds on armel.12:54
asac_dmart: do you see any way that arm.S could be used in that project?12:54
ogra3.11.1-2 to 3.11.2-112:54
asac_persia: they do thumb2 porting ;)? i doubt that12:55
asac_most stuff doesnt fail to build12:55
ograwell, i think the new ocaml at least deserves a new grep run on the new package12:55
asac_i did now12:56
persiaasac_: They are testing against qemu-arm-static and lool's qemu, so they should notice breakage as well.12:56
asac_also i did the last run last week12:56
dmartI guess so.  Probably there has been no change relevant to us...12:56
ograi think its unlikely something changed but you never know12:56
asac_the grep above is from the current lucid12:56
asac_13:53 < asac_> ocaml-3.11.2$ find | xargs grep arm.S12:56
asac_13:53 < asac_> ./asmrun/arm.S:/* $Id: arm.S 8823 2008-02-29 14:21:22Z doligez $ */12:56
asac_ok ... moving on.12:56
asac_openssl12:56
asac_we didnt create a bug for that because:12:56
asac_"seems ok - only armv4 files affected - verify that those are not used for modern arm "12:56
asac_so we should double check that now to scratch it forever12:57
* asac_ apt-get source openssl12:57
=== hrw|gone is now known as hrw
asac_we have a .pl file with assembly :) ...12:57
asac_./openssl-0.9.8k/crypto/aes/asm/aes-armv4.pl:movpc,lr@ return12:58
asac_i think that file is used12:58
asac_there is no other arm file in aes/asm12:59
* asac_ looks at build log12:59
asac_https://edge.launchpad.net/ubuntu/+source/openssl/0.9.8k-7ubuntu6/+build/149286812:59
asac_http://launchpadlibrarian.net/38924017/buildlog_ubuntu-lucid-armel.openssl_0.9.8k-7ubuntu6_FULLYBUILT.txt.gz12:59
asac_hmm ... dont see that armv4 is used somewhere13:00
asac_http://paste.ubuntu.com/383659/13:00
asac_thats the grep13:00
asac_any idea how those .pl files are used in that build system?13:01
asac_next one would be pixman13:04
asac_bug 51423713:04
ubot4Launchpad bug 514237 in pixman (Ubuntu Lucid) (and 1 other project) "[arm] needs porting to thumb2 (affects: 1)" [High,Invalid] https://launchpad.net/bugs/51423713:04
asac_seems i marked it as invalid13:04
asac_"Checked this. Its a false positive. the mov isn't used in combination with pc etc. ... the only use of it is in a ifdef _MSC_VER block ... e.g. windows only."13:05
asac_so its a MS thing13:05
asac_dmart: ^^13:05
asac_?13:05
dmartI think so; pixman is actively developed against Thumb-2 anyway I think.13:05
asac_postgresql-8.4 -> is fixed in bzr or even uploaded in archive already13:06
asac_was just atomics13:06
asac_qemu-kvm -> not sure ... bug 51425213:06
ubot4Launchpad bug 514252 in qemu-kvm (Ubuntu) "[arm] (might) need porting to thumb2 (affects: 1)" [Low,In progress] https://launchpad.net/bugs/51425213:06
asac_lool: ?13:06
ograi think lool is on that ?13:06
asac_did you do the swp atomics?13:06
asac_or do you need help? or is this the issue we talked about above?13:07
asac_ok seems it has a patch13:07
asac_http://launchpadlibrarian.net/39067738/0001-Detect-and-use-GCC-atomic-builtins-for-locking.patch13:07
asac_lool: planning to upload that?13:07
dmart^^ For openssl, some nasty hacks are used to enable compatibility with interworking, but the hacks look like they should work13:07
asac_dmart: do you understand the .pl files and how they are used?13:08
asac_lool: qemu-kvm just uses atomics for resetlock and testandset ?13:08
asac_or is the patch just a first revision?13:09
persiaThe .pl files for openssl are neither used in the build system nor installed int he package, and there seems to be a sufficiently comprehensive test suite that we'd notice an issue.13:10
asac_persia: we wont notice mov.*pc style things unless we are using smp afaiu13:10
asac_we could add some bogus syntax stuff and see if it causes some failure13:11
persiaUgh, so we'd have to run the test suite on SMP to know if it's an issue?13:11
asac_no ... we have to read the code ;)13:11
asac_and find out if its run13:11
asac_if its run its an issue ... if not, its not13:11
dmartThe mov pc issues will show up independently of SMP13:12
asac_dmart: how will it show up?13:12
dmartcrashes13:12
dmartThe issue for SMP is the atomics13:12
asac_hmm ok13:12
persiaThen I'm *really* confident that openssl is just fine.13:12
asac_isnt openssl testsuite run during build?13:12
persiaThat's a massive test suite.13:12
asac_yeah13:12
asac_so its not run? /me would think security would be damn hard about having that enabled13:13
dmartopenssl looks OK to me (if a bit nasty)13:13
asac_dmart: where do you see the nasty bits? (just for education)13:13
persiaasac_: It is run during build, and it succeeded in http://launchpadlibrarian.net/38924017/buildlog_ubuntu-lucid-armel.openssl_0.9.8k-7ubuntu6_FULLYBUILT.txt.gz for all four runs.13:13
asac_like you said there was interworking ... where do you spot that?13:13
asac_persia: nice13:13
asac_so yeah. openssl is off our list then13:13
asac_postgres is covered, qemu-kvm seems to be in progress (lets wait for lool)13:14
asac_next would be qt4-x1113:14
asac_is commented to have a webkit copy13:14
asac_webkit is invalid i found: bug 49037113:14
ubot4Launchpad bug 490371 in qt4-x11 (Ubuntu) "Atomic operations not safe for ARMv7,Thumb-2 and multicore (affects: 2)" [Medium,Triaged] https://launchpad.net/bugs/49037113:14
asac_bug 51425513:14
ubot4Launchpad bug 514255 in webkit (Ubuntu) "[arm] needs porting to thumb2 (affects: 1)" [Undecided,Invalid] https://launchpad.net/bugs/51425513:14
asac_ok so webkit part is invalid (we can check that when we come to webkit)13:14
asac_and qt4-x11 needs atomics13:14
asac_though odd that it builds13:15
asac_NCommander: qt4-x11 builds?13:15
asac_NCommander: e.g. is bug 490371 a none issue?13:15
asac_"In debian/rules Set DEB_HOST_ARCH and DEB_HOST_ARCH_OS. Configure with "-arch armv6" option on ARM"13:16
asac_seems its built using armv6?13:16
* asac_ waits for qt4-x11 sources to arrive13:16
ograi think there was a bug cjwatson worked on13:16
ograwhich he could only solve by switching to v613:16
asac_from v5?13:17
asac_or v7?13:17
ografrom using the default (v7)13:17
dmartI think this uses LDREX/STREX, if building for ARMv6.  Originally the build system did not recognise ARMv7 and fell back to the older SWP code causing ftbfs13:17
dmartThis was since bodged to lie to the build system about the architecture version so the v6 code is used, IIRC13:18
asac_oh13:18
asac_right13:18
asac_so we might want to fix the build system13:18
asac_or leave it as it is13:18
asac_NCommander: can you fix the buildsystem of qt4-x11 to understand v7?13:18
NCommanderasac_: its on my TODO behind OOo13:19
asac_NCommander: arent you idle all the time witing for ooo to build?13:19
NCommanderasac_: no, because i don't do full builds13:19
asac_NCommander: also i think that ooo is not higher priority than thumb2 ... its same priority13:19
* NCommander just rebuilds the libraries I need, and wait at most 30 minutes for a full rebuild13:19
ograqt4-x11 (4:4.6.0-1ubuntu2) lucid; urgency=low13:19
ogra  * Make libqt4-dev depend on libx11-dev13:19
ogra  * In debian/rules Set DEB_HOST_ARCH and DEB_HOST_ARCH_OS. Configure with "-arch armv6" option on ARM13:19
ogra -- Jonathan Riddell < jriddell@ubuntu.com>   Tue, 08 Dec 2009 13:30:39 +000013:19
ograthere we go13:19
NCommanderasac_: I was informed otherwise by davidm13:19
asac_NCommander: but you wait 30 minutes ;)13:20
dmartasac_, NCommander: we should probably note down qt4-x11 for a SMP safety review13:20
asac_you can surely work on something ;)13:20
asac_anywway13:20
asac_dmart: wouldnt that show up in our greps?13:20
* ogra goes to look for Riddell 13:20
NCommanderdmart: if you have a few minutes, can you help me grok the C++ ABI?13:21
* NCommander has found where OOo blows up13:21
asac_ok i have a call in 10 ... so i think we are over13:21
asac_we are down to four packages or so13:21
dmartNot really - this is about whether barriers are used correctly.  It's mainly an issue for packages which have their own hand-crafted atomics using the ARMv6+ primitives (LDREX/STREX) where SMP may not have been fully tested13:21
asac_out of which most are fixed13:21
asac_dmart: oh ok13:21
asac_so anything using ldrex etc. is subject to review13:22
dmartIdeally13:22
asac_but afaik we grepped for ldrex13:22
dmartOh, yes.13:22
dmartI mean grep can't tell us if it's wrong; but it does identify what's worth looking at.13:22
asac_bug 45155313:23
ubot4Launchpad bug 451553 in linux-mvl-dove (Ubuntu Karmic) (and 2 other projects) "Lots of errors during install on dove (affects: 2) (dups: 1)" [Medium,Confirmed] https://launchpad.net/bugs/45155313:23
asac_dmart: right. thats what i meant13:23
dmartI forgot we grepped for that too13:23
dmartok, I guess we are pretty much done13:24
dmartUnless people have questions13:24
asac_the rest is: thunderbird -> fixed13:25
asac_upx-ucl -> i think in invalidated that13:25
asac_bug 51425413:25
ubot4Launchpad bug 514254 in upx-ucl (Ubuntu Lucid) (and 1 other project) "[arm] needs porting to thumb2 (affects: 1)" [High,Triaged] https://launchpad.net/bugs/51425413:25
asac_oh no ;)13:25
asac_but webkit:13:25
asac_bug 51425513:25
ubot4Launchpad bug 514255 in webkit (Ubuntu) "[arm] needs porting to thumb2 (affects: 1)" [Undecided,Invalid] https://launchpad.net/bugs/51425513:25
asac_bug 51425713:25
ubot4Launchpad bug 514257 in xine-lib (Ubuntu Lucid) (and 1 other project) "[arm] needs porting to thumb2 (affects: 1)" [High,Triaged] https://launchpad.net/bugs/51425713:25
asac_so upx-ucl and xine-lib are still todo for main/important13:26
asac_and the qt4-x11 smp review13:26
asac_wiki page should be more or less up-to-date13:26
asac_ok me prepares for a call ;)13:26
dmartOK, thanks13:26
NCommanderdmart: if your around in about an hour, I need to pick your brain on unwind tables, and the fun of ARM C++ exception handling :-)13:26
asac_thanks dmart for your time again13:27
ogra<ogra> Riddell, in qt4-x11 4:4.6.0-1ubuntu2 you set -arch armv6, do you remember the reason for that ?13:27
ogra<Riddell> I did?13:27
ogra<Riddell> where?13:27
asac_and everyone else ;)13:27
ogra<cjwatson> ogra: I do, it was because there was a specific armv6 implementation of some bits13:27
ogra* sabdfl hat die Verbindung getrennt (Read error: No route to host)13:27
ogra<cjwatson> the default was arm, and wasn't good for armv713:27
ogra* sabdfl (~sabdfl@ubuntu/member/sabdfl) hat #ubuntu-devel betreten13:27
asac_bug 50900613:27
dmartNCommander: Not something I know too much about, but I'll see if I can draft in someone else13:27
ogra<ogra> do you remember if it was assembler ?13:27
ubot4Launchpad bug 509006 in linux-mvl-dove (Ubuntu) "[dove] hibernation failed to resume (affects: 1)" [High,Confirmed] https://launchpad.net/bugs/50900613:27
ogra<cjwatson> the armv6 code doesn't handle multicore, but is otherwise much better than what was there before13:27
ogra<cjwatson> yes13:27
armin76spam13:27
asac_ogra: ... cant you paste tsuch huge pastes in pastebin?13:28
NCommanderdmart: that would be useful13:28
asac_bug 50900613:28
asac_bug 45163513:28
ograasac_, ah, come on ... 10 lines ...13:28
ubot4Launchpad bug 451635 in alsa-driver (Ubuntu Karmic) (and 1 other project) "Sound not working on dove Y1 board (affects: 1)" [Medium,New] https://launchpad.net/bugs/45163513:28
asac_bug 45215613:28
ubot4Launchpad bug 452156 in linux-mvl-dove (Ubuntu) (and 1 other project) ""Write-error on swap-device" while installing Ubuntu (affects: 1)" [Undecided,New] https://launchpad.net/bugs/45215613:28
ograbut yes, i'll do in the future13:28
asac_bug 45155313:28
ubot4Launchpad bug 451553 in linux-mvl-dove (Ubuntu Karmic) (and 2 other projects) "Lots of errors during install on dove (affects: 2) (dups: 1)" [Medium,Confirmed] https://launchpad.net/bugs/45155313:28
asac_bug 52714813:28
ubot4Launchpad bug 527148 in linux-mvl-dove (Ubuntu) "dove fails to shutdown (affects: 2)" [Undecided,New] https://launchpad.net/bugs/52714813:28
asac_ok that were my 10 ;)13:28
dmartogra: OK, I guess if "the armv6 code doesn't handle multicore" it needs looking at, so definitely add this to the SMP safety review table.13:31
ograyeah13:31
dmartThanks for checking13:33
ograadded13:35
ogra(if the wiki ever saves)13:36
* dmart wonders why the wiki is so slow13:36
loolasac_: I think the gcc atomics patch is uploaded already??13:39
loolIt still FTBFS but not due to thumb/asm13:39
looldmart: Suggestions on how to fix the failure are actually welcome13:39
loolIt's float comparisons and gcc logic13:40
dmartlool: which package is this?13:40
looldmart: /build/buildd/qemu-kvm-0.12.2/fpu/softfloat-native.c:373: error: impossible constraint in 'asm'13:40
looldmart: qemu-kvm13:40
loolOh13:41
loolit's actually not th eplace I thought it was13:41
loolI was looking at the wrong function the first time13:41
looldmart: http://paste.ubuntu.com/383679/13:42
looldmart: probably if defined(__arm__) && !defined(__thumb__)?13:42
looldmart: what's rndd/rnddm etc.?  I grepped the ARM asm reference card and the VFP one for "RN" and couldn't find it13:57
loolMight be some gas syntax13:57
dmartHmmm, yes, I was just looking at that13:57
dmartI think these opcodes (and the "f" asm constraint) are probably related to the obsolete FPA architecture (which is what the netwinder fp emulator code in the kernel emulated)13:58
dmartThis code won't work on any Ubuntu armel release13:58
loolcan't find it in http://sourceware.org/binutils/docs/as/ARM-Opcodes.html#ARM-Opcodes14:00
looldmart: Oh, so an older FPU?14:00
dmartYes.  Well, an older FP architecture.  I'm not sure whether there was ever much silicon implementing it...14:00
dmartYou can probably make GCC accept the code with -mfpu=fpa or something, but unless this code is being built to run inside qemu (and qemu emulates the instructions) I can't see how it's going to work...14:01
looldmart: Bah, I'm wasting our time14:01
loolthe asm was dropped upstream14:01
dmartah... good thing too :)14:02
loolfloat64 float64_round_to_int( float64 a STATUS_PARAM )14:02
lool{ return rint(a);14:02
lool}14:02
lool(can't they just errr call rint()?  :-)14:02
ograprobably something uses float64_round_to_int in the code ?14:07
ograand they were lazy14:07
persiaOr maybe they use this to force a cast somehow?14:10
loolNah I just think it's historical14:10
loolrint is C99 just like qemu14:10
dmartNCommander: looks like our tools guys aren't available this afternoon.  Would 1500 UTC tomorrow be OK for you?  I can try and grab someone for then.14:17
NCommanderdmart: that would work14:18
dmartramana: Hi14:20
dmartNCommander: Looks like someone is available after all14:20
dmartRamana has been working with some of the Ubuntu guys (doko etc.) on the tools14:21
NCommanderhey ramana!14:21
ramanahi NCommander14:27
NCommanderramana: how goes your morning14:27
ramanaNcommander: Not too bad.. it's now afternoon where I'm sitting ... It's not raining and that's a plus :)14:28
ramanahow goes yours ?14:29
NCommanderramana: early morning conference calls14:29
ramanaNCommander: sounds like fun14:31
NCommanderramana: I'm dealing with crashing on ARM with OOo with modern toolchains, which is being caused by a direct call to __cxa_throw14:33
ramanaok14:33
NCommanderramana: it begins to unwind the stack, and then blows up with a phase2 failure14:35
NCommander__cxa_throw calls std::terminate14:35
NCommanderramana: I know there were unwind table changes between jaunty->karmic (gcc 4.3 to 4.4/glibc to eglibc)14:36
ramanado you know for what frame unwind_phase2 is in ?14:38
NCommanderramana: not sure how to get that14:39
NCommanderI'm guessing is marked CANTUNWIND that shouldn't, or the inverse14:40
NCommanderramana: the stack gets completely trashed so the debugger is of limited help14:40
ramanacan you get a backtrace from the point before it hits the throw to see what the frames are ?14:43
NCommanderramana: I can try. OOo does some very very strange and evil things that make debugging it extremely difficult14:45
ramanaNCommander: The last time I tried looking at this was in September and I was stymied by not knowing enough about OOo.14:46
NCommanderramana: I think I need to do an entire debug build of the entire stack14:46
NCommanderramana: thats a multiday love affar :-/14:46
ramanayes that sounds prudent to have.14:48
NCommanderramana: unfortunately, since I don't have a small test case for this14:48
ramanaNCommander : Is this the standard OOo in the lucid packages or is this in your PPA ?14:50
NCommanderramana: I'm working upstream; saner to build14:50
ograthe std oo.o in lucid uses a jaunty lib that works around that bug14:50
ramanaok14:50
NCommander(although sanity in this case is extremely relatively)14:51
NCommander*relative14:51
ramanaNCommander: is there any place where I or dmart could have a look at your chroot or libraries ? We can try doing some disass on the libraries / binaries ?14:56
NCommanderramana: I'm just using standarding ubuntu jaunty, karmic, and lucid chroots14:56
ramanaNCommander: and the OO build tree you might have ?14:56
dmartPresumably that's just apt-get source?14:57
dmartOr are you working on something not yet in the archive?14:57
ramanadmart: I think NCommander is working on upstream OOo14:57
dmart(the bug is old though...)14:57
asacNCommander: can you tell ramana how to build the package without the jaunty workaround so they can see the actual problem?15:04
asacogra: you said doko made packages available for you15:04
NCommanderasac_: that won't be useful without being able to debug it15:04
asacthat have that issue ... did doko als opush source for that?15:04
ograasac, yes, on jocote in his home15:04
ogranot sure about the source15:04
NCommanderramana: you can cause the issue by going into /usr/lib/ure/lib, and replacing libgcc3_uno.so with libgcc3_uno.so.karmic15:04
asacNCommander: well. they want a way to reproduce. if you have a better way, then just go for that15:04
ograi always only got a bunch of .so's15:05
asacNCommander: reproduce from source that is15:05
NCommanderasac_: you have to build OOo then from scratch15:05
NCommanderhttp://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Linux#ccache15:05
loolasac: IIRC, the two binaries (really built and from jaunty) are installed in the libdir15:05
asacNCommander: package sounds esaier ,)15:06
asacdebuild -b15:06
asacwait15:06
asacwait15:06
asac;)15:06
loolasac: So the current builds of oo.o ship the borken binary in a different path15:06
NCommanderasac_: that won't work because it won't build OOo with debugging15:06
asacfine if you can reproduce with upstream instrcutions15:06
* ogra kicks and punches qemu so it has dents and wrinkles 16:12
ograi dont love you anymore you darn thing !!!16:12
* ogra goes into a corner and sulks16:13
alecrimi'm with some problem to bootup a minimal ubuntu image with N810. I freezes as you can see here http://pastebin.com/41gRjZuF17:29
alecrims/I/it/g17:29
Stskeepsjaunty?17:30
Stskeepsout of curiousity, got serial console17:30
Stskeeps?17:30
Stskeepsand you are possibly running into the watchdog17:30
alecrimStskeeps, I generated rootfs using this procedure : sudo rootstock --fqdn n810 --login ubuntu --password ubuntu --imagesize 500M17:31
Stskeepsok, so lucid?17:31
alecrimStskeeps, karmic17:31
Stskeepsmmk17:32
Stskeepsand .33 is quite experimental there17:32
alecrimStskeeps, maybe the boot finished, but it does not show the serial. Old versions of ubuntu contain a /etc/inittab that I could force a login by serial, but not this one.17:33
Stskeepsah17:33
alecrimStskeeps, any idea?17:33
Stskeepscheck event.d? should be tty*17:33
alecrimStskeeps, thanks! I'll check it. I'll try lucid version, instead of karmic next time. let me see if I can get console17:34
Stskeepsno, lucid is armv717:35
Stskeepswill not work on n81017:35
alecrimStskeeps, I didn't know :(17:37
NCommanderramana: I've tied three babbage boards and one dove board into the OOo build18:05
NCommanderWhich shoul dget drastically cut build times down18:06
NCommander^- armin76 :-)18:06
ramananice :)18:08
NCommanderramana: the issue is I'm still not sure I'm going to get a proper backtrace18:10
NCommanderramana: the UNO call pulls CXX exceptions across multiple threads/processors/evil18:10
NCommanderSo even having a proper backtrace before the throw might not help18:11
NCommanderAnd I'm not sure stepping into the _Unwind_* will give me anything I'm going to be able ot grok18:11
ramanajoy18:11
NCommander(although I'll prepare to do a debug build of libgcc)18:11
NCommanderramana: is there a good way to debug the _Unwind_* functions and friends?18:14
alecrimStskeeps, it's working. http://paste.ubuntu.com/383843/18:15
alecrimStskeeps, actually /etc/init/ttyS2.conf is the correct place18:15
Stskeepsclose enough18:15
* DanaG wonders how much power it would take to get a mere Radeon 7500 sort of horsepower in an ARM.18:15
DanaGSpecifically, for the sake of compiz.18:15
Stskeepsalecrim: does your lcd work?18:16
alecrimStskeeps, it's a basic image using linux-omap latest version(2.6.33). I got serial using a special HW from Nokia18:17
Stskeepsah, good18:18
* alecrim is a privileged person 18:18
alecrimhehe18:18
Stskeepsyeah, i have one too :P18:18
ramanaNCommander: I've never personally done this but I can dig around.18:19
NCommanderramana: that would help. Google hasn't told me a lot of phase2 unwinder failures except they exist18:20
alecrimStskeeps,  I'm gonne work to get version 2.6.33 fully working like 2.6.29 version (http://franciscoalecrim.com/blog/2010/02/05/preparing-mamona-03-sync-with-openembedded-alpha/)18:20
Stskeepscool :) even with wifi and dsp?18:21
Stskeepsi will bookmark18:22
Stskeeps2.6.33 on n8x0 would be cool18:23
Stskeepsyou saw the release of MBX 3d drivers too?18:23
Stskeepsgpl kernel driver18:23
DanaGMBX?18:24
Stskeepsomap2 3d accelerator18:24
armin76NCommander: cheater18:26
NCommanderhehe18:26
Stskeepsalecrim: you have git tree for kernel somewhere?18:26
Stskeepsfor your patches18:26
NCommanderarmin76: there is somethng for being able to simply throw more hardware at a problem18:30
DanaGwhat I have is the beagleboard.18:32
ssvbalecrim: there is user luke-jr on #maemo and #gentoo-embedded channels and he tried to do something with the latest kernels on N810 too (at least he was the last to update http://elinux.org/N800 page)18:33
* armin76 prefers to throw NCommander at the problem and keep the hardware18:35
alecrimStskeeps, linux-omap tree. I sent patches with corrections a few weeks ago.18:52
Stskeepsk18:53
* NCommander sighs18:59
NCommandertrying to build OOo from source is like trying to drive in reverse on I-90 from Boston to Seattle18:59
armin76thats how is it on arm :)19:01
armin76you should be glad you don't have to work with a marvell orion and the like19:01
Martyn*ugh*19:29
MartynNo, building oOo is rally a pain in the ass19:29
MartynI'm still trying to build various MPI applications and libraries for our platform19:30
Martynand it's NOT fun19:30
MartynPlus I still have no work from Pegatron how the heck I can restore the image on their i.mx51 whitebox ( similar to the genesi box )19:30
DanaGPegatron as in split-off-from-ASUS?19:32
DanaGPegatron sounds like an el-cheapo brand... it's a bad choice of name, in my opinion.19:32
ojnMartyn: just boot from external SD card. $20 of hardware saves you how many hours of work?19:32
Martynojn : It's not booting19:32
Martynojn : And I have no debug cable so I can't change the configuration of the u-boot19:33
ojnMartyn: if you change the switches it'll load u-boot from SD19:33
Martynah!  That's new info19:33
Martyn0001?19:33
ojnCan't remember and I'm not in Austin this week19:33
Martynno worries19:33
ojnMy offer of borrowing the debug card also holds, but I guess it's more fun to fumble in the dark. :)19:33
MartynI forgot you were in the same city as me :)19:35
MartynWhen you're back, ping me19:35
armin76ojn: it is!19:37
NCommanderMartyn: well, at least I managed to isolate the crash19:44
NCommanderFixing it still going to be a real trick19:44
NCommanderMartyn: try using ooo-build, I think it will make it easier19:44
ChocoboDo any of you know of a good tutorial for interworking ARM and THUMB code?  For example... if I have a bunch of C code I want to compile in ARM and a small ASM routine I want in ASM...  what I need for compile flags20:24
loolChocobo: You can get the actual architecture reference manuals from arm.com, if you register and accept the license20:33
ogralool, no go with rootstock :( ... installing an ubuntu-netbook task makes qemu hang in iso-codes ... just installing iso-codes works fine though21:01
* ogra wasted the whole day on it and is out of ideas21:01
=== fta_ is now known as fta
|nfecteDqemu is whacky21:07
|nfecteDlocked up here too when i gave it too much to chew on21:07
ograit wasnt for the last two releases21:07
|nfecteDanyway... got it to build my rootfs when i removed lxde and gde from the seed21:09
ograright, minimal isnt a problem21:09
|nfecteDmmhmm21:09
|nfecteDnot that the damn thing wants to boot on my beagleboard21:09
|nfecteDinit: plymouth main process (625) terminated with status 7121:09
|nfecteDand such21:09
|nfecteDyay21:09
|nfecteDguess i'll try another kernel just for hell of it21:12
asacdyfet: hey23:02
asacdyfet: so you wanted to discuss mono ;)?23:02
* persia notes that the easiest way to get a high-end GFX card on armel is to find hardware with PCIe slots.23:05
dyfetyea, I see several different issues23:06
* persia also notes that "Pegatron is a cheap brand" is somewhat tricky to parse, as Pegatron is one of only 5-6 companies that build 96% of laptops shipped worldwide and not the one with the least market share23:06
asacdyfet: so lets talk ;)23:15
asacdyfet: where would you start? i thought looking at the failed test cases and then understanding why the fail might be a good way to start23:16
dyfetI was not aware of the status of that.  But I am also concerned what does it currently block building23:17
asacdyfet: i dont think it blocks anything from building23:17
asaconly problem is that the runtime behaviour is borked23:17
asacwhich makes good chunk of the archive unreliable to use ... which is bad ;)23:17
asacluckily mono hasn't spread out that muc in the archive, but still there are apps we would like to have working ;)23:17
dyfetout of curiosity, have the test cases also failed in qemu arm build?23:26
asachavent tried to build it there yet23:28
dyfetbecause it might offer an environment for testing where people don't have hardware, if it reproduces the behavior23:29
dyfetwhile pulling down latest which tests do fail?23:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!