Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: tiansm@lemote.com
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] fulong PCI updates
Date: Mon, 9 Jul 2007 14:41:04 +0100	[thread overview]
Message-ID: <20070709134104.GA14536@linux-mips.org> (raw)
In-Reply-To: <11838701474147-git-send-email-tiansm@lemote.com>

On Sun, Jul 08, 2007 at 12:49:07PM +0800, tiansm@lemote.com wrote:
> diff --git a/include/asm-mips/mips-boards/bonito64.h b/include/asm-mips/mips-boards/bonito64.h
> index cd71256..dc3fc32 100644
> --- a/include/asm-mips/mips-boards/bonito64.h
> +++ b/include/asm-mips/mips-boards/bonito64.h
> @@ -26,7 +26,12 @@
>  /* offsets from base register */
>  #define BONITO(x)	(x)
> 
> -#else /* !__ASSEMBLY__ */
> +#elif defined(CONFIG_LEMOTE_FULONG)
> +
> +#define BONITO(x) (*(volatile u32 *)((char *)CKSEG1ADDR(BONITO_REG_BASE) + (x)))
> +#define BONITO_IRQ_BASE   32
> +
> +#else
> 
>  /*
>   * Algorithmics Bonito64 system controller register base.

Okay, I've folded that into the existing Fulong patch in the -queue tree
and that'll also be the last thing I do on the -queue tree before merging
it into the main tree rsp. to Linus.

Note that the "mips-boards" in the filename was meant to mean
boards of MTI, so that mips-boards file would rather be moved around than
included via unobvious pathes that will eventually lead to breakage when
we change code for mips-boards/bonito64.h but I guess we can fix that
later.

  Ralf

  parent reply	other threads:[~2007-07-09 13:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08  4:49 [PATCH] fulong PCI updates tiansm
2007-07-08  4:50 ` Songmao Tian
2007-07-09 13:41 ` Ralf Baechle [this message]
2007-07-10  1:25   ` Songmao Tian
  -- strict thread matches above, loose matches on Subject: below --
2007-06-14  2:16 Songmao Tian
2007-06-14  2:21 ` Tian

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=20070709134104.GA14536@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=tiansm@lemote.com \
    /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