| 00:00.28 | *** join/#maemo atk (~Arch-TK@ircpuzzles/staff/Arch-TK) |
| 01:03.10 | *** join/#maemo inz (inz@irc.inz.fi) |
| 02:59.08 | *** join/#maemo LauRoman|Alt (~LauRoman@5-14-15-226.residential.rdsnet.ro) |
| 03:11.22 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 03:50.24 | *** join/#maemo pagurus (~user@i577B7215.versanet.de) |
| 04:00.24 | *** join/#maemo vahe (~vahe@unaffiliated/vahe) |
| 05:22.50 | *** join/#maemo florian__ (~florian_k@Maemo/community/contributor/florian) |
| 05:30.20 | *** join/#maemo spiiroin (~spiiroin@2001:998:2a:dead:5911:f130:3b12:ee11) |
| 06:05.46 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 06:23.40 | brolin_empey | Do non-AMD chipsets still exist for current AMD x86 platforms? Or is it like Intel x86 platforms, where there are no longer any non-Intel chipsets: apparently the Pentium 4 era was the last era with non-Intel chipsets. |
| 06:27.16 | *** join/#maemo auenf (~David@2001:8003:3d05:d200:a8ea:65a8:3a95:d3c9) |
| 06:35.03 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 06:42.06 | brolin_empey | I see only Intel and AMD chipsets listed on https://www.msi.com/Motherboards/ . Apparently the Asus Web site does not allow filtering by chipset. |
| 06:44.55 | brolin_empey | No, apparently the Asus Web site does allow filtering by chipset but it also lists only Intel and AMD chipsets. |
| 06:51.47 | brolin_empey | Same for https://www.gigabyte.com/Motherboard . |
| 06:59.00 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 07:19.37 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 07:35.27 | Maxdamantus | I suspect "chipset" practically means "class of CPUs" nowadays. |
| 07:35.46 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 07:36.19 | Maxdamantus | (I don't know anything about whether AMD requires their own hardware on motherboards, but I imagine even if they didn't, people would still use the term "chipset" to denote the set of CPUs that will work on the board) |
| 07:37.56 | Maxdamantus | Looking at the dates on the Wikipedia page for "List of AMD chipsets", I suspect they don't. |
| 07:38.55 | bencoh | Maxdamantus: "chipset" actually refers to the specialized/helper chips on the motherboard, not the set of working CPUs |
| 07:40.00 | *** join/#maemo geaaru (~geaaru@host170-152-static.43-88-b.business.telecomitalia.it) |
| 07:40.11 | bencoh | (and chip vendors eventually started merging their set of chips in a single helper chip) |
| 07:43.37 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 07:44.08 | Maxdamantus | bencoh: yes, I know. |
| 07:44.29 | Wizzup | there are some chinese companies taking amd zen and producing their 'own' CPUs with it |
| 07:44.35 | Maxdamantus | bencoh: but I imagine even if they didn't have them (which seems to be the case for AMD), people would still use the term "chipset". |
| 07:44.45 | bencoh | ah |
| 07:45.52 | Maxdamantus | âThis is an overview of chipsets sold under the brand AMD, manufactured before May 2004 by the company itself, before the adoption of open platform approachâ |
| 07:46.08 | *** join/#maemo KotCzarny (ariel@31.135.195.151) |
| 07:46.29 | Maxdamantus | So I guess since the "open platform approach", it's just been up to motherboard producers to implement whatever's necessary. |
| 07:46.43 | Maxdamantus | (again, just a guess, don't know anything about AMD from actual experience) |
| 08:04.50 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 08:26.09 | sixwheeledbeast^ | Last non-AMD chipset I can remember would be AM2+ era (Athlon64), not long after ATI became part of AMD. I recall after that the only boards non-AMD chipset being GeForce. So imagine AM3 boards would be the last non-AMD chipset, I only recall 900 Series chipset from there. |
| 08:41.57 | *** join/#maemo kraft (~kraft@gateway/shell/blinkenshell.org/x-xawkslnolcrqrvto) |
| 08:58.07 | *** join/#maemo florian__ (~florian_k@Maemo/community/contributor/florian) |
| 10:20.12 | *** join/#maemo xorly (~xorly@ip-86-49-24-93.net.upcbroadband.cz) |
| 10:21.14 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 10:23.00 | jonwil | Does anyone know of a mirror of the Nokia QT repository that used to be at https://gitorious.org/+qt-developers/qt/x11-maemo ? I dont mean https://github.com/community-ssu/qt-x11-maemo which is the Community SSU repository, I mean the nokia repository as it was at the time Nokia stopped making commits to it. |
| 10:24.49 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 10:26.21 | Maxdamantus | Based on https://wiki.maemo.org/Qt_Maemo_Git_Process , maybe this one? https://gitorious.org/qt/x11-maemo |
| 10:27.05 | Maxdamantus | The top of the log looks like nokia. |
| 10:29.36 | Maxdamantus | (hint: add ".git" to the end of the URL to get a remote that you can actually clone through `git`) |
| 10:31.05 | jonwil | Its not cloning |
| 10:31.12 | jonwil | Now it is :) |
| 10:31.13 | Maxdamantus | It seems slow. |
| 10:31.17 | jonwil | I still want https://gitorious.org/+qt-developers/qt/x11-maemo though |
| 10:31.27 | jonwil | since both are different repos with different contents |
| 10:31.31 | Maxdamantus | afaict that was a community project. |
| 10:31.48 | Maxdamantus | (according to the wiki page I linked) |
| 10:32.10 | *** join/#maemo eMHa (~mh@81.26.162.98) |
| 10:32.19 | jonwil | What I am trying to figure out is the relationship between https://gitorious.org/+qt-developers/qt/x11-maemo, http://qt.gitorious.org/qt/x11-maemo and https://github.com/community-ssu/qt-x11-maemo |
| 10:32.44 | jonwil | i.e. exactly what source code was first used to build https://github.com/community-ssu/qt-x11-maemo |
| 10:33.56 | Maxdamantus | Actually, it's the same repo. |
| 10:34.05 | Maxdamantus | well, the same head commit, at least. |
| 10:34.10 | jonwil | which ones? |
| 10:34.10 | Maxdamantus | https://web.archive.org/web/20110909004922/https://gitorious.org/+qt-developers/qt/x11-maemo |
| 10:34.20 | Maxdamantus | last push is 1f7db84 |
| 10:34.32 | Maxdamantus | which is the head of the repo I first linked. |
| 10:35.31 | Maxdamantus | guess the reason it's slow is just because the repository is so big. |
| 10:35.36 | Maxdamantus | Receiving objects: 43% (230155/534275), 157.12 MiB | 744.00 KiB/s |
| 10:35.46 | jonwil | Yeah |
| 10:36.28 | Maxdamantus | but you can they're the same by looking at the commit ids through the gitweb UI and through the wayback view of gitorious. |
| 10:39.39 | jonwil | My guess is that https://gitorious.org/+qt-developers and http://qt.gitorious.org were aliases of each other |
| 10:40.15 | jonwil | If you look at the wayback view of http://qt.gitorious.org/qt/x11-maemo you can see that its owned by +qt-developers |
| 10:41.11 | jonwil | Aha, now |
| 10:41.13 | jonwil | now I see |
| 10:41.36 | jonwil | http://gitorious.org/+qt-maemo-developers/qt/qt-maemo is a totally different repo than http://qt.gitorious.org/qt/x11-maemo aka https://gitorious.org/+qt-developers/qt/x11-maemo |
| 10:42.53 | Maxdamantus | hopes someday to use software on his phone that is not a fork of a fork of some mainstream software. |
| 10:43.25 | jonwil | And https://github.com/community-ssu/qt-x11-maemo formerly https://gitorious.org/community-ssu/qt-x11-maemo is clearly a fork of https://gitorious.org/+qt-developers/qt/x11-maemo |
| 10:48.13 | jonwil | so now I have yet another QT tree on my disk :) |
| 10:49.19 | Maxdamantus | You can probably save disk space by just keeping them all in the same local repository. |
| 10:52.21 | Maxdamantus | in one of the repositories, just add the other repositories as alternatives, then add all the remotes as used by the other repositories, and fetch. |
| 10:52.41 | Maxdamantus | then `git repack -a -d`, and remove the alternates file. |
| 10:53.20 | Maxdamantus | (won't need to download anything significant since you should already have the relevant objects accessible through alternates) |
| 10:54.04 | jonwil | Total on-disk size of all 4 QT related repos I can find off the top of my head is only 2.69GB which isn't a problem |
| 10:55.55 | jonwil | I have the Nokia QT repository, the CSSU repo that was forked from it, the upstream QT 4.x source repository and then the Debian QT 4.x repository (which is just the debian local packaging/patches stuff on top of the Nokia repo) |
| 10:56.08 | jonwil | I mean the upstream QT repo |
| 10:56.23 | jonwil | or rather its a fork on top of an upstream QT tarball :) |
| 11:30.11 | Wizzup | Maxdamantus: you're welcome to help out @ not a fork of a fork :p |
| 11:32.34 | Maxdamantus | Wizzup: yeah, if I can get around to doing stuff, it would basically just be making separate non-maemo software that is useful for my N900. |
| 11:32.55 | Maxdamantus | (so I can just run those programs on debian or something) |
| 11:34.39 | sixwheeledbeast^ | https://gitorious.org/qt/niqts-qt-maemo-developers-x11-maemo.git/ ? |
| 11:37.01 | jonwil | I got what I want now |
| 11:37.04 | jonwil | So its all good |
| 11:37.29 | Maxdamantus | That last repository linked is a subset of https://gitorious.org/qt/x11-maemo |
| 11:37.55 | jonwil | https://gitorious.org/qt/x11-maemo is the same code that used to be at both http://qt.gitorious.org/qt/x11-maemo and http://qt.gitorious.org/qt/x11-maemo |
| 11:54.12 | *** join/#maemo sunshavi (~user@181.64.192.4) |
| 11:56.26 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 12:22.49 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 12:52.16 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 13:00.23 | *** join/#maemo spiiroin (~spiiroin@82-203-188-96.bb.dnainternet.fi) |
| 13:07.55 | *** join/#maemo Oxyd76 (~quassel@5.18.99.0) |
| 13:17.29 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 13:33.41 | DocScrutinizer05 | famous findings that should have been archived on a wiki page but never were |
| 13:34.18 | DocScrutinizer05 | ~qt |
| 13:34.18 | infobot | it has been said that qt is TrollTech's QT library, available at http://www.trolltech.com |
| 13:34.38 | DocScrutinizer05 | ~#maemo qt is https://gitorious.org/qt/x11-maemo is the same code that used to be at both http://qt.gitorious.org/qt/x11-maemo and http://qt.gitorious.org/qt/x11-maemo |
| 13:34.38 | infobot | okay, DocScrutinizer05 |
| 13:34.47 | DocScrutinizer05 | ~qt |
| 13:34.47 | infobot | it has been said that qt is https://gitorious.org/qt/x11-maemo is the same code that used to be at both http://qt.gitorious.org/qt/x11-maemo and http://qt.gitorious.org/qt/x11-maemo |
| 13:36.39 | DocScrutinizer05 | ~literal x11 |
| 13:36.40 | infobot | "#maemo x11" is "Install xauth on N900 (apt-get install xauth). Run from your PC 'ssh -X user@Nokia-N900', and N900's X will be forwarded to your PC" |
| 13:37.58 | DocScrutinizer05 | ~#maemo x11 is also see ~qt |
| 13:37.58 | infobot | okay, DocScrutinizer05 |
| 13:38.05 | DocScrutinizer05 | ~x11 |
| 13:38.05 | infobot | [x11] Install xauth on N900 (apt-get install xauth). Run from your PC 'ssh -X user@Nokia-N900', and N900's X will be forwarded to your PC, or see ~qt |
| 13:39.15 | DocScrutinizer05 | ~listvalues x11-maemo |
| 13:39.54 | DocScrutinizer05 | WUT?? |
| 13:40.03 | DocScrutinizer05 | ~+listvalues x11-maemo |
| 13:40.30 | DocScrutinizer05 | wtf?! |
| 13:40.39 | DocScrutinizer05 | ~+listvalues x11 |
| 13:40.53 | DocScrutinizer05 | ~+listvalues poettering |
| 13:41.03 | KotCzarny | you've just dos'ed the poor bot |
| 13:41.08 | KotCzarny | out of mem or shm space |
| 13:41.08 | DocScrutinizer05 | ~die |
| 13:42.11 | *** join/#maemo infobot (ibot@208.53.50.136) |
| 13:42.11 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 13:42.11 | *** mode/#maemo [+v infobot] by ChanServ |
| 13:42.12 | DocScrutinizer05 | ~+listvalues x11-maemo |
| 13:42.25 | DocScrutinizer05 | o.O |
| 13:46.06 | DocScrutinizer05 | ~+status |
| 13:46.06 | infobot | Since Mon Jun 11 13:41:20 2018, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 1 command. I have been awake for 4m 46s this session, and currently reference 119759 factoids. I'm using about 82296 kB of memory. With 0 active forks. Process time user/system 1.16/0.14 child 0/0 |
| 13:46.22 | DocScrutinizer05 | wish I've thought of that before killing it |
| 13:47.19 | DocScrutinizer05 | wonder what ": RSSFeeds, Debian" means |
| 13:47.38 | KotCzarny | might be someone else started some task |
| 13:48.33 | DocScrutinizer05 | ~+help rssfeeds |
| 13:48.56 | DocScrutinizer05 | never wrapped my head around that |
| 13:50.06 | DocScrutinizer05 | prolly an unmaintained command that somebody ran nevertheless for debian? |
| 13:53.06 | DocScrutinizer05 | nfc, rssfeeds is not making sense to me |
| 13:53.28 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 13:53.44 | DocScrutinizer05 | there must be more commands related to this |
| 13:54.54 | DocScrutinizer05 | can't spot anythinh meaningful that might be related, in ~help. No "feed" or whatever command |
| 13:56.19 | DocScrutinizer05 | news? |
| 13:56.29 | DocScrutinizer05 | ~+help news |
| 13:56.42 | DocScrutinizer05 | ~+help newsadd |
| 13:56.59 | DocScrutinizer05 | ~+help news add |
| 13:57.29 | DocScrutinizer05 | ~news |
| 14:02.51 | DocScrutinizer05 | the bot is bitrotting :-S |
| 14:03.07 | DocScrutinizer05 | ~+status |
| 14:03.07 | infobot | Since Mon Jun 11 13:41:20 2018, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 16 commands. I have been awake for 21m 47s this session, and currently reference 119759 factoids. I'm using about 82428 kB of memory. With 0 active forks. Process time user/system 2.62/0.43 child 0/0 |
| 14:06.22 | DocScrutinizer05 | ~+uptime |
| 14:19.35 | brolin_empey | sixwheeledbeast^: Yes, at work we have an AM2 motherboard from 2006 with a non-AMD (nVidia nForce) chipset but I noticed that non-AMD chipsets for AMD x86 platforms seem to have disappeared. |
| 14:25.14 | sixwheeledbeast^ | brolin_empey: Nvidia have concentrated on GFX, ATI are part of AMD. also there is only the Southbridge chipset required on later stuff compared to older boards with a "northbridge". |
| 15:07.57 | enyc | sixwheeledbeast^: what about VIA, SiS, Ali ? |
| 15:10.00 | KotCzarny | all subpar performance, to say at least |
| 15:11.07 | enyc | I remember the Pentium-II with silly chipset |
| 15:11.25 | enyc | 'weird ISA timing issues on some cards, too |
| 15:11.26 | enyc | etc |
| 15:11.36 | sixwheeledbeast^ | All older chipsets than above? |
| 15:12.46 | enyc | no idea |
| 15:14.13 | sixwheeledbeast^ | I recall a SiS chipset on my first board Socket A |
| 15:20.23 | enyc | i had loats of weird failures orf sockt-A athlons |
| 15:20.31 | enyc | 'capactiros on board, chips fail, ..... |
| 15:20.41 | enyc | amd64's seem to have been more robust. |
| 15:25.02 | sixwheeledbeast^ | umm? |
| 15:27.43 | enyc | err as above? |
| 15:27.44 | enyc | anyway |
| 15:29.29 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:45.33 | sixwheeledbeast^ | I never had any issues with any AMD stuff. I always understood Socket A and Athlon where solid. Most chip deaths where related to damaging the CPU on heatsink mounting |
| 15:46.57 | sixwheeledbeast^ | Latter CPU's "amd64" had lids on covering the die etc and therefore less likely to damage from heatsink mounting. |
| 15:47.41 | sixwheeledbeast^ | caps would be down to board manufacturer I suppose. |
| 16:29.23 | *** join/#maemo LauRoman|Alt (~LauRoman@5-14-136-246.residential.rdsnet.ro) |
| 16:31.57 | *** join/#maemo florian__ (~florian_k@Maemo/community/contributor/florian) |
| 17:09.13 | *** join/#maemo Oxyd76 (~quassel@5.18.99.0) |
| 17:18.10 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 17:51.04 | *** join/#maemo drrty (drrty@gateway/vpn/privateinternetaccess/drrty) |
| 18:16.09 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 18:35.12 | *** join/#maemo drrty (drrty@gateway/vpn/privateinternetaccess/drrty) |
| 18:37.41 | *** join/#maemo florian__ (~florian_k@Maemo/community/contributor/florian) |
| 18:54.53 | *** join/#maemo __LauRoman (~LauRoman@5-14-136-246.residential.rdsnet.ro) |
| 19:16.54 | *** join/#maemo LauRoman|Alt (~LauRoman@5-14-136-246.residential.rdsnet.ro) |
| 19:54.08 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 19:55.32 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 20:08.20 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 20:29.45 | *** join/#maemo LauRoman (~LauRoman@5-14-136-246.residential.rdsnet.ro) |
| 20:40.59 | *** join/#maemo Oxyd76 (~quassel@5.18.99.0) |
| 20:42.50 | *** join/#maemo eMHa (~mh@p5089D79F.dip0.t-ipconnect.de) |
| 20:49.00 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 20:55.17 | *** join/#maemo M4rtinK (~M4rtinK@ip-78-45-137-21.net.upcbroadband.cz) |
| 21:21.24 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 21:28.17 | *** join/#maemo Kilroo (~Kilroo@71.71.97.50) |
| 21:53.19 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 21:54.43 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 22:49.57 | *** join/#maemo qwazix (~qwazix@46-198-128-218.static.cyta.gr) |
| 22:49.57 | *** join/#maemo qwazix (~qwazix@Maemo/community/ex-council/qwazix) |
| 23:13.10 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 23:28.42 | *** join/#maemo segnior (segnior@gateway/shell/xshellz/x-tuiclvscukfwilta) |
| 23:38.13 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |