Hi Jim,
I'm fairly certain that all the problems arise due to the fact that
the address of the clock registers on your machine is calculated
incorrectly for some reason in 2.6.18, but correctly in 2.6.16. If we
can confirm it, that would be a good starting point in understanding
of what went
On 14/10/2006, at 5:29 PM, Jurij Smakov wrote:
2.6.18, so we could compare. For 2.6.18 you could insert a line like
prom_printf(mstk48t59_regs=%p mstk48t02_regs=%p regs=%p\n,
mstk48t59_regs, mstk48t02_regs, regs);
around line 808 in time.c (right after these variables have been set).
The
On 13/10/2006, at 3:32 PM, Jurij Smakov wrote:
Thanks. One more thing: at boot time a line like this is displayed:
/[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:
Clock regs at 01fff100
Can you tell me (and send to the bug too), how this line looks
On Oct 13, 2006, at 5:45 AM, Jurij Smakov wrote:
On Sun, Oct 08, 2006 at 12:56:47PM +1000, Jim Watson wrote:
Hi,
I just installed linux-image-2.6.18-1-sparc64 which I think is the
latest available on debian/unstable.
But booting linux-image-2.6.18-1-sparc64 on sunblade100 fails:
Booting
Please find it attached.
Il giorno 13/ott/06, alle ore 05:45, Jurij Smakov ha scritto:
Can you please send the output of the 'prtconf -p -v' command to the
bug 392078?
--
Luigi Gangitano -- [EMAIL PROTECTED] -- [EMAIL PROTECTED]
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618
5 matches
Mail list logo
