Wednesday, 2017-01-04

*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #minnowboard00:00
*** vstehle <vstehle!> has quit IRC00:04
*** stephano <stephano!~stephano@> has joined #minnowboard00:49
*** jimt <jimt!~jim@2610:160:11:33:8d0a:cdd7:b090:8217> has quit IRC01:19
*** agust <agust!> has quit IRC01:32
*** jimt <jimt!~jim@2610:160:11:33:3d57:5290:1a0a:2b41> has joined #minnowboard01:59
*** jimt <jimt!~jim@2610:160:11:33:3d57:5290:1a0a:2b41> has quit IRC02:07
*** calculus <calculus!~calculus@gentoo/user/calculus> has joined #minnowboard02:10
*** m_w <m_w!> has joined #minnowboard02:17
*** gonzopancho <gonzopancho!~jim@2610:160:11:33:3d57:5290:1a0a:2b41> has joined #minnowboard02:17
*** gonzopancho <gonzopancho!~jim@2610:160:11:33:3d57:5290:1a0a:2b41> has quit IRC02:23
*** gonzopancho <gonzopancho!~Jim_Thomp@2610:160:11:33:3d57:5290:1a0a:2b41> has joined #minnowboard02:23
*** m_w <m_w!> has quit IRC04:03
*** Guest65710 is now known as kushal04:07
*** kushal <kushal!~figo@> has quit IRC04:08
*** kushal <kushal!~figo@fedora/kushal> has joined #minnowboard04:08
warthog9Bitweasil: I'm reasonably sure (without diggin through things) the S5 gpios route through to the sus block04:33
warthog9Bitweasil: core vs. sus is roughly core come off the main chunk of the soc, the sus come off another block bolted onto the main core of the soc04:34
warthog9since there's 3 gpio providers in the SoC04:34
warthog9(at least the E38xx series)04:34
*** gonzopancho <gonzopancho!~Jim_Thomp@2610:160:11:33:3d57:5290:1a0a:2b41> has quit IRC05:07
*** gonzopancho <gonzopancho!~Jim_Thomp@2610:160:11:33:c8d1:dd11:7558:6e7a> has joined #minnowboard05:21
*** vstehle <vstehle!> has joined #minnowboard06:00
*** gonzopancho <gonzopancho!~Jim_Thomp@2610:160:11:33:c8d1:dd11:7558:6e7a> has quit IRC06:04
*** gonzopancho <gonzopancho!> has joined #minnowboard06:27
*** gonzopancho <gonzopancho!> has quit IRC06:30
*** gonzopancho <gonzopancho!> has joined #minnowboard07:44
*** vaibhava <vaibhava!~vaibhava@> has quit IRC07:52
*** vaibhava <vaibhava!~vaibhava@> has joined #minnowboard07:54
*** vaibhava_ <vaibhava_!~vaibhava@> has joined #minnowboard08:10
*** vaibhava <vaibhava!~vaibhava@> has quit IRC08:10
*** vaibhava_ <vaibhava_!~vaibhava@> has quit IRC08:14
*** vaibhava <vaibhava!~vaibhava@> has joined #minnowboard08:43
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:31
*** agust <agust!> has joined #minnowboard11:29
BitweasilOk, thanks.  So no particular significance to the name, just different names for different blocks.14:28
BitweasilWHY is ACPI still using legacy IO ports? :p15:17
*** gonzopancho <gonzopancho!> has quit IRC16:39
*** dvhart <dvhart!~dvhart@> has joined #minnowboard16:48
*** dvhart <dvhart!~dvhart@> has quit IRC17:55
BitweasilOk, I can get my IO pins to start firing SMIs.  Now to get them to stop firing SMIs...18:01
BitweasilKinda sorta don't have a handler for that in the SMI handler, so it may be upset with me.18:02
BitweasilOh, wait, no, I'd just messed something else up. :)18:06
BitweasilNo, wait... ok, what on earth is S5_0 configured to do on the Minnowboard?18:07
BitweasilIt's routed to an SCI somehow.18:07
BitweasilI can still set off an endless stream of SMM entries on other pins.18:07
* Bitweasil goes to fiddle more.18:07
BitweasilI should probably detect those and not route them to the existing SMM handler... it doesn't seem to like them. :)18:08
BitweasilOk, I'll stop harassing pin 0...18:11
* Bitweasil goes to plow the driveway while it's not snowing actively.18:11
*** dvhart <dvhart!~dvhart@> has joined #minnowboard18:36
*** lamego <lamego!jose@nat/intel/x-vyjqjjukeasthmtq> has joined #minnowboard19:00
*** hugohagogo <hugohagogo!~cleber@> has quit IRC19:36
*** fyv <fyv!> has quit IRC19:36
*** jnavarro_ <jnavarro_!> has quit IRC19:36
*** hugohago1o <hugohago1o!~cleber@> has joined #minnowboard19:36
*** fyv <fyv!> has joined #minnowboard19:36
*** jnavarro_ <jnavarro_!> has joined #minnowboard19:36
*** dvhart <dvhart!~dvhart@> has quit IRC21:01
*** dvhart <dvhart!~dvhart@> has joined #minnowboard21:03
BitweasilInteresting.  If the SMI handler doesn't know what happened, it doesn't set end of SMI bit.21:27
*** dvhart <dvhart!~dvhart@> has quit IRC21:29
*** dvhart <dvhart!~dvhart@> has joined #minnowboard21:34
*** dvhart <dvhart!~dvhart@> has quit IRC22:16
BitweasilAll right.22:24
BitweasilGot it worked out.22:24
BitweasilY'all have a crappy manual for some of this stuff.22:24
BitweasilNOWHERE does it say, you clear the ALT_GPIO_SMI upper status bits by writing back to them.22:24
Bitweasil"These bits are sticky" is about as much clue as one gets.22:25
Bitweasil... and I've messed with enough Intel stuff to have a good idea that if writing 0s doesn't clear status bits, try writing 1s.22:25
BitweasilSeriously, the upper and lower half of that register behave differently.22:25
BitweasilI can't decide if knowing how Intel does stuff at this level is useful, or a mark of madness.22:25
BitweasilI can drive a stream of SMIs off the PWM output.22:26
BitweasilNow to clean up the code and make some *actual* paths instead of hacks...22:26
BitweasilI think I'll go with "Mark of Madness."22:28
Bitweasilm'kay.  Guess you don't need to set end of SMI there, just clear the proper status bits.22:57
*** agust <agust!> has quit IRC23:03
*** lamego <lamego!jose@nat/intel/x-vyjqjjukeasthmtq> has quit IRC23:04
*** dvhart <dvhart!~dvhart@> has joined #minnowboard23:10
*** dvhart <dvhart!~dvhart@> has quit IRC23:12
*** dvhart <dvhart!~dvhart@> has joined #minnowboard23:13
*** dvhart <dvhart!~dvhart@> has quit IRC23:23
*** dvhart <dvhart!~dvhart@> has joined #minnowboard23:52

Generated by 2.11.0 by Marius Gedminas - find it at!