All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Breuer <breuerr@mc.net>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32 2.6 work
Date: Mon, 16 May 2005 15:37:12 +0000	[thread overview]
Message-ID: <4288BE28.3050801@mc.net> (raw)
In-Reply-To: <4285EE7A.7090200@bellsouth.net>

Jurij Smakov wrote:
> 
> Well, UP in Debian is pretty solid on sparc32. I happen to own one of 
> the machines with Hypersparc CPU and UP 2.6.x and Debian's pre-built 
> kernels are stable enough to build other packages and kernels on it. The 
> only sparc32 patch we are applying against 2.6.11 is the following:
> 
> --- kernel-source-2.6.11-2.6.11-orig//arch/sparc/mm/srmmu.c    
> 2005-03-02 08:38:10.000000000 +0100
> +++ kernel-source-2.6.11-2.6.11/arch/sparc/mm/srmmu.c    2005-03-05 
> 10:39:38.677679448 +0100
> @@ -1464,7 +1464,6 @@
>  static void __init init_hypersparc(void)
>  {
>          srmmu_name = "ROSS HyperSparc";
> -    srmmu_modtype = HyperSparc;
> 
>          init_vac_layout();
> 
> Without it the kernel fails to mount initrd on boot due to unknown 
> reason. This change was discovered after numerous experiments :-). The 
> only other quirk I know (which can be related) is that Debian's 2.6.8 
> netboot images do not boot Hypersparc machines (others seem to be fine), 
> again due to the trouble with initrd.
> 

Reverting that change should not be needed for 2.6.11 (but it did cause 
other problems with 2.6.10).  Mounting an initrd under 2.6.11 works for 
me on my hypersparc ss20.  I think there was a memcpy fix for the initrd 
failures.  Anyway, if there is still a problem that requires the change, 
I'm willing to help track it down.

Bob

  parent reply	other threads:[~2005-05-16 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14 12:26 sparc32 2.6 work Heitzso
2005-05-14 17:43 ` Jurij Smakov
2005-05-16 15:37 ` Bob Breuer [this message]
2005-05-17  6:35 ` Jurij Smakov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4288BE28.3050801@mc.net \
    --to=breuerr@mc.net \
    --cc=sparclinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.