... > > > I don't quite understand why you want to have this configurable. I mean > > > this is a single board only, why not simply run it with the maximum > > > allowed frequency? Or does this board come with multiple SoCs for which > > > different maximum values exist? > > > > Yes. There are 2 versions of the chip. One with a maximum operating > > frequency of 74 MHz, second with 90 MHz. The only difference is on the CPU label. > > Which version is used, it is impossible to know in runtime. > > You can simply reject this patch [3/9], all other should not depend on this one. > > Later I'll try to make another different version. > > Ok, thanks for explaining. It's really discouraged to put such things in > Kconfig, but in this case it seems acceptable: There's no way to detect > it during runtime *and* it varies across the same board type. So I > applied this series. > > One option out of this might be that you could always startup with 74MHz > and add a command to switch to 90MHz. You could put this into the > environment on boards that you know work with 90MHz. Aynway, I don't > want to force you to do this on an Architecture you're probably > currently the only user of. OK. Thanks. --- _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
