| 00:14.34 | *** join/#qi-hardware guanucoluis (~luis@200.127.180.65) |
| 00:17.51 | *** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com) |
| 01:07.00 | *** join/#qi-hardware wolfspraul (~wolfsprau@221.220.189.240) |
| 01:16.51 | *** join/#qi-hardware x201 (~hzhang@222.130.135.35) |
| 03:20.05 | *** join/#qi-hardware mth (roydbdby@dhcp-089-098-069-120.chello.nl) |
| 03:37.10 | *** join/#qi-hardware x201 (~hzhang@116.213.117.66) |
| 03:52.38 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 03:54.47 | *** join/#qi-hardware heberth (~heberth@190.255.15.94) |
| 04:12.01 | *** join/#qi-hardware freakazoid0223 (~matt@pool-71-246-26-142.phlapa.fios.verizon.net) |
| 05:19.30 | *** join/#qi-hardware freespace (foobar@stark.pictorii.com) |
| 06:05.17 | *** join/#qi-hardware jluis|work (~jpddb@83.247.136.72) |
| 06:37.13 | *** join/#qi-hardware jekhor (~jek@leased-line-46-53-195-83.telecom.by) |
| 06:41.25 | *** join/#qi-hardware kristoffer (~kristoffe@c-90dae555.010-30-6c6b7012.cust.bredbandsbolaget.se) |
| 07:14.41 | *** join/#qi-hardware pabs3 (~pabs@d122-109-120-76.per801.wa.optusnet.com.au) |
| 07:21.26 | *** join/#qi-hardware kilae (~chatzilla@109.205.205.99) |
| 07:34.31 | *** join/#qi-hardware kristoffer (~kristoffe@c-90dae555.010-30-6c6b7012.cust.bredbandsbolaget.se) |
| 09:00.35 | *** join/#qi-hardware porchao (~hato@eatkyo312075.adsl.ppp.infoweb.ne.jp) |
| 09:50.18 | *** join/#qi-hardware panda|x201 (~hzhang@58.83.252.55) |
| 10:23.35 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 10:55.11 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 11:53.57 | *** join/#qi-hardware jekhor (~jek@178.120.20.33) |
| 12:03.02 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 12:29.24 | viric | if my computer hangs, but the at keyboard does not have leds blinking... does it mean it's not a panic? |
| 12:30.16 | mth | does led blinking work with usb keyboards too or just with ps/2? |
| 12:30.41 | viric | It's a ps/2 in this case. |
| 12:30.49 | viric | that's what I meant by 'at keyboard' |
| 12:31.00 | mth | ah, I read it too quickly |
| 12:31.01 | viric | I mean, if I force a crash (sysrq-c), they blink |
| 12:31.14 | viric | but when my computer hangs (sometimes), it does not blink |
| 13:10.14 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 13:28.11 | *** join/#qi-hardware panda|x201 (~hzhang@222.130.135.35) |
| 13:28.51 | whitequark | depends on your kernel version |
| 13:29.13 | whitequark | with newer kernels (3.5 is what I mean, through I'm not exactly sure when it has started), leds no more blink on panic |
| 14:11.13 | *** join/#qi-hardware cladamw (~adamwang@host-193.188-235-182.cable.dynamic.kbtelecom.net) |
| 14:26.55 | *** join/#qi-hardware porchao (~hato@eatkyo312063.adsl.ppp.infoweb.ne.jp) |
| 15:16.23 | *** join/#qi-hardware DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 15:47.48 | *** join/#qi-hardware emeb (~ericb@ip72-201-79-123.ph.ph.cox.net) |
| 16:31.07 | *** join/#qi-hardware GNUtoo (~gnutoo@ABordeaux-152-1-57-206.w82-125.abo.wanadoo.fr) |
| 16:49.18 | *** join/#qi-hardware GNUtoo (~gnutoo@ABordeaux-152-1-57-206.w82-125.abo.wanadoo.fr) |
| 16:56.14 | *** join/#qi-hardware urandom__ (~user@p54B0EDBC.dip.t-dialin.net) |
| 16:58.25 | *** join/#qi-hardware GNUtoo (~gnutoo@ABordeaux-152-1-57-206.w82-125.abo.wanadoo.fr) |
| 17:09.40 | *** join/#qi-hardware Ayla (~paul@pc-144-230-164-190.cm.vtr.net) |
| 17:47.45 | mth | larsc: do you know what the relation is between gpio and pinctrl in the Linux kernel? |
| 17:48.02 | mth | devres can manage pinctrls, but not plain gpios |
| 17:48.12 | larsc | it can |
| 17:48.37 | larsc | see drivers/gpio/devres.c |
| 18:04.05 | mth | hmm, they forgot the update devres.txt then? |
| 18:05.03 | larsc | probably |
| 18:05.08 | larsc | it is new though |
| 18:05.16 | larsc | I think 3.5 |
| 18:05.47 | mth | but in whatever version the implementation is added 3.5, the docs should be added as well ;) |
| 18:06.02 | mth | s/3.5/in/ |
| 18:06.02 | qi-bot | mth meant: "but in whatever version the implementation is added in, the docs should be added as well ;)" |
| 18:06.22 | mth | the implementation does exist in 3.5, in any case |
| 18:08.39 | larsc | at some point we should switch our jz_gpio_set_function over to pinctrl |
| 18:28.13 | mth | larsc: what is the practical difference between SND_SOC_DAPM_HP and SND_SOC_DAPM_LINE? |
| 18:28.25 | *** join/#qi-hardware heberth (~heberth@190.255.9.86) |
| 18:28.32 | mth | I have a single port here that's used for both headphones and TV-out, so I'm not sure what to label it |
| 18:30.45 | larsc | in practice there is not really a difference I think |
| 18:43.44 | *** join/#qi-hardware jekhor (~jek@leased-line-46-53-195-83.telecom.by) |
| 19:21.47 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 20:23.32 | *** join/#qi-hardware kyak (~kyak@95-28-122-139.broadband.corbina.ru) |
| 20:23.33 | *** join/#qi-hardware kyak (~kyak@unaffiliated/kyak) |
| 20:24.17 | *** join/#qi-hardware guanucoluis (~luis@Host98-111.epectelco.com.ar) |
| 20:35.17 | *** join/#qi-hardware porchao (~hato@eatkyo312063.adsl.ppp.infoweb.ne.jp) |
| 20:36.07 | *** join/#qi-hardware guanucoluis (~luis@2001:470:e450:0:225:56ff:fea1:2064) |
| 20:50.37 | *** join/#qi-hardware compcube (~compcube@c-76-112-242-32.hsd1.mi.comcast.net) |
| 20:50.38 | *** join/#qi-hardware compcube (~compcube@pdpc/supporter/student/compcube) |
| 21:23.20 | *** join/#qi-hardware heberth (~heberth@190.6.162.167) |
| 21:59.13 | *** join/#qi-hardware AwAyla (~paul@pc-144-230-164-190.cm.vtr.net) |
| 22:07.35 | *** join/#qi-hardware Hoolxi (~Openfree@183.195.224.101) |
| 22:39.18 | *** join/#qi-hardware zumbi (~zumbi@77.224.206.23) |
| 22:52.17 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 22:54.53 | *** join/#qi-hardware Ayla (~paul@pc-144-230-164-190.cm.vtr.net) |