| 00:10.54 | *** join/#elinux lyakh_ (~lyakh@dslb-094-221-104-202.pools.arcor-ip.net) |
| 00:52.55 | *** join/#elinux fenrig (~fenrig@94-226-35-134.access.telenet.be) |
| 05:04.11 | *** join/#elinux restrator (~teonmea@pool-108-13-4-165.lsanca.fios.verizon.net) |
| 09:47.57 | *** join/#elinux lyakh (~lyakh@dslb-094-221-104-202.pools.arcor-ip.net) |
| 12:26.31 | *** join/#elinux espiral (maze@unaffiliated/espiral) |
| 13:18.18 | *** join/#elinux phantoxeD (destroy@a89-154-113-87.cpe.netcabo.pt) |
| 13:20.30 | *** join/#elinux okias (~okias@berger.cust.centro-net.cz) |
| 14:04.38 | *** join/#elinux jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 18:19.31 | okias | How it's possible is power button EBUSY (-16), when nothing use GPIO0 |
| 18:27.03 | *** join/#elinux dagle (~dagle@d83-183-100-86.cust.tele2.se) |
| 22:22.36 | *** join/#elinux okias (~okias@berger.cust.centro-net.cz) |
| 22:23.01 | okias | can I someway figure, what driver use gpio 0? |
| 22:23.11 | okias | not by looking at code (that doesnt help) |
| 22:41.03 | *** part/#elinux dagle (~dagle@d83-183-100-86.cust.tele2.se) |
| 22:51.05 | okias | for while, it looked like udc automatically grab gpio 0, but no... |