2014-12-13 01:57 atommann has joined #qi-hardware 2014-12-13 02:14 sb0 has joined #qi-hardware 2014-12-13 03:44 Haswell has joined #qi-hardware 2014-12-13 03:55 atommann has quit [Quit: Leaving] 2014-12-13 04:00 xiangfu has joined #qi-hardware 2014-12-13 04:29 atgreen has joined #qi-hardware 2014-12-13 04:40 whitequark: dunno, maybe there is a problem handling connection to server. For example, the connection has died, but bot hasn't been notified and hangs in a limbo 2014-12-13 04:44 had your bot's nickname been registered, i'd also speculate that there could be a problem re-identifying with nickserv 2014-12-13 04:44 which could lead to your bot disconnection, depending on nickname settings 2014-12-13 04:44 btw, you really should register the nickname 2014-12-13 04:50 atgreen has quit [Read error: Connection reset by peer] 2014-12-13 04:51 atgreen has joined #qi-hardware 2014-12-13 04:52 I still don't know what benefit would that give me 2014-12-13 05:23 mooseboobs has quit [] 2014-12-13 05:30 first of all, there is a problem of personation, second, you nickname can be stolen 2014-12-13 05:30 the benefit of ghosting and definitely getting the nickname you want 2014-12-13 05:31 and that's pretty damn annoying when somebody steals your nickname and spams channels until you get klined or ignored or banned 2014-12-13 05:34 actually bot that don't authenticate can not get associated with a user who's responsible and thus are strongly deprecated or even forbidden 2014-12-13 05:37 and during netsplits you canot join under same name since that name still is considered online, so unless you ghost it you canot re-use it 2014-12-13 05:39 oh no, ghosting will not happend during netsplit.. It will happen if connection between you and server is broken, but server doesn't know that. You reconnect, but server still thinks you are online 2014-12-13 05:41 you however should _not_ enable nick protection or you need comstantly check if some services have renamed you to protect the nick, since your auth somehow temporarily failed to work or simply got delayed 2014-12-13 05:41 kyak: right 2014-12-13 05:49 hmm 2014-12-13 05:51 whitequark: anyway, other users of your irclogger might approach you any time and ask for a feature that let's bot authorize with services and maintain authorization :) 2014-12-13 05:51 the bot can do that alright 2014-12-13 05:51 ah, ok 2014-12-13 05:51 I'm just too lazy to actually register on freenode 2014-12-13 05:51 and I don't want to bring it down too 2014-12-13 05:52 can you issue commands on behalf of the bot? 2014-12-13 05:52 like send messages? 2014-12-13 05:53 no 2014-12-13 05:53 an account also has associated email addr, it's the proof the bot is legit and also the point of contact when anything goes haywire. Best common practice is to unhide mail for bots 2014-12-13 05:54 see /msg nickserv info infobot 2014-12-13 05:55 infobot account has "[Notice] -NickServ- apt has enabled nick protection" which I strongly discourage to do 2014-12-13 05:57 you also have less join restrictions regarding throttling etc when you're registered, and bot *accounts* can even get extended number of channels allowed 2014-12-13 06:28 (( if you have any robust anti-netsplit measure in mind, I'm happy to oblige)) the only strategy is to detect when bot isn't really online anymore (for that you ideally send a ping message to yourself every few minutes) and in case any conectivity issues are detected, the bot ideally does a complete relogin/re-auth 2014-12-13 06:29 infobot is pretty bad at that, she doesn't detect when a netsplit kicked her off some channels. You always get an "all ok" when you ask ~+chaninfo 2014-12-13 06:30 so you probably want to implement sth better than what infobot does now 2014-12-13 06:31 Tim more than once said "scheduler needs a complete rewrite" - alas nobody has the time to do that 2014-12-13 06:51 rejon has joined #qi-hardware 2014-12-13 06:59 jekhor__ has joined #qi-hardware 2014-12-13 07:02 whitequark, seems to be both pump plus some oil 2014-12-13 07:13 wouldn't oil eventually start evaporating/boiling and thus limit the vacuum you could reach? 2014-12-13 07:14 yes, it does 2014-12-13 07:14 well if you use oil designed for vacuum pumps, it doesn't boil 2014-12-13 07:15 but there's always some evaporation and it's a problem in sensitive systems 2014-12-13 07:15 whitequark: in latest c't-hacks err make: there's an awesome fsckdup magnetic "levitation" circuit that only works because the circuit doesn't do what the designer thought it would 2014-12-13 07:16 ultra high vacuum use a liquid nitrogen cryogenic trap that condenses oil vapors before they reach the vacuum chamber, or a dry (scroll) pump 2014-12-13 07:16 #2 is what most modern/rich labs use afaict 2014-12-13 07:20 :nod: 2014-12-13 07:20 ((levitation)) we commented exactly same circuit concept here in this chan a year and some ago 2014-12-13 07:23 they placed a light sensor next to the flashlight's bulb to sense distance to object by increase of brightness from reflected flashlight light by object. errr, make that a hall sensor and electromagnet 2014-12-13 07:24 that's honestly so idiotic it's amazing it works at all 2014-12-13 08:57 pcercuei has joined #qi-hardware 2014-12-13 09:02 kilae has joined #qi-hardware 2014-12-13 09:09 jekhor_ has joined #qi-hardware 2014-12-13 09:12 jekhor__ has quit [Ping timeout: 264 seconds] 2014-12-13 09:17 rejon has quit [Ping timeout: 260 seconds] 2014-12-13 09:29 xiangfu has quit [Remote host closed the connection] 2014-12-13 09:34 kilae has quit [Quit: ChatZilla 0.9.91 [Firefox 34.0.5/20141126041045]] 2014-12-13 09:54 rejon has joined #qi-hardware 2014-12-13 09:56 dandon has quit [Ping timeout: 265 seconds] 2014-12-13 10:03 rejon has quit [Ping timeout: 265 seconds] 2014-12-13 10:20 rejon has joined #qi-hardware 2014-12-13 10:31 pcercuei has quit [Remote host closed the connection] 2014-12-13 10:32 pcercuei has joined #qi-hardware 2014-12-13 10:51 wej has quit [Ping timeout: 258 seconds] 2014-12-13 10:56 wej has joined #qi-hardware 2014-12-13 11:01 wej has quit [Ping timeout: 272 seconds] 2014-12-13 11:06 wej has joined #qi-hardware 2014-12-13 11:11 kilae has joined #qi-hardware 2014-12-13 11:34 jekhor__ has joined #qi-hardware 2014-12-13 11:38 jekhor_ has quit [Ping timeout: 250 seconds] 2014-12-13 11:46 rejon has quit [Ping timeout: 260 seconds] 2014-12-13 11:58 rejon has joined #qi-hardware 2014-12-13 12:14 xiangfu has joined #qi-hardware 2014-12-13 12:25 Haswell has quit [Quit: Saliendo] 2014-12-13 13:04 nicksydney has quit [Remote host closed the connection] 2014-12-13 13:05 nicksydney has joined #qi-hardware 2014-12-13 13:29 kilae has quit [Quit: ChatZilla 0.9.91 [Firefox 34.0.5/20141126041045]] 2014-12-13 13:38 astr has joined #qi-hardware 2014-12-13 14:10 the heck, deadly receiver weapon: http://www.research-electronics.com/cgi-bin/main.cgi?action=viewprod&ct=products&num=OSCOR%20Blue 2014-12-13 14:11 >>The OSCOR Blue is listed on the United States Munitions List (USML) and requires an export license under the International Traffic in Arms Regulations (ITAR) << 2014-12-13 14:15 while TALAN is rather pathetic 2014-12-13 14:16 actually I searched for >>Non-linear Junction Detector<< 2014-12-13 14:17 poor man's NLJ-detector: microwave and watch the smoke ;-P 2014-12-13 14:28 xiangfu has quit [Quit: leaving] 2014-12-13 14:29 mooseboobs has joined #qi-hardware 2014-12-13 14:29 hey, you can find useful data at the most weird locations ;-) http://www.research-electronics.com/system/products/OSCOR Green/Custom_Span_Lists.zip 2014-12-13 14:31 Telecom LTE.csv is funny 2014-12-13 14:34 LOL, quite a huge range: >> Mobile-Satellite / Radiodetermination-Satellite,2.48350E+06,2.49500E+09 << 2014-12-13 14:35 I guess this must be a typo 2014-12-13 14:35 the mantissas are too similar 2014-12-13 14:38 ok, this .zip has some nonsense in it: >> WiFi 802.11,2.40E+09 [START!], 5.82500E+09[STOP!] << followed by line >> WiFi 2.4 GHz band (802.11b/g/n/ad),2.40E+09,2.50E+09 << 2014-12-13 14:42 http://www.research-electronics.com/system/products/OSCOR Green/OSCOR_Green_Brochure.pdf awesome spectrum analyzer: 10kHz ~ 24GHz 2014-12-13 14:53 FrankBlues has joined #qi-hardware 2014-12-13 14:55 jekhor_ has joined #qi-hardware 2014-12-13 14:59 jekhor__ has quit [Ping timeout: 272 seconds] 2014-12-13 15:13 ooh, and actually pretty cheap: >>Our Price: $36,000.00<< 2014-12-13 15:46 kilae has joined #qi-hardware 2014-12-13 15:55 ChanServ has quit [shutting down] 2014-12-13 16:24 ChanServ has joined #qi-hardware 2014-12-13 16:32 sb0 has quit [Quit: Leaving] 2014-12-13 16:51 jekhor_ has quit [Ping timeout: 260 seconds] 2014-12-13 16:54 tumdedum has quit [Ping timeout: 255 seconds] 2014-12-13 16:57 tumdedum has joined #qi-hardware 2014-12-13 17:03 tumdedum has quit [Ping timeout: 250 seconds] 2014-12-13 17:07 tumdedum has joined #qi-hardware 2014-12-13 17:30 FrankBlues has quit [Remote host closed the connection] 2014-12-13 18:05 wpwrak has quit [Read error: Connection reset by peer] 2014-12-13 18:09 wpwrak has joined #qi-hardware 2014-12-13 18:10 hmm, this is what happens if you kill the busiest processes, and X is among them ... :( 2014-12-13 18:11 i wish chromium would just not run tabs that aren't selected. then all those auto-reloading sites that have some sort of memory leak wouldn't have such an easy time crippling the system 2014-12-13 18:36 rejon has quit [Ping timeout: 265 seconds] 2014-12-13 19:22 pcercuei: if I understand things correctly we should not implement PIN_CONFIG_BIAS_PULL_DEFAULT 2014-12-13 19:22 why not? 2014-12-13 19:22 according to the documentation that's only for chips where you don't know the direction 2014-12-13 19:23 or the direction is set dynamically by the hardware depending on other parameters 2014-12-13 19:23 like the selected peripheral 2014-12-13 19:23 ok 2014-12-13 19:23 I thought it was to enable either pull-down or pull-up 2014-12-13 19:34 on the subject of pinctrl, I had to make a small change since there are no enable/disable handlers anymore, only a set handler 2014-12-13 19:34 when migrating to 3.18 2014-12-13 19:35 ok 2014-12-13 19:35 .set_mux to be exact 2014-12-13 19:36 also I put it in a subdir drivers/pinctrl/ingenic/ since many other pinctrl drivers have been grouped by hardware vendor 2014-12-13 19:42 but it doesn't really make sense, since we only have one driver there 2014-12-13 19:45 there will be separate drivers for the jz47xx series, won't there? 2014-12-13 19:45 I don't think so 2014-12-13 19:46 you mean all the differences can be pushed into DT? 2014-12-13 19:46 even so, wouldn't you need example DT configs somewhere then? 2014-12-13 19:47 or are those until arch/mips? 2014-12-13 19:47 s/until/under/ 2014-12-13 19:47 mth meant: "or are those under arch/mips?" 2014-12-13 19:55 I mean that there are almost no differences 2014-12-13 20:15 I thought the pin mapping itself is quite different 2014-12-13 20:24 I refactored things to be 3 different level 2014-12-13 20:24 top level, is generic stuff 2014-12-13 20:24 second level is either gen1 or gen2 2014-12-13 20:24 and the bottom level is the SoC itself which has the pinmap and mux maps, etc 2014-12-13 20:25 gen1 is for <=jz4760 and gen2 is for >=jz4770 2014-12-13 20:26 they kind of reshufeld the register map between those 2014-12-13 20:26 when using DT the last level would be described in the DT 2014-12-13 20:28 wej has quit [Ping timeout: 258 seconds] 2014-12-13 20:28 ah, it seems the .dts fiels are under arch/, so maybe there wouldn't be many files in the jz pinctrl driver then 2014-12-13 20:30 the subfolder probably doesn't hurt 2014-12-13 20:34 wej has joined #qi-hardware 2014-12-13 21:31 jekhor_ has joined #qi-hardware 2014-12-13 21:57 jekhor_ has quit [Remote host closed the connection] 2014-12-13 21:58 jekhor_ has joined #qi-hardware 2014-12-13 22:15 kilae has quit [Quit: ChatZilla 0.9.91 [Firefox 34.0.5/20141126041045]] 2014-12-13 22:45 Haswell has joined #qi-hardware 2014-12-13 22:48 Haswell has quit [Max SendQ exceeded] 2014-12-13 23:00 jekhor_ has quit [Ping timeout: 260 seconds] 2014-12-13 23:07 ChanServ has quit [*.net *.split] 2014-12-13 23:10 ChanServ has joined #qi-hardware 2014-12-13 23:11 Haswell has joined #qi-hardware 2014-12-13 23:20 Haswell has quit [Quit: Saliendo] 2014-12-13 23:24 ChanServ has quit [*.net *.split] 2014-12-13 23:25 Haswell has joined #qi-hardware 2014-12-13 23:28 ChanServ has joined #qi-hardware 2014-12-13 23:31 ChanServ has quit [*.net *.split] 2014-12-13 23:34 Haswell has quit [Quit: Saliendo] 2014-12-13 23:36 ChanServ has joined #qi-hardware 2014-12-13 23:38 Luke-Jr has quit [Excess Flood] 2014-12-13 23:39 Luke-Jr has joined #qi-hardware 2014-12-13 23:42 Haswell has joined #qi-hardware