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

loolpersia: Wow flags: OC in /usr/share/binfmts/qemu-arm09:29
loolbut flags: in /proc09:30
loolPff someone typo-ed that09:30
loolpersia: Just after fixing flags, it works09:36
loolpersia: I can sudo09:36
loolNo change needed to qemu09:37
persiaHeh.  It takes a night's sleep to try the obvious :)09:40
loolpersia: LP #51922811:00
ubot4Launchpad bug 519228 in binfmt-support (Ubuntu) "Support for C flag (affects: 1)" [Undecided,New] https://launchpad.net/bugs/51922811:00
persiaI saw the discussion in -devel.  Looks promising :)11:01
* persia presses the "me too" button11:01
lool(works here)11:01
ograsudo worked for me yesterday btw ... i only had a hostname not found warning11:03
persiaogra: OK.  Were you root at the time?  Based on the docs I read 12 hours back, it couldn't have worked.11:05
persiaBecause all setuid bits are being dropped by the binfmt_misc handler.11:06
* persia notes that opening a chroot whilst not being root can be tricky11:07
ograpersia, i have to be root to chroot :)11:09
ograwell, i usually dont use fakechroot or fakeroot :)11:09
* persia uses schroot11:09
ograah, right11:09
persiaThe other option is to do something like sudo to some unprivileged user inside the chroot.11:10
ograwhoops, i just dropped off the canonical server11:10
ograhmm, and LP doesnt respond11:11
ograheh, that just looked like a loose cable in the DC ... all back :)11:11
loologra: Try su - someuser in your chroot, and then sudo something11:21
loolIt wont work11:21
loolSee above bug11:21
ograyes, i just read it11:23
ogralool, btw, do you see something like http://paste.ubuntu.com/371902/ trying to start any gtk apps in qemu ?11:23
loologra: Did you file a bug?11:24
loolI didn't try running gtk+ apps11:24
ogranot yet, i was researching oem-config and ran into it ... wanted to see if its only me or a missing dep in my minimal setup rootfs11:25
loolWould anybody be interested in doing the reverse of the cleanup I did to the qemu versatile config?11:26
ograthe reverse ?11:27
loolBasically there are some configs which I turned on and ended up being armel specific (or versatile specific; it's the same) but are useless and should be turned off again11:27
loolTo minimize delta with other Ubuntu configs11:27
loolFor instance CONFIG_MTD doesn't actually work with qemu/versatile, so could be turned off to reduce delta11:27
* ogra doesnt really care as long as there are no lockups or other bad breakage11:27
loolFlags in debian.master/configs/armel/flavour.versatile should be examined11:28
ograand i'm sure the kernel team wont care either unless they actually get a patch11:28
ograif something gets in my way i'll research the issue and make a change, but if its just a silent delta i'm really not concerned11:29
ogralool, i'm currently more worried about the glibc failure i have seen and start to suspect its caused by the v7 hack we use11:32
ograsince it only fakes the v7 CPU but doesnt actually add the features cpuinfo exposes (i.e. neon)11:33
ogra(not that i have run any neon capable apps, but you know what i mean i guess)11:33
loolcpuinfo doesn't matter for neon11:39
loolI just got the double free (fasttop) error when installing packages11:52
loolIt's not specific to gtk+ apps11:52
loolIt was during the ldconfig trigger11:53
loolstartx segfaults in Xorg here11:55
loolI also get it with gtk-demo in Xorg12:04
ograstartx works for me if i just use xterm12:08
ograas soon as i use a toolkit it breaks, plain X seems to work12:08
loolI get a segfault when Xorg quits12:08
ograyay, imx51 with populate_rootfs \o/12:08
loolTry running startx, leaving  your session; do you have a segfault in /var/log/Xorg.0.log?12:08
* ogra hugs ApOgEE__ 12:08
ograopps12:09
ograapw i meant :P12:09
apwogra, ?12:09
ogralool, only if i use toolkit based apps12:09
apwogra, thank me if it boots for you12:09
ograapw, <ogra> yay, imx51 with populate_rootfs \o/12:09
ograi will as soon as i can get it from the archive :)12:09
apwheh, lets hope it builds in there :)12:10
ograwow, that changelog looks like someone nearly rewrote ext4 :)12:10
apwheheh12:11
ogralool, i have no segfault with an .xsession that just contains xterm12:11
loolapw: This is boot speedup work for imx51?12:12
ogralool, for ubuntu in general12:12
loolOh and it was borken on imx51?12:13
ograit just didnt make it in yet12:13
apwits a rebase for security and stable updates, plus a couple of patches from brian for performance12:13
apw(boot performance)12:13
ograwe try to get all the sweetness from our mainline kernel backported now that the patches dont create any hassle12:13
ogralool, the fsl patchset just applied smoothly this time so we actually have time for kernel improvements which we try pull in as many as we can from the ubuntu kernel12:14
apwdunno if you will gain anything with such cpu limited platforms, i assume brian tested it and measured it before asking for it12:14
ograno weird forward porting makes everything so much easier12:14
apwshame they still frig about in usb, and then wonder why usb drives fail to work properly12:15
ograwell, the devtmpfs backport surely gained us a lot already12:15
ograso i'm suspecting the populate_rootfs stuff will too12:16
apwogra, 'surley' ... i am guessing noone tested12:16
apwogra, in my experience its not a gain if you only have 1 cpu12:16
ograi did and see 2-3 sec speedup12:16
persiaapw: Note that there exists Ubuntu-compatible hardware for other architectures with even less CPU performance than most available ARMv7 hardware.12:16
apwpersia, indeed, but we are not targetting any specific performance for them12:16
ograare you talking celeron without L2 cache ? :)12:16
* ogra has such a thing and its slower than my babbage board12:17
loolapw: I did test devtmpfs with 2.6.32 kernels in qemu, and I can say the MAKEDEV was taking more than 5 seconds in qemu12:17
loolapw: BTW, there are further MAKEDEVs on startup ATM, perhaps we could add more devices to devtmpfs and avoid one more call?12:17
apwsaved about .2s on a real machine as i recall12:18
loolapw: /etc/init/mounted-dev.conf still calls /sbin/MAKEDEV fd in all cases12:18
persiaogra: That would be but one example of a large class :)12:18
ograi dont think it was produced in large amounts actually12:18
loolapw: Also, I wonder whether we could avoid remounting devtmpfs on top of devtmpfs; that's probably not very long, but still...12:18
apwkeybuk deals with all that side, i thought all devices were made which were registered in the kernel12:19
loolI get the glibc corruption with a minimal gtk+ program which does gtk_window_new + widget_show_all + gtk_main, but not without the window12:24
loolSetting MALLOC_CHECK_=0 I can actually run the app12:26
asacericm_: -meeting?13:18
loologra: I definitely get the segfault when exiting from xterm13:25
lool"startx" startx an xterm, I ^D and I get a segfault13:26
ograhmm, i didnt have one yesterday13:26
looldmart: Hey13:54
looldmart: I have this glibc errors which ogra mentionned13:54
looldmart: I wrote a trivial gtk program which reproduces these13:55
looland it aborts but, the backtrace is either useless or useless13:55
looldmart: I've installed our -dbgsym packages for libc6, libx11-6, gtk, pango, and cairo13:55
loolI even got a gdb segfault at some point, but not consistently13:55
looldmart: How would I track this down?13:55
loolI can break on main() in gdb, but when I get the actual abort, it's somewhere down the gtk internals, and it's hard to break on that13:56
loolAh!  G_SLICE=always-malloc also fixes the bug13:58
loolSo it's either a bug in glib'c gslice support on armel, or in glibc's memory checks on armel13:58
dmartAdd some trace I guess, if you can't get a backtrace from the segfault/abort.14:00
loolWhat do you mean by add some trace?14:00
dmartDon't really have bright ideas here I'm afraid14:00
looldmart: Do you find gdb useful on armel these days?14:00
loolIt frequently crashes for me14:00
dmartWhich version are you using?  lucid's gdb seems a lot more stable than karmic's gdb, but maybe I was lucky.14:01
loollucid's latest14:01
lool7.0 helped, but it's still crashy and frequently fails finding backtrace14:01
loolIn this case, I get either a corrupted backtrace or an infinite loop14:01
dmarthmmm, is there any way you can reproduce the crash?  I often get no backtrace though.  I wondering whether some components are built in a way which nukes the backtrace; or maybe there's some broken unwind info support in gdb.14:02
loolThe crash only happened one time out of 6 or so, but perhaps I will be able to reproduce it14:03
loolI suspect the versatile kernel under qemu might be having some issues of its own which don't help gdb14:03
dmartMaybe you can catch it with nested gdb14:03
looldmart: So you gdb gdb?14:04
dmartI'm sure I've managed to do this in the past.  gdb has special support for this.14:04
loolOk; never tride this14:05
loolA simple g_slice checks works14:07
loolFolks, the glib atomics patch was removed in january14:07
dmartHmmm, maybe we need it back in?14:08
loolI suspect we do, that might explain my issue14:09
dmartAnyway why it was pulled out?14:09
loolIs https://bugs.launchpad.net/bugs/491342 the correct reference?14:09
ubot4Launchpad bug 491342 in glib2.0 (Ubuntu) (and 1 other project) "assembly fails to build on armel/lucid (affects: 1)" [Critical,Fix released]14:09
lool  * debian/patches/70_glib2.0-gatomic-arm.patch:14:09
lool    - dropped since that patch was added without details nor reference14:09
lool      to a launchpad or upstream bug and it's not clear if it's still required14:09
lool      now with the change done upstream recently14:09
loolSeb, who removed the patch, had fixed it when syncing 2.23.1-1 over:14:10
lool  * debian/patches/70_glib2.0-gatomic-arm.patch:14:10
lool    - change to fix the build for armel14:10
dmartIf the change is upstream, it shouldn't be needed; maybe take a look at the patch and make sure the relevant changes are in the code?14:10
loolYes; glib wouldn't build without it, would it?14:11
dmartProbably not... it was a swp issue14:11
loolIt built on armel14:11
loolhttps://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/491342 was forwarded at https://bugzilla.gnome.org/show_bug.cgi?id=60378014:12
ubot4Launchpad bug 491342 in glib2.0 (Ubuntu) (and 1 other project) "assembly fails to build on armel/lucid (affects: 1)" [Critical,Fix released]14:12
loolWhich points at https://bugzilla.gnome.org/show_bug.cgi?id=531902 which is closed14:12
ubot4Gnome bug 531902 in general "Use GCC atomic buildins for g_atomic*" [Enhancement,Resolved: fixed]14:12
lool  Bug 531902 -  Use GCC atomic buildins for g_atomic*14:12
loolSummary: Use GCC atomic buildins for g_atomic*14:12
ubot4lool: Error: Bug #531902 not found.14:12
* persia pets ubot4 for trying14:12
dmart:)14:12
dmartLooks like it was fixed upstream, so long as ubuntu's package is now based on the new enough version.14:13
loolIt's merged in out glib2.0 ubuntu package14:13
loolchecking whether to use assembler code for atomic operations... checking whether GCC supports build-in atomic intrinsics... yes14:13
dmartlooks good14:13
dmartPerhaps your problems are caused by something else...14:14
* dmart has do disappear for a bit14:14
* dmart also can't spell14:14
loolI looked at the testsuite, there is one failure trying to create files in the non-writable home, another one on threadpool-test14:15
looland there might be more since it doesn't complete14:15
loolslice-test does pass though14:16
loolSo it could also be a gtk+ issue14:16
loolIn gtk+, the only failing test is abicheck; again the testsuite might not be running all tests14:17
ogralool, it couls also be a codesourcery issue, lets wait for the actual archive build of versatile14:30
* ogra still thinks its kernel related14:31
loolI have the same issues with my own cross-gcc14:33
loolWhich is based on a relatively recent FSF tree14:33
ograhmm14:33
loolHmm it's not the same error as with ldconfig14:35
loolldconfig was on fasttop, gtk+ is on !prev14:35
ogralets be patient and see what an in-archive kernel brings us :)14:36
loolThere's an experimental-malloc in eglibc which takes another code path14:40
loolMALLOC_CHECK_=0 G_SLICE=debug-blocks doesn't catch the error14:43
loolAh slice-test actually fail under my kernel14:54
looldmart, ogra: Could one of you try on real hardware with lucid userspace?14:54
loolTo check whether it's a toolchain or kernel regression14:54
ogralool, i have no issues at all on imx5114:55
ograsince weeks14:55
looljust build slice-test from glib2.014:55
ograi'm not sure i can get to that today but will do so if nobody else does14:55
ogramy babbage is fully swamped today14:55
=== 18VAACOTE is now known as Meizirkki
dmartI'll have a go... what's the easiest way to build just the affected test?14:56
looldmart: unpack memchunks.c and slice-test.c from glib2.0's tests/14:56
looldmart: And then basically gcc `pkg-config --cflags glib-2.0 gthread-2.0` -c memchunks.c14:57
looldmart: And then basically gcc `pkg-config --cflags glib-2.0 gthread-2.0` -c slice-test.c14:57
looldmart: And then basically gcc -o slice-test *.o `pkg-config --libs glib-2.0 gthread-2.0`14:57
lool(Sorry for the noise)14:57
loolSo ./slice-test 1 c 100 works and ./slice-test 1 c 1000 fails14:58
dmartok, I'll let you know what happens.14:58
loolIt works up to 512 and fails starting at 51314:58
looldmart, ogra: What's the kernel memory allocator on your kernel?14:58
loolIt's SLAB on versatile14:59
loolI think ARM requires SLAB anyway14:59
dmart /boot/config.blah says CONFIG_SLUB=y15:00
ograyeah15:01
dmartdunno whether that's better though15:01
looldmart: There was a recent post of slab versus slub on kernel-team@lists.ubuntu.com15:08
loolI don't know whether it's better or worse, but I care that it works or not   :-)15:08
loolversatile_defconfig has SLAB=y instead15:08
loollpia, i386, amd64 and ports have SLUB=y; pretty much only versatile has SLAB=y15:09
* dmart is still updating his fs15:09
dmartThe versatile is probably derived from the ARM kernel trees, which tend to use a more traditional/embedded style config (for whatever reason)15:10
* lool tries turning on SLUB15:10
loolOk; that worked, let's see if I can build a working kernel with it15:12
loolit built, but for some reason I'm missing disk drivers; /me tries again15:23
=== asac_ is now known as asac
loolSo it still fails15:35
loolI have CONFIG_SLUB=y15:35
loolSame symptoms15:36
looldmart: Did you manage to test on real hardware?15:37
dmartnot yet... trying to do too many things at the same time...15:40
dmartargh, more update problems15:41
loolWhat's the issue?15:41
armin76ricing15:42
dmartAny idea what's causing the contents of the archive to be broken at the moment?  I get a load of conflicts15:42
looldmart: I don't have that15:42
looldmart: Perhaps some packages you have are missing on armel; I have a minimal chroot15:42
ogramono15:42
loolYeah I was about to mention it15:43
loolCurrently mono-runtime is older than mono-gac15:43
ogramono breaks the world and the desktop team made half the world depend on it15:43
loolSo you can't install mono or ubuntnu-desktop15:43
ograso lots of stuff is outdated15:43
ograasac, is working on the mono ftbfs15:43
dmartHmm, I didn't even find that among the conflicts.  But trying to install/upgrade ubuntu-desktop is certainly broken right now.15:43
ograright15:43
ogralaincpad-integration and all the indicator- stuff are broken15:44
ograanything that uses either will likely fail to install15:44
dmartIs that really all caused by mono?15:44
ograyes15:44
dmartargh15:44
ogramost of the indicator bits hard depend on mono now15:44
loolOddly it took 2 hours to build in karmic and has been building since 3 hours in lucid15:45
ograas well as LP-integration15:45
loolLooks like the build hanged in configure15:45
ograoh, and nautilus depends on mono as well now15:46
asacmono is a mess15:46
asacit opens zillions of files ... but only on arm15:46
loolasac: Does the buildd output looks normal to you?15:46
ogralool, forget about the buildd :)15:46
loologra: ?15:46
asaclool: what do you mean?15:46
ografor now we'd be happy to be able to build on sane HW we have full access to15:46
asaclool: i tried it locally and found that we hit the 1024 open files barrier15:46
loolasac: https://launchpad.net/ubuntu/+source/mono/2.4.3+dfsg-1ubuntu1/+build/147742115:46
asaclool: no. that doesnt look normal15:47
dmartlool, looks like a won't have time to try and reproduce your issues right now15:47
asacand isnt what usually happened15:47
looldmart: Ok; thanks15:47
loolI'd love to know whether this is kernel specific or not15:47
dmartsorry15:47
* ogra smells one of the regular buildd segfaults15:47
asacyeah15:47
loolPerhaps someone else could try it on real hardware with up to date lucid?>15:47
ograasac, you gave it back today, didnt you ?15:48
asaci tried it on real hardare15:48
asacsame issue ... open files barrier15:48
asaci am now going to debug that15:48
ograasac, i think lool means the qemu issue15:48
asacunfortunately i trashed the build tree15:48
loolasac: Did you complete a build after bumping the open file limit?15:48
asacoh15:48
asacsorry15:48
asaclool: no it failed later on jocote15:48
loolYeah, I have an issue with glib under qemu15:48
asachavent tried to finish it here ...15:48
loolasac: Ah so no mono anytime soon15:48
loolI wanted to look into the double binfmt issue15:49
asacwill do that after confirming for the mono guy which mono it is15:49
asacwhich files are kept open15:49
loolconfig.status: creating mono/arch/s390x/Makefile15:49
loolmake: *** wait: No child processes. Stop.15:49
loolmake: *** Waiting for unfinished jobs....15:49
loolmake: *** wait: No child processes. Stop.15:49
loolSession terminated, killing shell... ...killed.15:49
ograyes, we see frequent random segfaults on the buildds since a while15:50
asacthats not the real issue. most likely just random buildd bustage as ogra said15:50
loologra: Is there a bug about the mono-runtime binfmt format that doesn't work with qemu?15:54
ograno, there are plenty in debian i think15:55
ograthey all point to syscall 242 though which is nonsense15:55
ograget_sched_affinity()15:56
loologra: could you file a launchpad bug?15:57
ogralool, i filed the one on the possible use of binfmt_ vs non binfmt_15:57
loolWhat is that?15:57
* ogra cant remember the number15:57
ogralool, bug 42786315:57
ubot4Launchpad bug 427863 in linux (Ubuntu) (and 1 other project) "binfmt allows breaking out of chroots due to not respecting namespaces (affects: 1)" [Medium,Incomplete] https://launchpad.net/bugs/42786315:57
loologra: That one is blocked on information on your side15:58
loolUpstream and Kees both asked you for more info15:58
ograwhich i dont really have time for to gather atm15:58
loolSince September?15:58
ograyes15:58
ogradmart, btw, do you use update-manager ? my upgrade works fine here just removes some stuff i'd rather keep, but still16:12
dmartNo, that was via apt-get dist-upgrade.  I should probably switch to apt-get upgrade so it doesn't unexpectedly uninstall half the system :P16:13
ograyou are not using netbook yet i guess16:13
ografor me only two indicators, rhythmbox, nautilus and the netboot-meta package are removed16:14
ograstuff i can live with until it comes back16:14
loolGah karmic userspace doesn't boot with devtmpfs16:17
loolThis so sucks16:18
suihkulokkiiirc the problem with mono in qemu is that it uses boehm gc which reads /proc/self/maps16:18
loolsuihkulokki: that's a good point16:18
loolsuihkulokki: Do you have any clue on the slice-test issues I have (see above)16:18
loolIt's under qemu-system-arm with a versatile kernel, not qemu-arm-static16:19
suihkulokkihavent seen any such issues16:19
loolsuihkulokki: You can run gtk+ apps fine under qemu-system-arm/versatile?16:19
suihkulokkiwell, haven't tried versatile for ages16:20
loolYou're using OMAP?16:20
suihkulokkibut on omap2/omap3 no problems with our gtk16:20
ograis omap stable already ?16:20
loolyeah, I've been tempted to switch to OMAP kernels for qemu16:21
loolsuihkulokki: So which tree do you use to run qemu/omap?  plain upstream, or do you need linux-omap for qemu too?16:21
ograis there enough in upstream to make use of it for qemu ?16:21
suihkulokkiso far I've just used linux-omap kernels.16:23
loolsuihkulokki: You're using the maemo OMAP3 qemu support?16:23
ograsad, no distro option for us atm16:23
loolI see some commits from you, so I guess you do  :)16:24
loolYou probably develop it too16:24
suihkulokkiyep16:25
suihkulokkiogra: ...didn't stop you from shipping mx51 and dove kernels ?16:26
ograsuihkulokki, no, but for other arm stuff we can only refer to mainline, for these two arches the kernel team made explicit exceptions16:27
ogras/arches/subarches/ :)16:28
persiaDoes mainline linux-omap work on qemu cleanly?  Might be easier to align, rather than chasing -versatile.16:30
* ogra files bug 51939817:10
ubot4Launchpad bug 519398 in oem-config (Ubuntu) "oem-config with debconf frontent goes into endless loop (affects: 1)" [Undecided,New] https://launchpad.net/bugs/51939817:10
ografinally some progress ...17:11
ograseems its actually an oem-config bug17:11
ographew17:11
persiaCan you replicate with a normal desktop install, or does it only happen with rootstock?17:15
ograno idea, i wont do any normal desktop install atm17:15
ograsince i a) dont have a spare desktop machine to test on and b) it takes extra time :)17:15
* ogra wonders why others sponsor fixes to rootstock ... why dont file people bugs so i can sponsor it :P17:16
ograpersia, though given that the debconf frontend isnt used on desktops it would have to ba a server install i guess17:18
ogra*be17:18
persiaDoes -server support oem-config?17:19
ograyes17:19
persiaAha.  Make them do the testing on !armel :)17:19
ograyou can do oem server installs nowadays apparently17:19
ograhow without HW and broken qemu ?17:19
ograi guess they are using it very rarely :)17:20
ograprobably even only testing it on x86 for milestones17:20
* ogra cant belive there is a thread in ubuntu-users about /bin/flase being to big17:22
persiaI thought they had working kvm.17:22
ogra*false17:22
persiaheh :)17:22
ograits like 50 mails already17:23
ogranearly beats the "OMG OO.o was dropped by canonical" one17:23
ograrm /17:28
ograoops17:28
persiaUm, did you really mean to run that locally?17:32
persiaThat command is usually followed by a ping timeout17:32
ograheh, no i hit tab and was on an SD card subdir in another term :)17:34
loolhaha18:02
loolthe slice-test issue doesn't affect karmic18:02
loolSo it's either a toolchain regression or a qemu bug with thumb218:02
loolsuihkulokki: ^  :)18:02
loolsuihkulokki: BTW do you use thumb2?18:02
loolI know you use NEON heavily, but I'm not sure you went through the thumb2 pain yet18:03
loolIt's eglibc18:25
loolWell upgrading it breaks things at least18:25
ografunny that we dont see it on real HW18:27
loolIt might be a bug in qemu or linux/versatile with thumb218:28
ograyeah18:28
ograi find versatile most likely18:28
ograwe just patch the CPU naming but nothing of the instruction set at all18:28
ograanyway, break before the call18:29
cwillu_at_workthere isn't a thermal sensor on the beagle is there?19:20
ogrause your thumb ?19:20
ogra:)19:20
cwillu_at_workI can't log my thumb :p19:20
cwillu_at_workalso, when setting mpurate=720, how does one also bump the voltage, or is the recommendation to do that obsolete?19:23
therealgalenHey, I'm looking for vendors who produce high-performance ARM CPUs for use with Linux... who's out there?20:02
cwillu_at_worklike, ti?20:02
ojntherealgalen: depends on what you consider high performance to be. everything is relative.20:02
ografreescale, marvell, qualcomm20:02
therealgalenI'll get clearer20:03
therealgalenI'm looking for ARM CPUs with PCI-Express support. Examples: Marvell 88F6282 (1.6-2 GHz), Marvell MV78200 (800 MHz - 1 GHz dual core), Cavium Networks CNS3420-700 (700 MHz dual core)20:06
therealgalenojn, ogra, cwillu_at_work: does that give you a better idea the performance range I am looking at?20:07
ojntherealgalen: Marvell is the only provider with pci-express solutions to date, I think. most others are targeting mobile devices where there's less need for high-performance interconnects.20:08
therealgalenojn: Cavium has PCI Express too20:08
therealgalenI'm trying to find if there are any others20:08
ojnCavium makes ARM processors? I thought they were mips20:08
therealgalenWithout wading through the 300+ ARM licensees20:08
* ogra has only seen marvell boards with PCI 20:08
ojnogra: dove has pci-e20:09
ograand i'm not even sure these ones were PCIe20:09
therealgalenhey, a few starting points are better than 300+ :)20:09
therealgalenojn: what is dove?20:09
ojntherealgalen: if PCI-e is a hard requirement, and ARM is a soft requirement, take a look at Freescale's PPC offerings as well.20:09
ojntherealgalen: The eval board for marvell's armv7 chip20:10
therealgalenah20:10
therealgalenojn: is it at all price competitive?20:10
ojntherealgalen: I have no idea where any of the vendors price their parts20:11
therealgalenthe CNS3420-700 costs like $17/unit in 1k quantities20:11
* cwillu_at_work should stop asking beagle specific questions in #ubuntu-arm20:11
cwillu_at_workogra's tongue-in-cheek response makes sense now :)20:12
therealgalenman, powerpc...20:13
therealgalena blast from the bast20:13
therealgalen*past20:13
ogracwillu_at_work, nah, there are ,many people using our userspace on beagle :)20:13
cwillu_at_workogra, I know, I'm one of them :p20:14
cwillu_at_workI just didn't realize I was in this channel:  I don't expect hardware questions to get good answers here :p20:14
therealgaleni'll just take whatever i can find, haha20:15
ogracwillu_at_work, pfft20:15
cwillu_at_workogra, you told me to use my thumb when I asked about the thermal monitor :p20:15
ograwell its a reliable methot to measure ... at least in the blister/no blister area of precision ;)20:17
ogra*method20:17
ogracwillu_at_work, but you are right, i could tell you more about imx51 than omap currently my beagle B3 is sitting on the shelf collecting dust20:22
therealgalenojn: freescale's CPUs are very expensive!21:10
therealgalenat least the PPC line21:10
persiaogra: Did you ever find a good way to suppress the extensive "qemu: Ubsupported syscall:" lines?21:47
loolpersia: Implement them?  :)22:42
persialool: Well, that works too.  ogra was talking at some point about some way to collect them and report each one only once or something.22:44

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