| + q66__ (~q66@q66.moe) | 00:12 | |
| - ajr (QUIT: ) (~ajr@user/ajr) | 00:12 | |
| minute | jfred: btw check the fuses, esp f2, it can blow but it manifests as one battery not being detected | 00:13 |
|---|---|---|
| jfred | Thanks! Will do when I get it back | 00:15 |
| - q66 (QUIT: ) (~q66@q66.moe) | 00:22 | |
| * q66__ -> q66 | 00:25 | |
| sevan | not Reform related, but same limb :) https://community.arm.com/oss-platforms/w/docs/604/notice-potential-damage-to-n1sdp-boards-if-using-latest-firmware-release | 00:29 |
| minute | exotic, n1sdp | 01:31 |
| - mtm- (QUIT: Ping timeout: 240 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 02:04 | |
| - mjw (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org) | 03:01 | |
| - nsc (QUIT: Ping timeout: 240 seconds) (~nicolas@175-49-142-46.pool.kielnet.net) | 03:20 | |
| + nsc (~nicolas@248-48-142-46.pool.kielnet.net) | 03:22 | |
| + mtm- (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 04:10 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 06:16 | |
| - Boostisbetter (QUIT: Ping timeout: 265 seconds) (4a410829d7@irc.cheogram.com) | 06:17 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 07:09 | |
| + bgs (~bgs@212-85-160-171.dynamic.telemach.net) | 07:13 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 07:51 | |
| - bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net) | 08:22 | |
| - eschaton (QUIT: Quit: ZNC 1.8.x-git-43-6af32bbf - https://znc.in) (~eschaton@li541-49.members.linode.com) | 11:59 | |
| + eschaton (~eschaton@li541-49.members.linode.com) | 12:01 | |
| + mjw (~mjw@gnu.wildebeest.org) | 12:35 | |
| eery | So I've been playing around with Gentoo, and I'm genuinely surprised at how little of an issue 4GB of RAM is, when running 4 build jobs in parallel | 13:00 |
| eery | Are compilers more memory efficient than they were a few years ago? | 13:00 |
| josch | eery: it depends on what you compile | 13:01 |
| josch | eery: try compiling chromium | 13:01 |
| eery | lol been there, done that | 13:02 |
| eery | took just over 7 days straight :) | 13:02 |
| eery | even so, it never really dipped too heavily into swap, which is what surprises me | 13:02 |
| josch | on Debian there is discussion what to do with chromium on certain arches that will never have enough ram to build it | 13:05 |
| eery | What arches does chromium run on that don't have enough ram? MIPS? | 13:07 |
| josch | yup | 13:07 |
| eery | I guess it doesn't cross-compile lol | 13:08 |
| josch | hahahahaha | 13:08 |
| josch | ever looked at chromium's build system? ;) | 13:09 |
| eery | I value my sanity :P | 13:09 |
| eery | I've looked just long enough when trying to get it to build on ppc64 before | 13:09 |
| eery | I'm being a little facetious, but I don't understand why chromium takes ... 15-20 times longer to compile than Firefox | 13:10 |
| eery | like, I know why, but it's still mind blowing | 13:10 |
| pandora[m] | Why is it actually? | 13:14 |
| eery | I don't know the exact reason but I know chromium includes such fun things as "webusb" and "web bluetooth" and I see source files related to controlling wifi and power management and whatever else | 13:15 |
| eery | there's also a ton of bundled libraries and their dependencies that get used instead of system stuff | 13:15 |
| vkoskiv | Also has code fo handling Xbox controllers, I believe :D | 13:16 |
| eery | although that's common to firefox as well | 13:16 |
| eery | dunno if that explains the literal order of magnitute difference tho | 13:18 |
| eery | my intel laptop can do a full PGO "double" build of firefox in 40~ minutes, and I killed the chromium build after 8 hours, and it was barely half done... | 13:19 |
| - mjw (QUIT: Ping timeout: 265 seconds) (~mjw@gnu.wildebeest.org) | 13:40 | |
| - mtm- (QUIT: Ping timeout: 265 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 14:04 | |
| * mark_ -> mjw | 14:06 | |
| + mtm- (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 16:10 | |
| - ec0 (QUIT: Ping timeout: 240 seconds) (~ec0@vps-446f4f39.vps.ovh.ca) | 16:23 | |
| + ec0 (~ec0@vps-446f4f39.vps.ovh.ca) | 16:28 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 17:05 | |
| - mark_ (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org) | 17:38 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 18:56 | |
| eery | Anyone tried running a kernel with 64KB pages? | 18:59 |
| + ajr (~ajr@user/ajr) | 19:07 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 19:15 | |
| - mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 19:16 | |
| * mark_ -> mjw | 19:16 | |
| + mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 19:16 | |
| minute | hmm, i just can't get the drm bridge chain to work between a311d's vpu, mipi and sn65dsi86. just can't wrap my head around the interdependencies while probing | 20:18 |
| Boostisbetter | minute: bummer. Give it time. It'll make sense soon enough. | 20:21 |
| minute | not sure that i should spend more time on this. already 2 days wasted | 20:21 |
| Boostisbetter | bummer, well at least things with the pocket SoC are going well. | 20:23 |
| Boostisbetter | there is always a bright side. hahahaha | 20:23 |
| minute | got in contact with the author of the patchset, it is actually a driver bug and will be fixd | 21:24 |
| minute | fixed | 21:24 |
| Boostisbetter | minute: great! Good that you got with them about it. | 21:30 |
| minute | very! | 21:31 |
| - Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66) | 23:05 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!