| 00:01.04 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1::4) |
| 00:23.14 | *** join/#maemo infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 00:23.14 | *** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | "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 http://maemo.cloud-7.de/irclogs/freenode/_maemo/latest.log.html | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 00:23.14 | *** mode/#maemo [+v infobot] by ChanServ |
| 01:21.08 | *** join/#maemo LauRoman|Alt (~LauRoman@5-14-132-220.residential.rdsnet.ro) |
| 02:04.39 | brolin_empey | sixwheeledbeast: I redd https://www.gpd.hk/gpdp2max . It is indeed interesting but it has a fan, lacks an integrated numeric keypad, and presumably requires disassembly to access the battery. Also, it looks like the main memory may be fixed (soldered) on the motherboard instead of socketed? The IPS AMLCD sounds nice but an AMOLED display would be more impressive. |
| 02:09.30 | brolin_empey | It also lacks integrated Ethernet connectivity and uses an old version of Bluetooth (4.x instead of 5.x). Apparently it lacks a discrete GPU too. |
| 02:13.26 | brolin_empey | They are comparing it to some iPad model but all Apple iOS computers are fanless as far as I know. |
| 02:26.48 | *** join/#maemo brett-soric (~brett@ppp203-122-220-93.static.internode.on.net) |
| 02:27.28 | brolin_empey | The keyboard is not backlit either. |
| 02:27.38 | *** join/#maemo ketas (~ketas@0011-0000-0000-0000-d7dc-830e-07d0-2001.dyn.estpak.ee) |
| 03:13.46 | *** part/#maemo brett-soric (~brett@ppp203-122-220-93.static.internode.on.net) |
| 03:30.50 | *** join/#maemo progenyx (progenyx@gateway/vpn/privateinternetaccess/progenyx) |
| 03:53.12 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 03:54.28 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 03:57.09 | *** join/#maemo pagurus` (~user@i59F7A034.versanet.de) |
| 06:48.09 | *** join/#maemo inz (inz@inz.fi) |
| 07:01.15 | *** join/#maemo inz (inz@inz.fi) |
| 07:14.15 | *** join/#maemo sicelo (~sicelo@Maemo/community/ex-council/sicelo) |
| 07:57.59 | sixwheeledbeast | brolin_empey: that is correct re battery and memory https://youtu.be/gpjrbHFv_dA?t=728 |
| 08:01.03 | brolin_empey | sixwheeledbeast: OK. The soldered main memory sucks if the memory develops a bad bit, especially because it is non-ECC RAM as far as I can tell because I have not seen any mention of ECC RAM. |
| 08:05.39 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 08:41.32 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 08:58.16 | Maxdamantus | Is ECC RAM really better than usual RAM when there's a bad bit? Presumably in either case, you could just use a software solution involving just not using a particular page of RAM. |
| 08:59.08 | KotCzarny | ecc means error CORRECTING without any workarounds |
| 08:59.24 | KotCzarny | your solution is similar to 'are hardware modems better than software ones' |
| 08:59.37 | KotCzarny | yes, they are. |
| 09:01.32 | KotCzarny | ecc works at dram's speed, software solution would slow down dram to cpu speed |
| 09:01.34 | KotCzarny | or worse |
| 09:02.01 | Maxdamantus | Sure, but aiui you can only recover from one bit of error, so all you're doing is turning the bad bit of ECC RAM into a good bit of non-ECC RAM. |
| 09:02.09 | KotCzarny | depends on ecc used |
| 09:02.14 | KotCzarny | in case of 1bit, yeah |
| 09:02.23 | KotCzarny | but there are higher grades too |
| 09:03.30 | Maxdamantus | so .. what you'd want to do is detect that there's a problem with that bit, and tell your software to stop mapping pages to that location in RAM. |
| 09:03.32 | brolin_empey | is a night owl in a diurnal human world. Sigh. |
| 09:03.46 | KotCzarny | its already in linux kernel |
| 09:04.06 | KotCzarny | you can map out bad memory for 10-15 years already |
| 09:04.28 | KotCzarny | how do i know? because i used that long time ago |
| 09:04.58 | Maxdamantus | Right, so once you've got a bad bit, there's no point in relying on ECC to correct it. |
| 09:05.04 | Maxdamantus | since you can just stop using it. |
| 09:05.11 | KotCzarny | but you are now talking about bad ram modules |
| 09:05.30 | KotCzarny | ecc is about bit flips resulting in physical temporary events |
| 09:05.45 | KotCzarny | ie. radon gas (radioactivity) bit flipping |
| 09:05.56 | Maxdamantus | Right, that's what I've assumed is the main point of ECC, not in handling bad RAM. |
| 09:06.04 | KotCzarny | yup |
| 09:25.47 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 10:19.23 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 11:39.02 | sixwheeledbeast | I wouldn't be expecting many laptops/foobooks to have ECC most tablets would be soldered |
| 12:15.44 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 12:46.46 | *** join/#maemo Oksana_ (~Wikiwide@124-169-149-187.dyn.iinet.net.au) |
| 12:47.35 | *** join/#maemo Oksana_ (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 13:51.18 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 14:06.32 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 14:23.59 | *** join/#maemo Venemo (~venemo@fedora/Venemo) |
| 17:45.36 | *** join/#maemo Kabouik (~kabouik@2a01:e35:2fd3:5030:ebd:59c2:cdd:e2f8) |
| 17:46.16 | *** join/#maemo Kabouik (~kabouik@2a01:e35:2fd3:5030:ebd:59c2:cdd:e2f8) |
| 18:12.12 | *** join/#maemo Kilroo (~Kilroo@173.94.24.151) |
| 18:40.53 | brolin_empey | I correctly guessed that Python 2.7.x has a function named âroundâ, which seems to solve my aforementioned floating point âproblemâ. |
| 18:43.57 | *** join/#maemo Vajb (~Vajb@85-76-1-156-nat.elisa-mobile.fi) |
| 19:09.52 | *** join/#maemo Natch (~Natch@h-112-130.A444.priv.bahnhof.se) |
| 19:13.54 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 19:24.48 | brolin_empey | Incidentally: This is cool: https://webaudiodemos.appspot.com/slides/webmidi.html |
| 20:13.29 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 20:59.06 | *** join/#maemo RedW (~redw@89-67-10-209.dynamic.chello.pl) |
| 21:12.08 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 22:16.40 | *** join/#maemo cyteen_ (~cyteen@146.66.58.8) |
| 22:41.22 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 23:25.13 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 23:46.07 | *** join/#maemo xes (~xes@unaffiliated/xes) |