Mikhail Zolotaryov wrote:
> Hi Mike,
>
> you wrote:
> "Row address bits : 13
> DDR0_02 = 0x020C0E01
> DDR0_42 = 0x0006"
>
> Register values above define that memory has 14 row address bits. The
> correct setting is (for CAS Latency = 3):
> DDR0_42 = 0x0106
>
> Best regards,
> Mikhail Zol
Valentine wrote:
> AFAIK, u-boot just writes pre-defined values to the memory controller
> registers. It doesn't do any chiptype/memsize detection. These values
> are set for Sequoia and may not suite your board. So you probably need
> to adjust the u-boot to make linux detect the memory size corre
(top-posting corrected)
Mikhail Zolotaryov wrote:
> Mike Nuss wrote:
>> There was a fix a while back called "Correct memory size calculation
>> for Denali based boards" that corrected the data width detection in
>> the 4xx bootwrapper.
>>
>> This seem
There was a fix a while back called "Correct memory size calculation for
Denali based boards" that corrected the data width detection in the 4xx
bootwrapper.
This seems to have had the unintended consequence of exposing another
bug in the same code. I have a board very similar to Sequoia, except
On Sep 25, 2007 1:18 PM, Mike Nuss <[EMAIL PROTECTED]> wrote:
> > > Is there a reason that booke_wdt.c does not specify a MODULE_LICENSE?
> > >> From the copyright notice at the top it appears to be GPL. As
> > >> written,
> > > it taints the kern
I'm writing a module for the Security/KASUMI function on the
PPC440EPx-S and PPC440GRx-S. This relies on checking the PVR value at
runtime, which is done early on in the boot process. What would be
the correct way to check which CPU is present during module
initialization?
Thanks,
Mike
__
> > Is there a reason that booke_wdt.c does not specify a MODULE_LICENSE?
> >> From the copyright notice at the top it appears to be GPL. As
> >> written,
> > it taints the kernel.
>
> Odd, no reason. I'll submit a patch for that.
>
> > Also, if I test out the driver by killing my process that's d
Hi,
I have a PPC440EPx and I am testing out the builtin watchdog. I have a
couple of questions:
Is there a reason that booke_wdt.c does not specify a MODULE_LICENSE?
>From the copyright notice at the top it appears to be GPL. As written,
it taints the kernel.
Also, if I test out the driver by ki
