Though I'd like to move to a uboot fdt, I can't afford to port it yet,
maybe in January. But until then ...
It appears that a simple change in U-boot constant,
#define CONFIG_8260_CLKIN6600/* in Hz */
to
#define CONFIG_8260_CLKIN1 /* in Hz */
has fixed
My uboot is new-ish, but I don't have the fdt commands? U-Boot 1.3.0
g992742a5-dirty
u-boot:clock configuration
===
MPC8248 Clock Configuration
- Bus-to-Core Mult 3.5x, VCO Div 2, 60x Bus Freq 30-85 , Core Freq 100-300
- dfbrg 1, corecnf 0x1e, busdf 3, cpmdf 1, plldf 0,
On Wed, 28 Nov 2007 21:06:36 -0700
Alan Bennett wrote:
> It comes from uboot. Can you point me in the right direction to make
> sure its right?
>PowerPC,[EMAIL PROTECTED] {
>device_type = "cpu";
>reg = <0>;
>d
It comes from uboot. Can you point me in the right direction to make
sure its right?
PowerPC,[EMAIL PROTECTED] {
device_type = "cpu";
reg = <0>;
d-cache-line-size = ;
i-cache-line-size = ;
Alan Bennett wrote:
> I've got a routine that needs to delay for X microseconds, this is a
> must. The command after schedule_timeout must has to wait for the HW
> to complete a task that takes X microseconds.
>
> I would think that one way to do this is with a simple
> schedule_timeout. But in
I've got a routine that needs to delay for X microseconds, this is a
must. The command after schedule_timeout must has to wait for the HW
to complete a task that takes X microseconds.
I would think that one way to do this is with a simple
schedule_timeout. But in the example below, the time that
