All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: [2/3] sun4d updates (guys, please send me real descriptions!)
Date: Tue, 21 Dec 2004 04:39:46 +0000	[thread overview]
Message-ID: <20041221043946.GB771@holomorphy.com> (raw)
In-Reply-To: <20041221042836.GZ771@holomorphy.com>

Dave, I got the following hunk from Chris Newport and Thomas Bogendoerfer.
I'm not sure of your opinion regarding sun4d impact on generic sbus
driver code. I can drop this hunk (vs. 2.6.10-rc3) if it's not acceptable.

-- wli

On Mon, Dec 20, 2004 at 08:28:36PM -0800, William Lee Irwin III wrote:
>   * prom_sbus_ranges_init(), with all sun4d stuff cut away.
>   * Ask DaveM what is going on here, how is sun4d supposed to work... XXX
>   */
> +/* added back sun4d patch from Thomas Bogendoerfer - should be OK (crn) */
> +
>  static void __init sbus_bus_ranges_init(int parent_node, struct sbus_bus *sbus)
>  {
>  	int len;
> @@ -229,6 +231,18 @@
>  		return;
>  	}
>  	sbus->num_sbus_ranges = len / sizeof(struct linux_prom_ranges);
> +	if (sparc_cpu_model = sun4d) {
> +		struct linux_prom_ranges iounit_ranges[PROMREG_MAX];
> +		int num_iounit_ranges;
> +
> +	len = prom_getproperty(parent_node, "ranges",
> +				(char *) iounit_ranges,
> +				sizeof (iounit_ranges));
> +		if (len != -1) {
> +			num_iounit_ranges = (len/sizeof(struct linux_prom_ranges));
> +			prom_adjust_ranges (sbus->sbus_ranges, sbus->num_sbus_ranges, iounit_ranges, num_iounit_ranges);
> +		}
> +	}

  reply	other threads:[~2004-12-21  4:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  4:28 [2/3] sun4d updates (guys, please send me real descriptions!) William Lee Irwin III
2004-12-21  4:39 ` William Lee Irwin III [this message]
2004-12-21  6:09 ` David S. Miller
2004-12-21  6:36 ` William Lee Irwin III
2004-12-21  8:57 ` Jan-Benedict Glaw
2004-12-21  8:59 ` William Lee Irwin III

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=20041221043946.GB771@holomorphy.com \
    --to=wli@holomorphy.com \
    --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.