crossdev has quit [Remote host closed the connection]
GenTooMan has quit [Ping timeout: 260 seconds]
crossdev has joined #riscv
heat_ is now known as _Heat
_Heat has quit [Read error: Connection reset by peer]
heat has joined #riscv
GenTooMan has joined #riscv
davidlt has quit [Ping timeout: 272 seconds]
hightower3 has joined #riscv
hightower4 has quit [Ping timeout: 260 seconds]
fuwei has quit [Ping timeout: 268 seconds]
fuwei has joined #riscv
BootLayer has quit [Quit: Leaving]
crossdev has quit [Remote host closed the connection]
Stat_headcrabed has joined #riscv
crossdev has joined #riscv
Stat_headcrabed has quit [Client Quit]
mlw has quit [Ping timeout: 272 seconds]
mlw has joined #riscv
heat_ has joined #riscv
heat has quit [Ping timeout: 264 seconds]
MaxGanzII has joined #riscv
heat_ has quit [Remote host closed the connection]
heat_ has joined #riscv
heat__ has joined #riscv
heat_ has quit [Read error: Connection reset by peer]
mlw has quit [Ping timeout: 268 seconds]
jmdaemon has joined #riscv
hightower3 has quit [Remote host closed the connection]
hightower3 has joined #riscv
hightower3 has quit [Remote host closed the connection]
hightower3 has joined #riscv
hightower3 has quit [Remote host closed the connection]
hightower3 has joined #riscv
hightower3 has quit [Remote host closed the connection]
hightower3 has joined #riscv
hightower3 has quit [Remote host closed the connection]
naoki has joined #riscv
[exa] has quit [Quit: WeeChat 4.1.2]
<la_mettrie>
JH7110's reset drivers perform timeout polling in order to prevent hanging when deasserting reset lines associated to gated clocks. no other reset driver mentions gated clocks. so is this some kind of hardware bug in JH7110 or what?
heat__ is now known as heat
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #riscv
jfsimon1981 has joined #riscv
vagrantc has joined #riscv
Narrat has quit [Quit: They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.]