Ultralinux archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daz <daz@undertaker.homeip.net>
To: ultralinux@vger.kernel.org
Subject: Re: Ultra4000 and kernel 2.4.0
Date: Thu, 25 Jan 2001 17:16:59 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-98044261124866@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-98043007617176@msgid-missing>

That worked!!  muchas gracias!!   Now I just have to go back to fixing
that dang soc problem.....grumble...grumble...



David
On Thu, 25 Jan 2001, David
S. Miller wrote:

> 
> Please try this patch, thanks:
> 
> --- drivers/sbus/sbus.c.~1~	Tue Nov 28 08:33:08 2000
> +++ drivers/sbus/sbus.c	Thu Jan 25 07:34:01 2001
> @@ -238,10 +238,14 @@
>  					break;
>  			}
>  			if (rngnum = num_ranges) {
> -				prom_printf("sbus_apply_ranges: Cannot find matching "
> -					    "range nregs[%d] nranges[%d].\n",
> -					    num_regs, num_ranges);
> -				prom_halt();
> +				/* We used to flag this as an error.  Actually
> +				 * some devices do not report the regs as we expect.
> +				 * For example, see SUNW,pln device.  In that case
> +				 * the reg property is in a format internal to that
> +				 * node, ie. it is not in the SBUS register space
> +				 * per se. -DaveM
> +				 */
> +				return;
>  			}
>  			regs[regnum].which_io = ranges[rngnum].ot_parent_space;
>  			regs[regnum].phys_addr += ranges[rngnum].ot_parent_base;
> 

-- 
"I find your lack of faith disturbing."
--Darth Vader

-
To unsubscribe from this list: send the line "unsubscribe ultralinux" in
the body of a message to majordomo@vger.kernel.org

      parent reply	other threads:[~2001-01-25 17:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25  7:33 Ultra4000 and kernel 2.4.0 Daz
2001-01-25 13:52 ` David S. Miller
2001-01-25 14:56 ` Daz
2001-01-25 15:35 ` David S. Miller
2001-01-25 17:10 ` David S. Miller
2001-01-25 17:16 ` Daz [this message]

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=marc-linux-ultrasparc-98044261124866@msgid-missing \
    --to=daz@undertaker.homeip.net \
    --cc=ultralinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox