14:40 <mth> larsc: the frequencies of CCLK, HCLK, MCLK and PCLK are dependent

14:41 <mth> should clock.c contain that knowledge?

14:41 <mth> or should clock.c stay close to the hardware and should the caller deal with the interdependencies?

14:42 <mth> I'm leaning towards the latter, because otherwise the scope of clock.c will become bigger and bigger

14:43 <larsc> me too

14:44 <mth> in that case, maybe moving jz_clk_main_divs to clock.h is better than making a function that enumerates possible frequencies

14:44 <mth> since the dividers that can be used for one clock depend on the divider selected for another clock

14:50 <mth> hmm, things are a lot simpler when just duplicating that info

15:43 <sid_on> is it purpose that icon-naming-utils and mutt is in default config for solving compile failtures? they are in default

16:30 <lekernel> how do you configure the a wiki license in mediawiki?

16:31 <bartbes> edit the php scripts :P

16:31 <lekernel> which one?

16:31 <bartbes> I was joking

16:31 <lekernel> ah

16:31 <lekernel> localsettings.php

16:32 <lekernel> grep rules

16:32 <bartbes> I have only *used* mediawiki

16:32 <bartbes> so I was right after all?

16:33 <lekernel> ha, yes

16:33 <lekernel> but a lot of stuff in MW is done by editing various php files

16:33 <lekernel> not very user friendly

16:34 <bartbes> very user-friendly

16:34 <bartbes> just not hoster-friendly :P

16:34 <lekernel> I damn hate sysadmin and webadmin in particular

16:34 <lekernel> I prefer pushbutton stuff like wordpress