ChanServ changed the topic of #linux-cros-arm to:
tobhe has joined #linux-cros-arm
hexdump0815 has joined #linux-cros-arm
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump01 has quit [Ping timeout: 480 seconds]
<dcz[m]> what's the problem with the clock driver?
<timon25h[m]> ellyq: weirdtreething I'm definitely curious about the above as well, also which chips are we talking about?
<ellyq> dcz[m]: it's annoying to write one without any documentation
<ellyq> timon25h[m]: MT8183, MT8186, MT8188, MT8192, MT8195 and whatever's coming out now (MT8196, MT8189 etc)
<timon25h[m]> you're expecting the driver to be mostly shared between them? (with typical register defines and minor if (mtxxxx) {a} else {b}, etc)
<weirdtreething> the way they are written is mostly the same as linux, but with a few slight changes which makes it tedious and annoying to convert from linux to u-boot
<ellyq> timon25h[m]: not at all
<ellyq> MT8188 for instance seems to have been designed by the same team that designed MT8195
<ellyq> s/MT8188/MT8186
<ellyq> it's a per-soc kind of deal
<timon25h[m]> ehh, things are never nice:|
weirdtreething has quit [Remote host closed the connection]
weirdtreething has joined #linux-cros-arm
weirdtreething has quit [Remote host closed the connection]
weirdtreething has joined #linux-cros-arm