**** BEGIN LOGGING AT Wed Apr 19 03:00:04 2017 Apr 19 07:38:26 Wizzup, do you have ARM hildon-desktop packages? Apr 19 07:48:43 wonder if this can be interesting for Maemo UI - https://www.xda-developers.com/halium-is-an-open-source-project-working-towards-a-common-base-for-non-android-mobile-operating-systems/ Apr 19 08:09:01 NotKit: could be interesting to ease "porting" Apr 19 08:09:30 (ie porting to android-powered devices) Apr 19 09:09:50 NotKit: do they only have chat rooms, or also a website? The article doesn't seem to mention one Apr 19 09:10:10 NotKit: no arm packages yet, waiting on amprolla. Reason to do intel first is that 3d accel is not a total mess on intel. Apr 19 09:10:51 actually since its pc, 3d accel support is more broad :) Apr 19 09:16:04 When I said intel I meant amd64 Apr 19 09:16:20 just say x86_64 Apr 19 09:16:22 but essentially anything with decent PCI support works OK with 3d graphics, as you can plug in an amd card Apr 19 09:16:31 KotCzarny: that'd not be correct :) Apr 19 09:16:43 asnt amd64 just that? Apr 19 09:16:46 *isnt Apr 19 09:17:01 unless context is something else Apr 19 09:17:58 x86-64 (also known as x64, x86_64 and AMD64) is the 64-bit version of the x86 instruction set Apr 19 09:18:05 https://en.wikipedia.org/wiki/X86-64 Apr 19 09:18:39 AMD64 was created as an alternative to the radically different IA-64 architecture, which was designed by Intel and Hewlett Packard. Originally announced in 1999[13] while a full specification became available in August 2000,[14] the AMD64 architecture was positioned by AMD from the beginning as an evolutionary way to add 64-bit computing capabilities to the existing x86 architecture, as opposed to Intel's Apr 19 09:18:45 approach of creating an entirely new 64-bit architecture with IA-64. Apr 19 09:18:47 The first AMD64-based processor, the Opteron, was released in April 2003. Apr 19 09:19:49 yes, but intel's 64bit x86 cpu joined it Apr 19 09:20:18 The original specification, created by AMD and released in 2000, has been implemented by AMD, Intel and VIA Apr 19 09:20:31 https://en.wikipedia.org/wiki/X86-64#Industry_naming_conventions Apr 19 09:20:47 KotCzarny: it's still the name for it with all distros I use Apr 19 09:20:54 yup Apr 19 09:21:00 and since I wanted to refer to generic 64 bit x86, amd64 is the proper term Apr 19 09:21:06 yup Apr 19 09:21:08 I didn't want to refer to intel-only computers Apr 19 09:21:27 but people who dont know that could be confused by 'amd' part Apr 19 09:21:41 that's why x86_64 or x64 is often used Apr 19 09:22:35 but ... nobody except the linux kernel and gcc :p Apr 19 09:22:37 s/but/by/ Apr 19 09:22:38 Wizzup meant: by ... nobody except the linux kernel and gcc :p Apr 19 09:22:38 anyway Apr 19 09:24:37 and linux kernel and gcc are quite hard core of almost all linux systems Apr 19 09:24:52 I'd like to interject for a moment Apr 19 09:29:35 https://botbot.me/freenode/devuan/2017-03-02/?msg=81815088&page=2 Apr 19 09:47:25 Wizzup: x86 isn't intel specific, it's the canonical generic name for the IA. Intel64 would be intel specific Apr 19 09:48:08 ... Apr 19 09:48:18 It's called amd64; I don't care if you think it's not sensible Apr 19 09:48:49 yes, debian calls "it" that way Apr 19 09:49:50 not just debian. all distros out there except for ... dragonflybsd and some obscure linux ones Apr 19 09:51:17 that's the way they call that build since it was originally done for AMD and later on worked for other manufacurers' CPUs as well. But the IA is x86 Apr 19 09:53:22 >>way to add 64-bit computing capabilities to the existing x86 architecture<< Apr 19 09:54:47 ia64 is itanium and compatible only with intel's itanium cpus Apr 19 09:56:30 also, doesnt gentoo use x86_64 ? Apr 19 09:56:49 since it's relying on gcc so its more natural there Apr 19 09:57:11 KotCzarny: no, it uses amd64 Apr 19 09:57:33 but guys ... big deal Apr 19 09:58:12 well, they have 'amd64 (x86_64)' in their handbook Apr 19 09:58:16 so they use both ;) Apr 19 09:58:36 still, it doesnt matter much Apr 19 09:58:36 If you want to (un)keyword a package, you have to write ~amd64 verbatim Apr 19 09:59:00 just saying that it might be confusing for noobs and requires some explanation Apr 19 09:59:26 amd got themselves place forever in that part Apr 19 10:00:30 they deserve it. Apr 19 10:00:31 bbl ;) Apr 19 11:08:42 Wizzup, as for website, not yet, http://halium.org/ has only placeholder Apr 19 11:15:54 well, IA-64 simply isn't x86_64/amd64 Apr 19 11:17:26 fwiw, Linux uses x86_64 Apr 19 11:17:49 and the gcc target is usually x86_64 Apr 19 11:18:09 (I suspect those are bound to each other) Apr 19 11:18:56 yeah, by instruction set for example ;) Apr 19 11:19:59 "the IA is x86" sounds wrong Apr 19 11:20:26 afaik, "IA" refers to Itanium, which .. again, afaik, is pretty much independent of x86 Apr 19 11:20:27 it is wrong Apr 19 11:21:02 I think "IA" here refers to "Instruction Architecture" like m68k, armv7, etc. Apr 19 11:21:10 Oh. Apr 19 11:21:12 Maxdamantus: 11:20 < Wizzup> https://en.wikipedia.org/wiki/X86-64#Industry_naming_conventions Apr 19 11:21:54 anyway, as long as noone calls it "x64" I don't mind. Apr 19 11:22:09 MS does ;) Apr 19 11:22:15 I know. Apr 19 11:22:49 ;) Apr 19 11:25:37 warfare: they call it amd64 Apr 19 11:25:52 "instruction architecture" doesn't seem to be a common term. Apr 19 11:26:00 Microsoft Windows's x64 versions use the AMD64 moniker internally to designate various components which use or are compatible with this architecture. For example, the environment variable PROCESSOR_ARCHITECTURE is assigned the value "AMD64" as opposed to "x86" in 32-bit versions, and the system directory on a Windows x64 Edition installation CD-ROM is named "AMD64", in contrast to "i386" in 32-bit Apr 19 11:26:06 versions.[80] Apr 19 11:26:18 "IA" in "IA-64" seems to just mean "Itanium architecture" Apr 19 11:26:46 (there's of course the common acronym "ISA" though) Apr 19 11:27:42 I might just have mixed this up :) Apr 19 11:29:16 also, even though debian calls it amd64 in its packages, I think it uses "x86-64" in the filesystem. Apr 19 11:29:45 eg, I think it has some /lib/linux-x86-64 or something directory. Apr 19 11:29:56 vendor neutral pronouns :) Apr 19 11:30:21 Maxdamantus: that is per binutils/gcc more than choice Apr 19 11:30:28 /lib/x86_64-linux-gnu Apr 19 11:30:36 that is the gcc tuple name, isn't that obvious? Apr 19 11:30:56 as for vendor neutrality, as Wizzup's link said, AMD called it "x86-64" Apr 19 11:31:55 UEFI calls it x64 Apr 19 11:32:09 BOOTX64.EFI as defined in the specs Apr 19 11:32:09 * Wizzup checks the channel name and seems #maemo, not #pedants Apr 19 11:32:12 * Wizzup shrugs Apr 19 11:32:17 s/seems/sees/ Apr 19 11:32:18 :) Apr 19 11:33:15 it's irc, which has 'internet' as a first word Apr 19 11:33:23 which means, we have to be 100% correct! Apr 19 11:33:59 Or, be incapable of realising that we all agree in the first place, and instead argue on forever about meaningless things Apr 19 11:34:28 :) (or rather :( in that specific case) Apr 19 11:35:19 Wizzup: regarding halium, the article mentions #halium@freenode, halium on telegram, and #halium:matrix.org) Apr 19 11:35:36 Yeah; exactly, but no website to quickly get an idea of what they'll do Apr 19 11:37:16 https://xkcd.com/386/ (what a fitting number) Apr 19 11:38:08 :] Apr 19 11:40:41 https://lists.sailfishos.org/pipermail/devel/2017-April/007842.html "Currently this project idea is codenamed Halium. Overall idea for the project is Apr 19 11:40:44 drafted at the https://tinyurl.com/halium" Apr 19 11:40:52 but this tinyurl doesn't seem to work :/ Apr 19 11:41:15 ah nevermind, it does work without trailing , Apr 19 14:49:51 /set irc.look.buffer_switch_autojoin off Apr 19 14:55:13 :) Apr 19 15:12:32 umm is there someone still bouncing in and out? Apr 19 15:13:36 I suppose so, I decided to ignore his join/part/quit Apr 19 15:14:01 nope Apr 19 15:14:04 it stopped Apr 19 15:15:03 i ignore all part/join/quits Apr 19 15:15:23 very convenient in a big silent channel Apr 19 15:52:32 hmm, I wonder if anyone tried https://github.com/mozilla/webrtc-standalone Apr 19 15:52:41 or https://www.openwebrtc.org/ Apr 19 15:53:20 I suppose that could be used with webrtc-powered A/V call services Apr 19 16:18:34 meh, openwebrtc needs gstreamer-1.0 ... Apr 19 16:18:59 so this would be unusable on n900, unless we decide to port libgstdsp to gstreamer-1.x Apr 19 18:54:06 bencoh: shouldn;t be that hard Apr 19 19:20:30 freemangordon: maybe, I never seriously compared both APIs Apr 19 19:46:57 Vajb: there was, he fixed his issue Apr 19 19:52:02 Zungo: yup. I saw it from the logs :) Apr 20 00:32:05 ~lazyflash Apr 20 00:32:16 ~flash Apr 20 00:32:17 [maemo-flashing] http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh; or see ~flashing-cmdline, or see ~lazyflashing **** ENDING LOGGING AT Thu Apr 20 03:00:01 2017