* RE: Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b d_in fo structure in the kernel booting code
@ 2005-01-18 19:08 Povolotsky, Alexander
2005-01-18 20:29 ` John W. Linville
0 siblings, 1 reply; 3+ messages in thread
From: Povolotsky, Alexander @ 2005-01-18 19:08 UTC (permalink / raw)
To: 'John W. Linville'
Cc: 'Steven Blakeslee',
'linuxppc-embedded@ozlabs.org'
My board is using:
bd->bi_intfreq = 50000000;
bd->bi_busfreq = 50000000;
While RPX-Lite is using
bd->bi_intfreq = 48000000;
bd->bi_busfreq = 48000000;
Is this what makes RPX-Lite work and my (MPC 880) not ?
-----Original Message-----
From: Povolotsky, Alexander
Sent: Tuesday, January 18, 2005 1:53 PM
To: 'John W. Linville'
Cc: 'Mark Chambers'; 'linuxppc-embedded@ozlabs.org'; 'Tom Rini'; 'Steven
Blakeslee'
Subject: RE: Linux 2.6-10.rc3 8xx: debugging (over-writing) content of b
d_in fo structure in the kernel booting code
The "one, I am using" from my previous e-mail relates to 2.6.10-rc3
My processor is MPC880.
-----Original Message-----
From: Povolotsky, Alexander
Sent: Tuesday, January 18, 2005 1:19 PM
To: 'John W. Linville'
Cc: 'Mark Chambers'; 'linuxppc-embedded@ozlabs.org'; 'Tom Rini'; 'Steven
Blakeslee'
Subject: RE: Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b
d_in fo structure in the kernel booting code
>Aren't there still generic problems w/ 8xx and 2.6.x?
Allegedly - yes (with memory initialization) but ...
both Tom Rini and Steve Blakeslee were able to boot their
RPXLite Variant of 8xx on 2.6.10-rc3 (the one I am using)
-----Original Message-----
From: John W. Linville [mailto:linville@tuxdriver.com]
Sent: Tuesday, January 18, 2005 1:11 PM
To: Povolotsky, Alexander
Cc: 'Mark Chambers'; 'linuxppc-embedded@ozlabs.org'
Subject: Re: Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b
d_in fo structure in the kernel booting code
On Tue, Jan 18, 2005 at 10:45:53AM -0500, Povolotsky, Alexander wrote:
> Forgot to mention - this board boots (and works) well with Linux 2.4.26
Aren't there still generic problems w/ 8xx and 2.6.x?
--
John W. Linville
linville@tuxdriver.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b d_in fo structure in the kernel booting code
2005-01-18 19:08 Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b d_in fo structure in the kernel booting code Povolotsky, Alexander
@ 2005-01-18 20:29 ` John W. Linville
0 siblings, 0 replies; 3+ messages in thread
From: John W. Linville @ 2005-01-18 20:29 UTC (permalink / raw)
To: Povolotsky, Alexander
Cc: 'Steven Blakeslee',
'linuxppc-embedded@ozlabs.org'
On Tue, Jan 18, 2005 at 02:08:19PM -0500, Povolotsky, Alexander wrote:
> My board is using:
>
> bd->bi_intfreq = 50000000;
> bd->bi_busfreq = 50000000;
>
> While RPX-Lite is using
>
> bd->bi_intfreq = 48000000;
> bd->bi_busfreq = 48000000;
>
> Is this what makes RPX-Lite work and my (MPC 880) not ?
That, of course, depends on which value is correct for your
board... :-)
When I mentioned in one of our (possibly off-line) exchanges that
_slightly_ incorrect clock speeds might explain how you get a few good
characters from the serial port before you get all that garbage, this
is the kind of descrepancy I was suggesting. There may be enough
"slop" in the timings of the relatively slow serial port to make
48MHz and 50MHz "close enough" for a few characters.
So, what is the correct number for your board? Do you know how to
identify an oscillator? They have a bit of a 'tin can' look to them.
Find the one closest to the CPU on the board, and see what number is
on it.
John
--
John W. Linville
linville@tuxdriver.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b d_in fo structure in the kernel booting code
@ 2005-01-18 20:45 Povolotsky, Alexander
0 siblings, 0 replies; 3+ messages in thread
From: Povolotsky, Alexander @ 2005-01-18 20:45 UTC (permalink / raw)
To: 'John W. Linville'
Cc: 'Steven Blakeslee',
'linuxppc-embedded@ozlabs.org'
On my board the oscillator is marked 50.000 and the 50000000 setting works
on my board with Linux 2.4 ...
but I meant to ask in my question: whether (may be) the current 8xx vs 2.6
kernel memory initialization problems
only showing themself at 50Mhz and not at 48Mhz (I am trying to find
explanation why 2.6 works on RPX-Lite -
per Tom and Steve).
-----Original Message-----
From: John W. Linville [mailto:linville@tuxdriver.com]
Sent: Tuesday, January 18, 2005 3:29 PM
To: Povolotsky, Alexander
Cc: 'Mark Chambers'; 'linuxppc-embedded@ozlabs.org'; 'Tom Rini'; 'Steven
Blakeslee'
Subject: Re: Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b
d_in fo structure in the kernel booting code
On Tue, Jan 18, 2005 at 02:08:19PM -0500, Povolotsky, Alexander wrote:
> My board is using:
>
> bd->bi_intfreq = 50000000;
> bd->bi_busfreq = 50000000;
>
> While RPX-Lite is using
>
> bd->bi_intfreq = 48000000;
> bd->bi_busfreq = 48000000;
>
> Is this what makes RPX-Lite work and my (MPC 880) not ?
That, of course, depends on which value is correct for your
board... :-)
When I mentioned in one of our (possibly off-line) exchanges that
_slightly_ incorrect clock speeds might explain how you get a few good
characters from the serial port before you get all that garbage, this
is the kind of descrepancy I was suggesting. There may be enough
"slop" in the timings of the relatively slow serial port to make
48MHz and 50MHz "close enough" for a few characters.
So, what is the correct number for your board? Do you know how to
identify an oscillator? They have a bit of a 'tin can' look to them.
Find the one closest to the CPU on the board, and see what number is
on it.
John
--
John W. Linville
linville@tuxdriver.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-01-18 20:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-01-18 19:08 Linux 2.6.10-rc3 8xx: debugging (over-writing) content of b d_in fo structure in the kernel booting code Povolotsky, Alexander
2005-01-18 20:29 ` John W. Linville
-- strict thread matches above, loose matches on Subject: below --
2005-01-18 20:45 Povolotsky, Alexander
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).