| - sts-q (QUIT: Remote host closed the connection) (~sts-q@2a01:41e1:2d06:2500:a682:3650:236b:b8c) | 00:07 | |
| + sts-q (~sts-q@2a01:41e1:2d06:2500:a682:3650:236b:b8c) | 00:07 | |
| + ephase (~ephase@2a01:e0a:168:1211::885) | 00:12 | |
| - alex4nder (QUIT: Ping timeout: 240 seconds) (~alexander@wsip-184-186-224-227.sb.sd.cox.net) | 00:17 | |
| - mjw (QUIT: Quit: Leaving) (~mark@gnu.wildebeest.org) | 00:36 | |
| - ephase (QUIT: Quit: WeeChat 3.5) (~ephase@2a01:e0a:168:1211::885) | 00:39 | |
| - Christoph_ (QUIT: Remote host closed the connection) (~Christoph@79.231.49.219) | 00:51 | |
| - oomono (QUIT: Quit: Connection closed for inactivity) (uid328183@id-328183.tinside.irccloud.com) | 00:53 | |
| minute | josch: those values sound ok? | 01:38 |
|---|---|---|
| minute | josch: 2.3v is not a big deal, it should easily recharge | 01:41 |
| - sl (QUIT: Quit: Lost terminal) (~sl@beastie.sdf.org) | 01:42 | |
| - mtm (QUIT: Ping timeout: 256 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:03 | |
| - Guest1805 (QUIT: Ping timeout: 276 seconds) (~nicolas@192-99-142-46.pool.kielnet.net) | 03:09 | |
| + nsc (~nicolas@50-49-142-46.pool.kielnet.net) | 03:10 | |
| * nsc -> Guest9508 | 03:11 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 03:21 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:08 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 04:18 | |
| - sts-q (QUIT: Ping timeout: 260 seconds) (~sts-q@2a01:41e1:2d06:2500:a682:3650:236b:b8c) | 04:44 | |
| + sts-q (~sts-q@2a01:41e1:2d38:1f00:c3f5:f3e2:8cb7:d4b4) | 04:47 | |
| + sl (~sl@beastie.sdf.org) | 05:29 | |
| josch | but how can it happen that one cell is 0.9 V less than the rest? | 07:56 |
| + alex4nder (~alexander@ip98-171-191-229.sb.sd.cox.net) | 08:26 | |
| - sl (QUIT: Ping timeout: 240 seconds) (~sl@beastie.sdf.org) | 11:14 | |
| - sts-q (QUIT: Remote host closed the connection) (~sts-q@2a01:41e1:2d38:1f00:c3f5:f3e2:8cb7:d4b4) | 11:36 | |
| + sts-q (~sts-q@2a01:41e1:2d38:1f00:c3f5:f3e2:8cb7:d4b4) | 11:40 | |
| + sl (~sl@beastie.sdf.org) | 12:05 | |
| - robin (QUIT: Remote host closed the connection) (~robin@user/terpri) | 12:10 | |
| + robin (~robin@user/terpri) | 12:11 | |
| + Christoph_ (~Christoph@p4fe73cb6.dip0.t-ipconnect.de) | 12:31 | |
| - SnowCode (PART: WeeChat 3.0) (~debian@vps-709aceac.vps.ovh.net) | 13:55 | |
| - mtm (QUIT: Ping timeout: 272 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:04 | |
| + MajorBiscuit (~MajorBisc@c-001-011-047.client.tudelft.eduvpn.nl) | 14:07 | |
| - mrus (QUIT: Remote host closed the connection) (~mrus@gateway/tor-sasl/mrus) | 16:16 | |
| + mrus (~mrus@gateway/tor-sasl/mrus) | 16:18 | |
| + pr_ (pr@faeroes.sdf.org) | 16:52 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 17:43 | |
| josch | the cell that was 2.3 V yesterday is down to 1.7 V right now while the remaining ones are still at 3.2 V | 17:44 |
| josch | i'm on the road without my AC adapter and without a screwdriver -- there is nothing I can do then, right? | 17:45 |
| josch | what should I do different next time? | 17:45 |
| josch | the battery status says that the system draws 0.000 A | 17:45 |
| josch | down to 1.6 V now... | 17:45 |
| sts-q | josch: | 18:00 |
| sts-q | I am for sure no hardware guy. That said, how exact are the different values? | 18:00 |
| sts-q | Mine show 4.5 for the first and 3.3 for all other cells all over today. | 18:00 |
| sts-q | It looks like first, the value of the first cells differs from the others | 18:00 |
| sts-q | and only later the other values change? | 18:00 |
| minute | josch: you can open it without a screwdriver, for example with a knife or fork | 18:01 |
| minute | josch: also, you should press circle 0 after checking the status, that way you make sure both kbd and motherboard lpc are in sleep mode | 18:02 |
| josch | no knife or fork with me in the train i'm afraid :D cirle-0 was pressed already yesterday and again about 9 hours ago just for good measure | 18:07 |
| minute | josch: also, you can charge the thing with almost any dc adapter that has the right barrel, for example i used the power supply of my dyson vacuum once | 18:07 |
| minute | josch: ahh, train! well, lets hope the cell survives till you find a charger, otherwise you can replace it cheaply later | 18:08 |
| vagrantc | what could possibly go wrong waving a knife around poking at a battery pack on a moving train? | 18:13 |
| josch | "mister conductor, I swear lifepo batteries are not as dangerous as you think they are!" XD | 18:15 |
| vagrantc | i have seriously wondered if i ever take a flgiht again ... how to answer the question of "are you carrying any lithium-ion batteries?" if i brought my mnt/reform | 18:17 |
| vagrantc | as lifepo4 are definitely a form of lithium-ion chemistry ... but so much more stable than what the kind the question is actually designed to catch ... | 18:18 |
| vagrantc | what would the mnt/reform look like to a security agent reading the luggage scanner? | 18:19 |
| josch | same here -- i'll report my experience with flying with the reform in june in case something funny happens | 18:22 |
| vagrantc | oh fun | 18:23 |
| minute | i heard from 2 people carrying it through airport security iirc and it went ok | 18:23 |
| minute | when i travelled to belgium and sweden with demos i checked it into luggage | 18:23 |
| minute | but those units looked more like prototypes | 18:24 |
| vagrantc | i don't know if the clear bottom would reassure someone suspicious or be helpful ... seee, it's not a bomb at all | 18:24 |
| sknebel | isnt that question tied to *spare* batteries normally? | 18:24 |
| sknebel | lots of rules in that area count installed batteries differently | 18:25 |
| vagrantc | sknebel: it's never been clear to me when asked, but i think so ... | 18:25 |
| sknebel | e.g. https://www.faa.gov/hazmat/packsafe/more_info/?hazmat=7 | 18:25 |
| sknebel | vs https://www.faa.gov/hazmat/packsafe/more_info/?hazmat=20 | 18:27 |
| vagrantc | wow, first url works, second url gets access denied ... | 18:28 |
| sknebel | weird | 18:28 |
| sknebel | the second is the referenced "For lithium batteries that are installed in a device (laptop, cell phone, camera, etc.), see the entry for "portable electronic devices, containing batteries"." | 18:29 |
| vagrantc | seem to have invoked the ire of faa.gov, can't even get to the first url that worked :) | 18:31 |
| vagrantc | archive.org to the rescue | 18:32 |
| minute | batteries installed in devices are fine according to IATA | 18:32 |
| minute | that's why we can fly all those reforms to texas with ups | 18:32 |
| vagrantc | right | 18:34 |
| sknebel | heh, yeah. heard from people developing ebikes that its easier and cheaper to ship a full bike with a prototype battery pack mounted to it than just the battery | 18:44 |
| + mjw (~mark@gnu.wildebeest.org) | 18:52 | |
| - mrus (QUIT: Ping timeout: 240 seconds) (~mrus@gateway/tor-sasl/mrus) | 19:08 | |
| + mrusme (~mrus@gateway/tor-sasl/mrus) | 19:08 | |
| - sigrid (QUIT: Ping timeout: 240 seconds) (~ftrvxmtrx@ftrv.se) | 20:08 | |
| - XgF (QUIT: Ping timeout: 248 seconds) (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 20:09 | |
| + XgF (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 20:11 | |
| + sigrid (~ftrvxmtrx@ftrv.se) | 20:15 | |
| - natalie (QUIT: Ping timeout: 272 seconds) (~natalie@user/natalie) | 20:30 | |
| cinap_lenrek | 0: stuck disabled: ffffffff | 20:33 |
| cinap_lenrek | 0: stuck enabled: 00000000 | 20:33 |
| cinap_lenrek | 32: stuck disabled: 00000000 | 20:33 |
| cinap_lenrek | 32: stuck enabled: 00000000 | 20:33 |
| cinap_lenrek | 64: stuck disabled: 00000000 | 20:33 |
| cinap_lenrek | 64: stuck enabled: 00000000 | 20:33 |
| cinap_lenrek | 96: stuck disabled: 00000000 | 20:33 |
| cinap_lenrek | 96: stuck enabled: 00000000 | 20:33 |
| cinap_lenrek | 128: stuck disabled: 00000000 | 20:33 |
| cinap_lenrek | 128: stuck enabled: 00000000 | 20:33 |
| cinap_lenrek | so seems all the PPI's are disabled? | 20:33 |
| cinap_lenrek | intid's 0-31 | 20:34 |
| cinap_lenrek | is this some trusted firmware fuckery? | 20:34 |
| cinap_lenrek | i'm trying to get the generic arm timer interrupt to work | 20:35 |
| + natalie (~natalie@user/natalie) | 20:43 | |
| * mrusme -> mrus | 20:52 | |
| - natalie (QUIT: Ping timeout: 240 seconds) (~natalie@user/natalie) | 20:55 | |
| + natalie (~natalie@user/natalie) | 21:01 | |
| - natalie (QUIT: Ping timeout: 272 seconds) (~natalie@user/natalie) | 21:09 | |
| + al3x4nder (~alexander@wsip-184-186-225-187.sb.sd.cox.net) | 21:12 | |
| al3x4nder | hey | 21:12 |
| + natalie (~natalie@user/natalie) | 21:12 | |
| - natalie (QUIT: Remote host closed the connection) (~natalie@user/natalie) | 21:13 | |
| cinap_lenrek | maybe the generic arm timer interrupt cannot be used at all? | 21:14 |
| + natalie (~natalie@user/natalie) | 21:21 | |
| - al3x4nder (QUIT: Quit: leaving) (~alexander@wsip-184-186-225-187.sb.sd.cox.net) | 21:40 | |
| - XgF (QUIT: Ping timeout: 240 seconds) (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 21:57 | |
| - sigrid (QUIT: Ping timeout: 248 seconds) (~ftrvxmtrx@ftrv.se) | 21:57 | |
| + sigrid (~ftrvxmtrx@ftrv.se) | 21:59 | |
| + XgF (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 21:59 | |
| sigrid | cinap_lenrek: you mean gpt? | 22:44 |
| cinap_lenrek | no | 22:45 |
| cinap_lenrek | i mean the armv8 timer | 22:45 |
| cinap_lenrek | it is a per core timer | 22:46 |
| cinap_lenrek | CNTPCT_EL0, CNTP_TVAL_EL0, CNTP_CTL_EL0 | 22:48 |
| cinap_lenrek | interrupt according to devicetree is standard 14, which maps to intid 30 | 22:48 |
| cinap_lenrek | that thing works just out of the box on raspberry pi | 22:50 |
| sigrid | I see an example here: https://github.com/aohzju/gicDemo/blob/master/gicv3.c | 22:50 |
| sigrid | don't know how accurate that is | 22:50 |
| cinap_lenrek | i already have a prooven gic implementation | 22:51 |
| sigrid | yeah there is a timer example at the bottom too | 22:52 |
| sigrid | which I can't parse tbh | 22:52 |
| cinap_lenrek | interesting, this accesses ICC_CTLR_EL3 | 22:53 |
| khm | how did you even find that? searching for "GEN_TIMER_INTID"? | 22:54 |
| - natalie (QUIT: Quit: quit) (~natalie@user/natalie) | 22:54 | |
| khm | some kind of arm-sniffing internet sorcery | 22:55 |
| cinap_lenrek | its in the generic timer documentation and they suggest that mapping | 22:55 |
| cinap_lenrek | but i checked the devicetree dump from uboot | 22:55 |
| cinap_lenrek | the truth is that we'r running on a psci system | 22:56 |
| cinap_lenrek | so theres a hypervisor and secure modes and what not | 22:56 |
| cinap_lenrek | and i might have locked down shit so its not possible to enable it from the os | 22:56 |
| sigrid | khm: random people on the internet trying to program gic v3 | 22:58 |
| + natalie (~natalie@user/natalie) | 22:58 | |
| cinap_lenrek | the gic spec is 788 pages ;) | 22:58 |
| cinap_lenrek | they created a monster | 22:58 |
| sigrid | yeah, it's horrendous | 22:58 |
| sl | the spec is not the solution to the problem, the spec IS the problem | 22:58 |
| cinap_lenrek | i'm out of time for today | 22:59 |
| cinap_lenrek | at least we got to userspace | 22:59 |
| cinap_lenrek | spi interrupts might actually work as i got it to fire during experimentation | 23:00 |
| cinap_lenrek | so at least mmu stuff seems to work as expected | 23:00 |
| sigrid | noice | 23:00 |
| cinap_lenrek | sigrid: thanks for the example, but i think i will not be able to access ICC_CTLR_EL3 | 23:02 |
| sigrid | did you also have to do any security group stuff in your gicv3 code? | 23:02 |
| cinap_lenrek | i *assume* we'r in non-secure EL1 | 23:03 |
| cinap_lenrek | i have to tripple check this | 23:04 |
| minute | nice | 23:07 |
| - MajorBiscuit (QUIT: Ping timeout: 240 seconds) (~MajorBisc@c-001-011-047.client.tudelft.eduvpn.nl) | 23:08 | |
| cinap_lenrek | yeah, manual sais only accessible in EL3 | 23:08 |
| cinap_lenrek | also exmplains why they poll the WAKER | 23:09 |
| cinap_lenrek | i determined all this init already has been done by uboot/tf | 23:09 |
| sigrid | uboot must be using that timer too I guess | 23:09 |
| cinap_lenrek | no | 23:09 |
| cinap_lenrek | uboot runs without interrupts | 23:10 |
| sigrid | huh. how does it do the countdown then, just counting cycles? | 23:10 |
| cinap_lenrek | it spins | 23:10 |
| sigrid | D: | 23:10 |
| sigrid | makes sense | 23:10 |
| cinap_lenrek | also funny the code is wrong | 23:12 |
| cinap_lenrek | they do a read/modify/write for GICR_ISENABLER0 | 23:12 |
| cinap_lenrek | but you should be able to just write the bit | 23:12 |
| cinap_lenrek | theres a corresponding clear register | 23:12 |
| cinap_lenrek | it might not be a bad idea to just try the generic timer from nxp | 23:19 |
| cinap_lenrek | as ppi's are a bit special | 23:19 |
| cinap_lenrek | and the spi's are not locked | 23:19 |
| cinap_lenrek | at least that can help narrowing it down | 23:20 |
| sigrid | I can see linux using that one | 23:23 |
| cinap_lenrek | sigrid: thats a good sign | 23:23 |
| cinap_lenrek | do we know it uses it for interrupts too? | 23:23 |
| cinap_lenrek | like it can be used as a timestamp counter for userspace too | 23:24 |
| cinap_lenrek | you can configure the counter to be userspace readable | 23:24 |
| cinap_lenrek | hm | 23:24 |
| cinap_lenrek | i wonder | 23:24 |
| cinap_lenrek | can you cat some /proc file in linux? | 23:24 |
| sigrid | yes | 23:24 |
| sigrid | https://www.kernel.org/doc/Documentation/devicetree/bindings/arm/arch_timer.txt | 23:32 |
| cinap_lenrek | sigrid: i read that to find the irq mapping and if there are quirks | 23:33 |
| cinap_lenrek | but thanks | 23:33 |
| sigrid | I'll just assume you read everything already :D | 23:33 |
| cinap_lenrek | its also possible its some stupid bug and i typoed somewhere in the ICC system register definitions | 23:33 |
| cinap_lenrek | yeah, no worry | 23:33 |
| cinap_lenrek | i'll try another interrupt source | 23:34 |
| - Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p4fe73cb6.dip0.t-ipconnect.de) | 23:34 | |
| cinap_lenrek | and go over the gic code with a clear mind another day | 23:34 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!