| 00:21.29 | *** join/#maemo infobot (ibot@208.53.50.136) |
| 00:21.29 | *** 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 |
| 00:21.29 | *** mode/#maemo [+v infobot] by ChanServ |
| 00:54.09 | brolin_empey | Heh, apparently Kingston has discontinued earlier-than-DDR3 SDRAM modules. I wonder if this means that the lifetime warranty for the DDR1 and DDR2 modules I am still using is now worthless because Kingston can no longer provide a replacement for DDR2 and earlier modules? |
| 01:36.27 | Hurrian | They probably have some in a backroom somewhere, manufacturers typically reserve some stock for replacements |
| 01:36.41 | Hurrian | But might take a month+ for them to find and ship it to you |
| 01:39.15 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 02:09.32 | brolin_empey | Hurrian: Maybe. That makes sense. What about my SODIMM question? |
| 02:12.36 | Hurrian | nope, the first few Intel integrated memory controllers (especially on laptops) were a bit flaky, so they don't support gigantic DIMMs |
| 02:12.57 | Hurrian | 1st gen Nehalem was really bad at this, crashed and burned with 8GB sodimms |
| 02:13.16 | Hurrian | 2nd gen Sandy Bridge, which is what's in your laptop, only supports up to 8GB SODIMM |
| 02:13.37 | Hurrian | if your CPU is socketed and you can upgrade to Ivy Bridge, you can use a 16GB SODIMM |
| 02:22.46 | brolin_empey | Hurrian: It is the notebook computer of my father, not of me. I use only desktop and handheld computers, not something in between. Can I tell from the software if the CPU is socketed? Maybe from the package type? I guess if it is some form of BGA then it is soldered on their motherboard but if it is some form of PGA or LGA then it may be socketed? Does the motherboard firmware have to support the CPU released after the model of computer was released? |
| 02:23.34 | brolin_empey | s/their/the/ |
| 02:23.56 | Hurrian | Typically if you have a microcode update in your BIOS released after Ivy Bridge came out, you'll have support for the newer CPUs |
| 02:27.04 | brolin_empey | Hurrian: I intentionally said âmotherboard firmwareâ instead of âBIOSâ because this computer uses EFI, not BIOS. Anyway, can I tell from the software if the CPU is socketed? |
| 02:27.36 | Hurrian | no, that core i5 CPU was available in both BGA and PGA form factors, you'll have to check by opening it up |
| 02:33.13 | brolin_empey | Hurrian: I could check if System Information Viewer or CPU-Z or similar shows the package type/form factor but my father has rebooted the computer into GNU+Linux because he usually uses GNU+Linux and was only temporarily running Windows. |
| 02:48.50 | brolin_empey | Hurrian: I ran lshw as root on GNU+Linux. Apparently the motherboard firmware is from Phoenix Technologies and is dated 2011â11â21. |
| 03:05.57 | brolin_empey | Hurrian: Apparently lshw does not say which package type/form factor the CPU uses. :-/ |
| 03:37.04 | Hurrian | IIRC you can't check the package type of the installed CPU from software, as socketed/soldered doesn't really make a difference to the software |
| 03:40.27 | Hurrian | also, the microcode in the firmware probably isnt updated with the Ivy Bridge microcode, by then it was likely still in final qualification |
| 03:45.49 | *** join/#maemo pagurus` (~user@i59F7753E.versanet.de) |
| 05:28.56 | brolin_empey | Hurrian: That makes sense but lots of things can be checked from software that usually should not matter to application software, such as the type of RAM or the chassis type of the computer. |
| 05:31.15 | Hurrian | Only if the vendor declares those properties in e.g. ACPI tables |
| 05:31.21 | Hurrian | or the DMI table |
| 05:35.17 | brolin_empey | Hurrian: Maybe a better example is the brand of CPU as reported by the CPUID instruction. How often does application software need to know on which brand of CPU it runs as long as the CPU does what the software needs? |
| 05:38.33 | brolin_empey | Maybe the government of the PRC wants to avoid VIA CPUs because VIA is in the ROC? |
| 05:39.47 | Hurrian | often never, but iirc optimizing compilers sometimes enable faster code paths depending on available CPU features |
| 05:44.18 | brolin_empey | Well, the position of the CPC is that the ROC no longer legitimately exists, so I guess the CPC does not care if they use hardware from Taiwan because their position is that Taiwan is a province of the PRC. |
| 05:46.49 | brolin_empey | Hurrian: Features of the CPU running the compiler or of the CPU targetted by the compiler? |
| 05:47.32 | Hurrian | the latter |
| 05:51.17 | brolin_empey | Hurrian: Then why do features of the CPU running the compiler matter? Use of cross-compilers is common, even within the same family of computer/instruction set architecture, such as using an x86-64 computer to build software for x86-32. |
| 05:52.07 | Hurrian | the CPU running the compiler doesn't matter as long as it's set up to do cross compile properly |
| 05:52.35 | Hurrian | for gcc at least, building cross-endian compilers more or less works too, for most architectures |
| 05:55.24 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 06:02.10 | brolin_empey | Hurrian: I guess non-GNU compilers have had cross-endian compilation working for decades too because, as far as I know, x86 (little endian) computers are used to run compilers targetting big-endian computers, such as embedded platforms using m68k or PowerPC. |
| 06:04.54 | brolin_empey | I guess a specific example is CodeWarrior or some other non-GNU compiler targetting an m68k Palm OS computer but running on an x86 computer. |
| 06:11.31 | brolin_empey | Or a Microsoft compiler running on an x86 computer but targetting a big-endian video game console, such as one using the MIPS (PlayStation, Nintendo 64) or SuperH/SH (Sega Saturn, Sega Dreamcast) architecture. I forgot the endianness of MIPS and SH but I remember that m68k is big-endian and PowerPC supports both little- and big-endian modes but Darwin/Mac OS X uses big-endian mode. |
| 06:16.54 | brolin_empey | If I recall correctly, Alpha also supports both little- and big-endian modes. |
| 06:18.45 | brolin_empey | If I recall correctly, 6800/6502 are little-endian, which seems unexpected because 68000 is big-endian. |
| 06:20.55 | brolin_empey | Does a Sun x86 computer use the IBM PC architecture or does Sun have their own computer architecture using the x86 ISA? |
| 06:24.19 | brolin_empey | There was the SGI Visual Workstation that, if I recall correctly, uses the x86 ISA but at least partly does not use the IBM PC architecture. |
| 06:45.10 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 07:23.24 | *** join/#maemo guerby (~guerby@ip165.tetaneutral.net) |
| 07:23.24 | *** join/#maemo guerby (~guerby@april/board/guerby) |
| 08:28.41 | *** join/#maemo Kabouik (~kabouik@lns-bzn-37-82-253-53-3.adsl.proxad.net) |
| 08:43.26 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 09:21.24 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 09:40.44 | *** join/#maemo tkok__ (~tkok@dttkqwyf5nydbmq3g157t-3.rev.dnainternet.fi) |
| 09:51.33 | *** join/#maemo Kabouik_ (~kabouik@2a01:e35:2fd3:5030:ebd:59c2:cdd:e2f8) |
| 09:56.30 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 10:10.38 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 10:14.26 | *** join/#maemo aloril_ (~aloril@80.246.146.6) |
| 10:22.54 | *** join/#maemo guerby (~guerby@ip165.tetaneutral.net) |
| 10:22.55 | *** join/#maemo guerby (~guerby@april/board/guerby) |
| 10:35.33 | *** join/#maemo eMHa (~mh@b2b-78-94-197-130.unitymedia.biz) |
| 10:36.31 | *** join/#maemo jonwil (~jonwil@27-33-80-219.tpgi.com.au) |
| 11:10.46 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1::3) |
| 11:58.27 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 12:20.26 | *** join/#maemo Trizt (~user@ukko.aho.hk) |
| 12:20.30 | *** join/#maemo m4lvin (~m4lvin@w4eg.de) |
| 12:43.39 | *** join/#maemo Trizt (~user@ukko.aho.hk) |
| 12:43.40 | *** join/#maemo m4lvin (~m4lvin@w4eg.de) |
| 12:58.18 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 13:09.35 | *** join/#maemo Hurrian (~hurrian@unaffiliated/rikanee) |
| 13:24.36 | *** join/#maemo Vajb (~Vajb@85-76-49-118-nat.elisa-mobile.fi) |
| 13:28.34 | *** join/#maemo vectis (~vectis@78.141.51.129) |
| 13:48.15 | *** join/#maemo sunshavi (~user@181.64.192.254) |
| 14:08.07 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 15:13.56 | *** join/#maemo Milhouse (~Milhouse@kodi/staff/milhouse) |
| 16:00.36 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 16:14.12 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 16:17.35 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 16:47.25 | *** join/#maemo vahe (~vahe@unaffiliated/vahe) |
| 17:35.20 | *** join/#maemo drrty (drrty@gateway/vpn/privateinternetaccess/drrty) |
| 18:04.02 | *** join/#maemo xy2_ (~xy2_@94.239.253.5) |
| 18:27.44 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 18:41.03 | *** join/#maemo Vajb (~Vajb@85-76-146-230-nat.elisa-mobile.fi) |
| 18:50.22 | *** join/#maemo xy2_ (~xy2_@94.239.177.175) |
| 19:19.34 | *** join/#maemo sunshavi (~user@181.64.192.254) |
| 19:54.13 | *** join/#maemo l_bratch (~l_bratch@serenity.bratch.co.uk) |
| 20:05.28 | *** join/#maemo Kabouik_ (~kabouik@2a01:e35:2fd3:5030:ebd:59c2:cdd:e2f8) |
| 20:08.36 | *** join/#maemo eMHa (~mh@p5089DF5B.dip0.t-ipconnect.de) |
| 21:07.06 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 21:40.17 | *** join/#maemo Kilroo (~Kilroo@071-071-097-050.res.spectrum.com) |
| 22:00.08 | brolin_empey | Hurrian: Can you recommend a model of 8-GiB SODIMM that will work with this notebook computer with the current CPU? |
| 22:00.37 | brolin_empey | I mean with the CPU currently installed. |
| 22:10.56 | brolin_empey | Also, will this computer with the current CPU work with 2Ã 8-GiB SODIMMs? |
| 23:57.56 | Hurrian | yep, would probably be better to buy matching SODIMMs you could use dual channel on all 16GB of memory |
| 23:58.50 | Hurrian | as for a model of SODIMM, any 1333MHz 1.5V DDR3 SODIMM would work if you bought two, but if you're only buying one you need to match at least the primary timings |