[00:40] <infinity> hrw: I can haz a linux-meta-chromebook to go with this kernel?
[05:44] <hrw> infinity: will make such
[07:52] <dholbach> good morning
[11:35] <hrw> infinity: linux-meta-chromebook uploaded
[14:39] <dholbach> can somebody please reply to the comment on  https://plus.google.com/u/0/109795858099658821877/posts/JKQWnaRVqC1?cfem=1 ?
[14:40] <ogra_> will do if i'm on a sane machine
[14:41] <ogra_> (nexus7 isnt so great for typing ;) )
[14:55] <fly-away> any tablet isnt so great for typing afaik
[14:55] <fly-away> even ipad
[15:01] <ogra_> its fine, i use it for hours every evening (i banned all other machinery from my living room)
[15:01] <ogra_> but not for answering posts with long texts :)
[15:04] <VarmVaffel> I'm trying to use a regular C write() operation on a i2c bus, but it keeps timing out
[15:04] <VarmVaffel> could this be because the bus is always too busy, or would I get other error messages then?
[15:06] <VarmVaffel> Im' using the /dev/i2c interface
[15:28] <dholbach> thanks ogra_
[15:29] <ogra_> welcome
[15:29] <ogra_> might be that he uses an old version of the dual boot image
[15:29] <ogra_> that had issues with kernel updates
[15:30] <dholbach> ah yes
[15:31] <ogra_> (fixed in newer versions of that image, Tassadar is very responsive to fixes :) )
[15:34] <Tassadar> well, at least that I can do)
[15:50] <sveinse> Why wouldn't the kernel allow me to umount something I've just mounted in initramfs (local-premount)? I'm getting Device or resource busy
[16:01] <ogra_> sveinse, lsof ?
[16:01] <ogra_> or fuser
[16:02] <sveinse> well neither is included in initramfs afaiks
[16:05] <sveinse> hmmm. "error: couldn't mount because of unsupported optional features (240)" <-- that is probably why I can't umount it afterwards. Perhaps mount needs to be told explicitly that this is ext4 not ext2
[16:07] <ogra_> no
[16:07] <ogra_> if you dont specify a fs the kernel just loops over all the ext* ones
[16:07] <ogra_> these messages are from probing, not from the actual mount
[16:07] <sveinse> No, they come when I call mount
[16:08] <sveinse> Ah. I see. Scratch that. EXT3-fs fails, EXT2-fs fails EXT4-fs mounts
[16:09] <sveinse> sooo. how come I cant umount afterwards...
[16:13] <ogra_> something has a file open in your mountpoint
[16:22] <sveinse> I need a fresh set of eyes on this:
[16:23] <sveinse>  mount -t vfat /tmp/sr/root/data.img /tmp/sr/data.img -o loop
[16:23] <sveinse>  umount -f /tmp/sr/root/data.img
[16:23] <sveinse> umount: can't forcibly umount /tmp/sr/root/data.img: Invalid argument
[16:24] <sveinse> Does it require the mount device to be specified, not the mount point?
[16:24] <Tassadar> umount requires the folder to which it was mounted to I think
[16:25] <ogra_> either should work, though -f might not work on loop mounts, not sure
[18:53] <wookey> infinity: Can you peruse https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1117602 and tell me if you understand what's going on?
[18:53] <ubot2> Ubuntu bug 1117602 in eglibc (Ubuntu) "eglibc does not crossbuild for arm64" [Undecided,New]
[18:56] <infinity> wookey: multiarch doesn't mean what you think it means.
[18:57] <wookey> right. That's what I was thinking
[18:57] <wookey> but it's turned on for all arches, I'm just trying what happens if I turn it off for arm64
[18:57] <wookey> What will that break?
[18:57] <infinity> wookey: Anyhow, I was going to rev cross-base stuff today.  Let me play with this.
[18:58] <wookey> OK, there are a couple of patches in there that need merging I think.
[18:58] <wookey> So that cross-building from the normal source works
[18:59] <infinity> I'm on top of it.  Don't worry.
[19:00] <wookey> I guess we should either fix whatever is wrong with dh_shlibdeps or put 'if cross-building don;t do this' round it properly
[19:00] <wookey> the disable selinux patch is wrong (should be controlled by DEB_STAGE, not just nobbled)
[19:01] <wookey> arm64 no profile is good
[19:01] <infinity> The DEB_STAGE stuff all needs fiddling.
[19:01] <infinity> And the no profile patch is obsolete.
[19:01] <wookey> yes
[19:02] <infinity> The dh_shlibdeps thing may or may not still be necessary, I fixed a bunch of things relating to that sort of thing in 2.17, but I'm not sure what the point of the patch was.
[19:02] <wookey> I'm not sure about the others.
[19:02] <infinity> Like I said, I'm fiddling with this today.
[19:02] <wookey> OK. I'll let you poke and go back to perl :-)
[19:02] <infinity> I'm not entirely sure what the point of the locales patch is either, except to very marginally speed up the build, perhaps.
[19:02] <wookey> Keen to test though cos I can;t build anything automatically without a buildable libc. SO when yuo think it might go...
[19:03] <wookey> yes. I'd ignore that
[19:03] <wookey> Or at least it can stay in cross-base
[19:11] <infinity> wookey: Wait, is this a cross-only issue, or is arm64 really the only arch that doesn't support IFUNC?
[19:12] <plars> do we not continue to produce preinstalled images for omap4 on precise?
[19:14] <infinity> plars: Nope.
[19:21] <infinity> wookey: Anyhow, it's entirely possible we don't need enable-multiarch for arm64 at all right now, given that aarch64 only has one subarch.
[19:36] <infinity> wookey: So, yeah, I'll disable multiarch on aarch64 for now.  That seems the sane and reasonable thing.  As Roland points out, any case of this "working" before when it shouldn't have was broken, so this isn't a regression, but a fix. :P
[19:37] <infinity> wookey: I suspect ARM will probably want ifun/multi-arch madness when armv8 starts to rev with new features, but we'll cross that bridge when we get there.
[19:37] <infinity> ifunc*
[19:38] <infinity> wookey: (Basically, this isn't what you think multi-arch is, in the Debian sense, this is being able to build DSOs that contain multiple versions of symbols for different subarches)
[19:38] <infinity> wookey: So, it was always a mistake that it was in the arm64.mk config in Debian/Ubuntu, it was just luck that it "worked" cause the test was broken.
[19:39] <infinity> wookey: I'll push fixes for this to experimental/raring today.
[19:46] <infinity> wookey: I had to do an experimental build to fix mips/mipsel anyway, so this makes me feel less bad about it if I have something else to upload for. :P
[22:13] <wookey> infinity: right, yes as you say, confusion over what 'multi-arch' meant and luck that it built/worked on 2.16
[22:13] <wookey> yes aarch64 probably is the only one without ifunc support
[22:14] <wookey> ifunc is coming, I'm told, jus tnot done yet
[22:14] <infinity> wookey: All fixed in Debian SVN, at any rate, and tested locally.  Just fixing one more thing before I upload.
[22:15] <wookey> cool