In message [off-list ref] you wrote:
it was tracked down to a UPM/SDRAM timing problem. People keep talking
about running > 50 MHz bus on these newer parts, is there something
different about the memory controller that allows this and may cause
compatibility problems? I have (fortunately :-) not looked at this
level of detail in the newer parts.
There are no differences AFAIK. It's just a faster CPU that allows 66
or even 76 MHz with 1:1 CPU/bus clock mode.
We have a MPC823E system here that runs at 66 MHz, and I will have a
MPC855T at 66MHz in 18 hours from now. So far I didn't encounter any
problems - of course you have to adjust the UPM tables and what else
you need to initialize the memory controller.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The Wright Bothers weren't the first to fly. They were just the first
not to crash.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Wolfgang Denk wrote:
There are no differences AFAIK. It's just a faster CPU that allows 66
or even 76 MHz with 1:1 CPU/bus clock mode.
Interesting. Faster than 50 MHz cores used to require the 2:1 bus
clock division. I don't remember timing parameters that would
exceed 50 MHz. Yes, the part will let you do that, but I thought that
was outside of the part specification. I guess I'll have to take a look.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Dear, everyone!
I'm poring linux-2.4.18-pre7 (from penquinppc.org) on my customized board (with IBM 405GP)
My board has no keyboard, so I'm using serial console on UART0.
I ported ppcboot, and it works well.
When I ported linux on my board, there happened some problem.
After init forks sash (standalone shell as you know),
I can see the prompt of the sash but the character sent wasn't delivered to sash.
So what character I send to the sash. It never respond.
I watch for the serial source (driver/char/serial.c) and enabled DEBUG option and the character sent
was received by kernel.
I don't know why the characters are disappeared.
Anyone know the reason?
Please, help me.
==============================================
Just for fun...
- Linus Torvalds
==============================================
Kwansuk Kim
Engineer, NeoWave Inc.
Tel +82-31-380-4927 Fax +82-31-380-4747
E-mail: kskim@neowave.co.kr
==============================================
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Hi, Kim,Kwansuk!
It seams you have the same problem that I had just two weeks ago.
It is likely you have the serial port located below 0xc0000000.
If it is so, I suggest you to move the serial port above 0xc0000000.
If you want to know the reason, just find the mails, in this mailing list, titled "Re: execve system call question"
- Sangmoon Kim -
----- Original Message -----
From: "Kim, Kwansuk" <redacted>
To: <redacted>
Sent: Thursday, March 07, 2002 11:42 AM
Subject: serial console on 405GP
Dear, everyone!
I'm poring linux-2.4.18-pre7 (from penquinppc.org) on my customized board (with IBM 405GP)
My board has no keyboard, so I'm using serial console on UART0.
I ported ppcboot, and it works well.
When I ported linux on my board, there happened some problem.
After init forks sash (standalone shell as you know),
I can see the prompt of the sash but the character sent wasn't delivered to sash.
So what character I send to the sash. It never respond.
I watch for the serial source (driver/char/serial.c) and enabled DEBUG option and the character sent
was received by kernel.
I don't know why the characters are disappeared.
Anyone know the reason?
Please, help me.
==============================================
Just for fun...
- Linus Torvalds
==============================================
Kwansuk Kim
Engineer, NeoWave Inc.
Tel +82-31-380-4927 Fax +82-31-380-4747
E-mail: kskim@neowave.co.kr
==============================================
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/