DocScrutinizer05 changed the topic of #qi-hardware to: 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
<wpwrak> not if you look at catch 22 as a means to prevent change :)
<wpwrak> "you must be sane to be allowed to leave, but if you were sane, you wouldn't be here"
arossdotme has joined #qi-hardware
<DocScrutinizer05> sounds about right
<DocScrutinizer05> I wonder if Rigol scope runs sth like a VNCserver
sb0 has joined #qi-hardware
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
wej has quit [Ping timeout: 245 seconds]
wej has joined #qi-hardware
Haswell has joined #qi-hardware
atgreen has quit [Read error: Connection reset by peer]
atgreen has joined #qi-hardware
xiangfu has joined #qi-hardware
xiangfu has quit [Ping timeout: 245 seconds]
<roh> .s
<whitequark> wpwrak: not a ban
<whitequark> the law makes it legal to forbid such people from getting a license
<whitequark> i.e. it is at discretion of the doctor
<whitequark> will likely be used for selective enforcement
<wpwrak> so at the level of that law it sounds pretty harmless. i would kinda expect to find such things everywhere.
<wpwrak> and yes, selective enforcement is of course an issue. again, everywhere ...
<whitequark> russia has a history of punitive psychiatry...
<whitequark> so, no, I do not see it as harmless
<whitequark> not to mention the timing of the law
<wpwrak> (harmless) i mean that you probably have a provision in any country that you can be declared unfit to drive for medical conditions
<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)
<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
<whitequark> however, adding a provision on "behavioral disorders" right in the middle of crackdown on lgbt is uh
<wpwrak> at least insensitive :)
<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
<whitequark> of course
<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 ;-)
<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
<wpwrak> (for whatever the closet may be)
<mth> there are different meanings to "sexual"... setting orientation to "gay" in a profile is not the same as posting bedroom videos
<mth> but in either case, I don't think it's any business of the state
<whitequark> ^
<whitequark> note that the russian state does not actually care, it needs a scapegoat
<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.
<wpwrak> (or maybe it's just included by reference)
<mth> my guess is they just quoted the WHO as a "look, we didn't make this up" excuse
<whitequark> slipping something problematic hidden in a larger packet of law is a very common tactic
<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.
<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
<whitequark> where similar laws *are* selectively enforced against even the same groups
<whitequark> lack of knowledge of law does not absolve you of responsibility. then how lack of understanding of consequences absolves the lawmaker from it?
<wpwrak> yeah, it's probably not the most clever law. i wonder if the lawmakers went "oops" after they realized the implications.
<wpwrak> hehe ;-)
<whitequark> "oops"? more like "yay"
<wpwrak> hehe :)
<whitequark> I'm not being sarcastic, transphobic and proud of it MPs are abundant
<wpwrak> perhaps a general lack of neutral viewpoint in those folks ?
<wpwrak> of course, kant would approve :) "if you don't like someone's idiosyncrasies, then there should be a universal law against them"
<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
<wpwrak> an aggressive stance against minorities is quite typical in societies that have a recent history of distress
idundidit has quit [Remote host closed the connection]
<wpwrak> where "minorities" is any kind of "outlier" perceived as negative. of course, the definition of "negative" can vary
<wpwrak> e.g., in russia it's probably quite okay to be a flamboyant atheist. now try that in the caliphate ...
FAMAS has quit [Ping timeout: 240 seconds]
FAMAS has joined #qi-hardware
FAMAS has quit [Max SendQ exceeded]
FAMAS has joined #qi-hardware
FAMAS has quit [Max SendQ exceeded]
FAMAS has joined #qi-hardware
FAMAS has quit [Max SendQ exceeded]
FAMAS has joined #qi-hardware
FAMAS has quit [Max SendQ exceeded]
infobot has quit [Ping timeout: 244 seconds]
infobot has joined #qi-hardware
FAMAS has joined #qi-hardware
xiangfu has joined #qi-hardware
jekhor__ has joined #qi-hardware
FAMAS has quit [Read error: Connection reset by peer]
FAMAS has joined #qi-hardware
FAMAS has quit [Read error: Connection reset by peer]
FAMAS has joined #qi-hardware
FAMAS has quit [Read error: Connection reset by peer]
<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
xiangfu has quit [Ping timeout: 255 seconds]
wpwrak has quit [Read error: Connection reset by peer]
<kyak> despite all, the title couldn't be more yellow
xiangfu has joined #qi-hardware
<kyak> of course, they had to mention putin
<kyak> frankly, the more western media/politics bash Putin _personally_, the more support he will get in Russia
<kyak> i don't know if this is a pecularity of russians or if the same psyhologically will work in any other country
<larsc> and he probably knows that
<viric> it's a bit similar with president Mas in Catalonia
wpwrak has joined #qi-hardware
<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"
wolfspraul has joined #qi-hardware
<viric> while Mas has always been the major ballast in the independence movement.
<viric> As the Spaniards attack Mas personally, he gets more support from the pro-independence, while he is the ballast towards independence.
<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.
<kyak> wpwrak: does it going suspend correlate with political discussions on this channel? :)
<wpwrak> hmm. now that you mention it. maybe it got some separatist ideas ...
<kyak> your monitor is corrupted, you should through it away. Or, and your video card, too
<kyak> shit, you just started loving them even more..!
xiangfu has quit [Ping timeout: 265 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
<viric> :)
xiangfu has joined #qi-hardware
sb0 has quit [Quit: Leaving]
xiangfu has quit [Ping timeout: 256 seconds]
jekhor__ has quit [Ping timeout: 245 seconds]
rozzin has quit [Ping timeout: 264 seconds]
rozzin has joined #qi-hardware
xiangfu has joined #qi-hardware
Haswell has quit [Quit: Saliendo]
xiangfu has quit [Remote host closed the connection]
dandon has joined #qi-hardware
jekhor__ has joined #qi-hardware
jekhor__ has quit [Read error: Connection reset by peer]
jekhor__ has joined #qi-hardware
jekhor__ has quit [Read error: Connection reset by peer]
jekhor__ has joined #qi-hardware
jekhor__ has quit [Read error: Connection reset by peer]
jekhor has joined #qi-hardware
Nik05 has quit [Read error: Connection reset by peer]
Nik05 has joined #qi-hardware
viric has quit [Ping timeout: 252 seconds]
viric has joined #qi-hardware
pcercuei has joined #qi-hardware
FAMAS has joined #qi-hardware
FAMAS has quit [Max SendQ exceeded]
<larsc> hm, I'm thinking that the TCU thingy is a CPU bug
<larsc> or compiler
<larsc> notice the jz4740_timer_disable() if the mode is not periodic
jwhitmore has quit [Ping timeout: 255 seconds]
<larsc> if I remove that the timer does not get disabled when the watchdog is enabled
<larsc> but if I replace the disable() with a printk I never see the printk either
<larsc> putting some random other instructions before or after the disable also fixes the bug
<larsc> and the bug only happens if TIMER_CLOCKEVENT is 0
<larsc> yep, that's a compiler bug
<pcercuei> :/
<larsc> It always writes to JZ_REG_TIMER_ENABLE_CLEAR
<larsc> if mode is != CLOCK_EVT_MODE_PERIODIC
<larsc> it reads the current value from the register
<larsc> and then writes it back
<larsc> thing is the register is not readable
<larsc> and reading it will return garbage
<larsc> I guess it aliases with the WATCHDOG enable register
<larsc> since the bug only happens when the watchdog is enabled
jwhitmore has joined #qi-hardware
<larsc> so it reads back 1 and writes 1 to the register and hence disables the TCU0
<larsc> screw you gcc!
<wpwrak> seems that it's gcc who's doing the screwing this time :)
<wpwrak> and not on itself :)
<larsc> basically what the asm translates to is
<larsc> val = readb(JZ_REG_TIMER_ENABLE_CLEAR); if (cd->mode == CLOCK_EVT_MODE_PERIODIC) val = 1; writeb(val, JZ_REG_TIMER_ENABLE_CLEAR);
<mth> which version of GCC are you using?
<larsc> '(OpenWrt/Linaro GCC 4.6-2012.12 r37492) 4.6.4'
<mth> if you have a minimal test case, I can compile it on 4.9.1 to check whether the issue still exists
<mth> actually 4.9.2 is out, but I haven't built that yet
<larsc> your webserver does not respond
<mth> fixed
<larsc> looks better
<larsc> no ldu
<larsc> Guess it's time to update the toolchain
<pcercuei> that explains why you had problems with the watchdog driver that we didn't have
<larsc> yep
wpwrak has quit [Quit: video adventures ...]
<larsc> 4.8 looks like it works
<larsc> oh no, started make -j and forgot the number
<pcercuei> :D
<larsc> looks like it's not coming back to life
wpwrak has joined #qi-hardware
<wpwrak> victory ! low-cost solution: find a DVD-D cable to use my one spare DVI port instead of the failing VGA
<larsc> DVD-D?
<wpwrak> err, DVI-D
<wpwrak> why can't they choose less freudian acronyms ?
jekhor_ has joined #qi-hardware
jekhor has quit [Ping timeout: 265 seconds]
<wpwrak> thanks to the internet of things, we'll soon be able to have this: https://www.youtube.com/watch?v=DJklHwoYgBQ
arossdotme has quit [Ping timeout: 264 seconds]
jekhor_ has quit [Ping timeout: 264 seconds]
arossdotme has joined #qi-hardware
FAMAS has joined #qi-hardware
FAMAS has quit [Read error: Connection reset by peer]
FAMAS has joined #qi-hardware
wolfspraul has quit [Ping timeout: 255 seconds]
jekhor_ has joined #qi-hardware
jekhor_ has quit [Read error: Connection reset by peer]
jekhor_ has joined #qi-hardware
FAMAS is now known as GALIL
GALIL is now known as FAMAS
jekhor_ has quit [Read error: Connection reset by peer]
jekhor_ has joined #qi-hardware
<DocScrutinizer05> pcercuei: ((neo-nazi demonstrations like in the east of Germany)) last PEGIDA in Dresden, iirc 16k. Today: 35k *against* PEGIDA
<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
<DocScrutinizer05> s/spou/sou/
<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
<eintopf> wpwrak: I already thought about connecting my toilet flush into the IPv6 world
<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
<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.
<eintopf> With smartphone in your hand you can push a big button :)
<eintopf> instead of turning around and search the flush key
<eintopf> s/you need the toilet/you need to hit the toilet/
jekhor_ has quit [Ping timeout: 245 seconds]
jwhitmore has quit [Ping timeout: 264 seconds]
jwhitmore has joined #qi-hardware
arossdotme has quit [Ping timeout: 256 seconds]
kristianpaul has quit [Ping timeout: 265 seconds]
arossdotme has joined #qi-hardware