| 00:00.08 | wpwrak | not if you look at catch 22 as a means to prevent change :) |
| 00:00.35 | wpwrak | "you must be sane to be allowed to leave, but if you were sane, you wouldn't be here" |
| 00:13.19 | *** join/#qi-hardware arossdotme (~astr@79-69-195-102.dynamic.dsl.as9105.com) |
| 01:37.50 | DocScrutinizer05 | sounds about right |
| 01:39.26 | DocScrutinizer05 | I wonder if Rigol scope runs sth like a VNCserver |
| 02:17.16 | *** join/#qi-hardware sb0 (~sb0@124244181048.ctinets.com) |
| 02:35.36 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a027:21::4e) |
| 02:51.08 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a027:21::4e) |
| 03:24.45 | *** join/#qi-hardware Haswell (~Haswell@unaffiliated/haswell) |
| 03:31.30 | *** join/#qi-hardware atgreen (~user@CPE687f74122463-CM84948c2e0610.cpe.net.cable.rogers.com) |
| 05:34.41 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 06:07.33 | roh | .s |
| 06:09.15 | whitequark | wpwrak: not a ban |
| 06:09.40 | whitequark | the law makes it legal to forbid such people from getting a license |
| 06:09.54 | whitequark | i.e. it is at discretion of the doctor |
| 06:09.59 | whitequark | will likely be used for selective enforcement |
| 06:12.53 | wpwrak | so at the level of that law it sounds pretty harmless. i would kinda expect to find such things everywhere. |
| 06:13.11 | wpwrak | and yes, selective enforcement is of course an issue. again, everywhere ... |
| 06:14.00 | whitequark | russia has a history of punitive psychiatry... |
| 06:14.06 | whitequark | so, no, I do not see it as harmless |
| 06:14.41 | whitequark | not to mention the timing of the law |
| 06:16.08 | wpwrak | (harmless) i mean that you probably have a provision in any country that you can be declared unfit to drive for medical conditions |
| 06:16.57 | wpwrak | if it's not some blanket "for whatever reason" (to be defined by some rules governed my the entity in charge of administering licenses) |
| 06:17.29 | whitequark | depends on context. I mean, there always was a provision that you can't drive if you're blind or can't use the controls |
| 06:17.54 | whitequark | however, adding a provision on "behavioral disorders" right in the middle of crackdown on lgbt is uh |
| 06:18.07 | wpwrak | at least insensitive :) |
| 06:18.59 | mth | the message seems to be that if you don't conform to the norm, they want you to keep your mouth shut about it |
| 06:19.15 | whitequark | of course |
| 06:21.05 | wpwrak | luckily, in the free world, we regularly share our most intimate details, especially those of a sexual nature, with the world at large and only experience friendly acceptance and support ;-) |
| 06:23.02 | wpwrak | the difference seems to be more along the lines of people in .ru staying in their closets because they fear bad things will happen while people in other countries stay in their closets because they fear bad things may happen |
| 06:23.14 | wpwrak | (for whatever the closet may be) |
| 06:29.26 | mth | there are different meanings to "sexual"... setting orientation to "gay" in a profile is not the same as posting bedroom videos |
| 06:29.39 | mth | but in either case, I don't think it's any business of the state |
| 06:30.20 | whitequark | ^ |
| 06:30.50 | whitequark | note that the russian state does not actually care, it needs a scapegoat |
| 06:30.58 | wpwrak | i'd agree with that. but it seems they just copied their list of problematic conditions from the WHO. they may not even have paid much attention to the details. |
| 06:31.15 | wpwrak | (or maybe it's just included by reference) |
| 06:31.49 | mth | my guess is they just quoted the WHO as a "look, we didn't make this up" excuse |
| 06:31.55 | whitequark | slipping something problematic hidden in a larger packet of law is a very common tactic |
| 06:32.24 | wpwrak | i.e., i can easily see how you end up with this constellation if all you want is to say that driving licenses can be denied if 1) the applicant suffers a recognized medical condition and 2) a doctor says it's bad enough to be a reason to not let that person drive. |
| 06:33.08 | whitequark | frankly, I don't care whether the intent was malicious or not. the result *will* be used maliciously, as evident from, say, how it happens in USA |
| 06:33.25 | whitequark | where similar laws *are* selectively enforced against even the same groups |
| 06:34.12 | whitequark | lack of knowledge of law does not absolve you of responsibility. then how lack of understanding of consequences absolves the lawmaker from it? |
| 06:34.20 | wpwrak | yeah, it's probably not the most clever law. i wonder if the lawmakers went "oops" after they realized the implications. |
| 06:34.29 | wpwrak | hehe ;-) |
| 06:34.55 | whitequark | "oops"? more like "yay" |
| 06:35.10 | wpwrak | hehe :) |
| 06:35.31 | whitequark | I'm not being sarcastic, transphobic and proud of it MPs are abundant |
| 06:41.09 | wpwrak | perhaps a general lack of neutral viewpoint in those folks ? |
| 06:44.24 | wpwrak | of course, kant would approve :) "if you don't like someone's idiosyncrasies, then there should be a universal law against them" |
| 06:50.20 | wpwrak | but i guess such things will even themselves out in a couple of generations if russia can avoid any major societal upset for that long |
| 06:51.05 | wpwrak | an aggressive stance against minorities is quite typical in societies that have a recent history of distress |
| 06:54.00 | wpwrak | where "minorities" is any kind of "outlier" perceived as negative. of course, the definition of "negative" can vary |
| 06:55.22 | wpwrak | e.g., in russia it's probably quite okay to be a flamboyant atheist. now try that in the caliphate ... |
| 07:10.40 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 07:13.12 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 07:19.34 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 07:20.15 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 07:52.43 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 07:52.43 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 07:52.43 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 07:53.36 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 08:16.05 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 08:19.23 | *** join/#qi-hardware jekhor__ (~jek@134.17.144.64) |
| 08:24.58 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 08:27.38 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 08:33.18 | qi-bot | [commit] Werner Almesberger: gui_canvas.c (key_press_event): make / rotate through packages as well (master) http://qi-hw.com/p/fped/5fdea0e |
| 08:59.38 | kyak | despite all, the title couldn't be more yellow |
| 08:59.43 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 08:59.48 | kyak | of course, they had to mention putin |
| 09:06.37 | kyak | frankly, the more western media/politics bash Putin _personally_, the more support he will get in Russia |
| 09:07.34 | kyak | i don't know if this is a pecularity of russians or if the same psyhologically will work in any other country |
| 09:16.32 | larsc | and he probably knows that |
| 09:21.53 | viric | it's a bit similar with president Mas in Catalonia |
| 09:22.20 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 09:22.29 | viric | a right wing man that never was pro-independence, until last elections. He managed to convince enough people, and Spanish media proclaim everywhere that "Mas is the messiah of independence" |
| 09:22.33 | *** join/#qi-hardware wolfspraul (~wolfsprau@brln-4d073968.pool.mediaWays.net) |
| 09:23.28 | viric | while Mas has always been the major ballast in the independence movement. |
| 09:24.25 | viric | As the Spaniards attack Mas personally, he gets more support from the pro-independence, while he is the ballast towards independence. |
| 09:24.40 | wpwrak | hmm, principal monitor going into suspend all the time. interestingly, another monitor on the same card doesn't. but i think the card is still trying to tell me something there ... like, that's it's envious of the recent retirement of its long-time neighbour. |
| 09:27.12 | kyak | wpwrak: does it going suspend correlate with political discussions on this channel? :) |
| 09:27.58 | wpwrak | hmm. now that you mention it. maybe it got some separatist ideas ... |
| 09:33.37 | kyak | your monitor is corrupted, you should through it away. Or, and your video card, too |
| 09:34.03 | kyak | shit, you just started loving them even more..! |
| 09:46.21 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 09:47.19 | viric | :) |
| 10:05.40 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 11:05.32 | *** join/#qi-hardware rozzin (~rozzin@209-20-69-211.slicehost.net) |
| 11:14.52 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 11:54.48 | *** join/#qi-hardware dandon (~dandon@88.151.79.117) |
| 12:11.45 | *** join/#qi-hardware jekhor__ (~jek@port-162-adslby-pool37.infonet.by) |
| 12:22.22 | *** join/#qi-hardware jekhor__ (~jek@port-162-adslby-pool37.infonet.by) |
| 12:28.27 | *** join/#qi-hardware jekhor__ (~jek@port-162-adslby-pool37.infonet.by) |
| 13:40.47 | *** join/#qi-hardware jekhor (~jek@port-217-adslby-pool36.infonet.by) |
| 15:38.15 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 15:56.30 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 16:25.55 | *** join/#qi-hardware pcercuei (~pcercuei@95.91.238.32) |
| 16:35.25 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 16:47.04 | larsc | hm, I'm thinking that the TCU thingy is a CPU bug |
| 16:48.07 | larsc | or compiler |
| 16:48.42 | larsc | This is what the clockevent IRQ handler looks like https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/mips/jz4740/time.c#n46 |
| 16:48.58 | larsc | notice the jz4740_timer_disable() if the mode is not periodic |
| 16:49.13 | larsc | if I remove that the timer does not get disabled when the watchdog is enabled |
| 16:49.43 | larsc | but if I replace the disable() with a printk I never see the printk either |
| 16:50.09 | larsc | putting some random other instructions before or after the disable also fixes the bug |
| 16:51.04 | larsc | and the bug only happens if TIMER_CLOCKEVENT is 0 |
| 16:52.32 | larsc | the asm http://pastebin.com/3fgSC28h |
| 16:59.55 | larsc | yep, that's a compiler bug |
| 17:00.52 | pcercuei | :/ |
| 17:01.00 | larsc | It always writes to JZ_REG_TIMER_ENABLE_CLEAR |
| 17:01.19 | larsc | if mode is != CLOCK_EVT_MODE_PERIODIC |
| 17:01.26 | larsc | it reads the current value from the register |
| 17:01.30 | larsc | and then writes it back |
| 17:01.36 | larsc | thing is the register is not readable |
| 17:01.45 | larsc | and reading it will return garbage |
| 17:02.02 | larsc | I guess it aliases with the WATCHDOG enable register |
| 17:02.13 | larsc | since the bug only happens when the watchdog is enabled |
| 17:02.20 | *** join/#qi-hardware jwhitmore (~jwhitmore@host217-43-211-43.range217-43.btcentralplus.com) |
| 17:02.33 | larsc | so it reads back 1 and writes 1 to the register and hence disables the TCU0 |
| 17:03.02 | larsc | screw you gcc! |
| 17:03.28 | wpwrak | seems that it's gcc who's doing the screwing this time :) |
| 17:03.37 | wpwrak | and not on itself :) |
| 17:05.19 | larsc | basically what the asm translates to is |
| 17:05.21 | larsc | val = readb(JZ_REG_TIMER_ENABLE_CLEAR); if (cd->mode == CLOCK_EVT_MODE_PERIODIC) val = 1; writeb(val, JZ_REG_TIMER_ENABLE_CLEAR); |
| 17:06.04 | mth | which version of GCC are you using? |
| 17:06.47 | larsc | '(OpenWrt/Linaro GCC 4.6-2012.12 r37492) 4.6.4' |
| 17:10.44 | mth | if you have a minimal test case, I can compile it on 4.9.1 to check whether the issue still exists |
| 17:11.09 | mth | actually 4.9.2 is out, but I haven't built that yet |
| 17:19.30 | larsc | http://pastebin.com/zH2enADr with -O2 |
| 17:21.45 | mth | larsc: http://www.treewalker.org/temp/clockbug.s |
| 17:23.22 | larsc | your webserver does not respond |
| 17:24.00 | mth | fixed |
| 17:25.32 | larsc | looks better |
| 17:25.38 | larsc | no ldu |
| 17:27.10 | larsc | Guess it's time to update the toolchain |
| 17:34.36 | pcercuei | that explains why you had problems with the watchdog driver that we didn't have |
| 17:35.19 | larsc | yep |
| 17:52.37 | larsc | 4.8 looks like it works |
| 17:54.14 | larsc | oh no, started make -j and forgot the number |
| 18:04.38 | pcercuei | :D |
| 18:05.12 | larsc | looks like it's not coming back to life |
| 18:09.08 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 18:10.04 | wpwrak | victory ! low-cost solution: find a DVD-D cable to use my one spare DVI port instead of the failing VGA |
| 18:11.09 | larsc | DVD-D? |
| 18:11.16 | wpwrak | err, DVI-D |
| 18:11.43 | wpwrak | why can't they choose less freudian acronyms ? |
| 18:32.35 | *** join/#qi-hardware jekhor_ (~jek@port-217-adslby-pool36.infonet.by) |
| 18:43.08 | wpwrak | thanks to the internet of things, we'll soon be able to have this: https://www.youtube.com/watch?v=DJklHwoYgBQ |
| 19:47.39 | *** join/#qi-hardware arossdotme (~astr@79-69-207-100.dynamic.dsl.as9105.com) |
| 20:02.02 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 20:10.33 | *** join/#qi-hardware FAMAS (~FAMAS@182.48.84.140) |
| 20:52.13 | *** join/#qi-hardware jekhor_ (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 21:11.23 | *** join/#qi-hardware jekhor_ (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 21:35.04 | *** join/#qi-hardware jekhor_ (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 22:31.54 | DocScrutinizer05 | pcercuei: ((neo-nazi demonstrations like in the east of Germany)) last PEGIDA in Dresden, iirc 16k. Today: 35k *against* PEGIDA |
| 22:42.07 | DocScrutinizer05 | larsc: this doesn'T already spound like compiler bug. Rather I'd check my macros. They might implement bitset/bitclear on a register by readback of the register and (re)setting the bit in "Accumulator", then write back to register. That's how such stuff usually is implemented, either on opcode level or on macro level or on level of the uppermost sourcecode. And obviously that's BAD[TM] when the register is write-only |
| 22:42.32 | DocScrutinizer05 | s/spou/sou/ |
| 22:44.23 | DocScrutinizer05 | you regularly need a shadow variable mirroring the content of w/o register, do all the bit-toggling on this variable, and after each change write the var to the register |
| 22:44.45 | eintopf | wpwrak: I already thought about connecting my toilet flush into the IPv6 world |
| 22:55.36 | DocScrutinizer05 | larsc: even when the compiler uses a read-modify-write opcode for the write-only register (which obviously is illegal and an according note would show up in manual about that w/o register), it's not the compiler's fault. You need to tell the compiler about the very special case that this particular register is not readable. By whatever means, worst case by using inline assembler |
| 23:14.18 | eintopf | the use case would be: you sitting on the toilet (you know it will take longer) sometimes you need the toilet flush and turn around. |
| 23:14.31 | eintopf | With smartphone in your hand you can push a big button :) |
| 23:14.48 | eintopf | instead of turning around and search the flush key |
| 23:15.17 | eintopf | s/you need the toilet/you need to hit the toilet/ |
| 23:32.22 | *** join/#qi-hardware jwhitmore (~jwhitmore@host81-148-224-110.range81-148.btcentralplus.com) |
| 23:50.29 | *** join/#qi-hardware arossdotme (~astr@79-69-206-107.dynamic.dsl.as9105.com) |