=== bjf is now known as bjf-afk === ogra_ is now known as ogra === jiteshs is now known as jitesh_afk === plars_ is now known as plars === ericm is now known as ericm-Zzzz [16:45] i hear someone was working on maemo in ubuntu. stil true? [16:48] pwnguin, Have a look at Mer http://wiki.maemo.org/Mer [16:50] ive seen mer [16:50] i just grabbed a vbox image last night === Q_Continuum_ is now known as Q_Continuum [18:56] Martyn: 9.10! [19:13] lool: Do you happen to have info on what the different DIP switches on the pegatron/efika control? No silk screen info. :( === lbt_ is now known as lbt [20:55] Is ubuntu 9.10 supported on the ARMv5te architecture, or is what I've been hearing true that it requires ARM6 or later with vfp? [20:55] ogra: ^ [20:58] Karmic is ARMv6 and above [20:58] (big difference between ARMv6 and ARM6 :-) [20:59] right, v6 is what I meant. As in, won't run on v5te without vfp [21:00] any particular reason ? debian still supports v5te iirc [21:01] I run ubuntu on my sheevaplug (which is ARMv5te-based without a vfp), and was hoping to be able to do a straight dist-upgrade instead of having to completely wipe and load a new disi [21:01] *dist [21:02] darkstar62: unfortunately that's not possible. It is a bit of a bummer since the sheevaplug is a neat platform, too bad Marvell had been lagging behind on the architecture for so long. [21:04] is it lack of resources to maintain the two that's the problem? I'm kinda surprised there would only be the one release for v5 [21:04] eFfeM: v6 is needed for SMP (A9) [21:05] No lock primitives in v5 I think? [21:05] hmm, I could be wrong on that though [21:05] since there's v5 smp chips. :) [21:05] ojn no idea about whether there are lock primitives [21:06] but guess this means non-smp support is drooped ? [21:06] I don't see why that would be dropped [21:07] as you said v6 is needed for smp [21:07] yes? [21:07] there are v6 non-smp systems too [21:07] sure [21:08] but if you can have systems w/o smp then why could armv5te not be supported ? [21:10] No idea. It probably makes sense from a business decision though; especially if the chip vendors are paying for the ports. It's bad marketing for them to say "get this distro we sponsored that doesn't take advantage of our hardware". [21:10] indeed [21:16] well, if that's the case, could the community work with the ubuntu devs to support armv5? [21:16] Is anyone stopping you? [21:17] I have no idea, but anyone is free to do their own spin [21:17] I was thinking more alongside ubuntu to have a ubuntu version for armv5 instead of a spin-off or fork [21:17] I'd just run debian on it though. since it's headless, and alot of the differentiation between ubuntu and debian is on the desktop, you're not missing all that much [21:18] mm, true [21:18] I moved back to debian when ubuntu abandoned ppc (for my ppc boxes), and I'm not missing much. [21:18] ojn: thing is the plug comes with ubuntu :) [21:19] yeah, I'd have to completely re-image [21:19] which I can do, I had just hoped I wouldn't have to [21:19] ah [21:19] bummer [21:20] darkstar62: compiling the entire archive for armv5 would be a bit pointless don't you think? [21:20] yep, ironic :) [21:20] (since debian already supports it) [21:21] for headless-operations I'd agree [21:21] but there are some shivaplug users using usb video/keyboard/mouse combos to use it as a desktop [21:21] debian has desktop as well :P [21:21] true [21:22] it would require an archive for armv5, optimised v6 and (who knows) in the future armv7 and so on [21:22] but there again, the shiva plug comes with ubuntu, so they'd have to completely reinstall [21:22] sounds like something you should talk to the shiva plug providers about [21:22] darkstar62: you have to blame marvell for that :) [21:22] did they coordinate with canonical? [21:22] my guess is no, since it's not supported officially by canonical [21:23] right [21:23] so they're on their own [21:23] and yeah, definitely it's marvell's issue on that [21:24] amitk: well, really all it would take is to provide something at a low enough common denominator. With glibc multilib support some of the perfomance can be recovered (but not all). [21:24] well, I guess if there isn't much call for an armv5 port outside some shivaplug users, it doesn't make sense to setup a whole system for just that [21:25] amitk: i think the next after karmic is armv7 only [21:26] armin76: would make sense to be able to move to thumb2 [22:46] armin76: some folks with ubuntu cloaks said otherwise, btw === ApOgEE__ is now known as ApOgEE