All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
	Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [PATCH -queue v2] MIPS: Alchemy: use 36bit addresses for PCMCIA resources.
Date: Wed, 24 Feb 2010 12:39:44 +0100	[thread overview]
Message-ID: <20100224113943.GA14446@linux-mips.org> (raw)
In-Reply-To: <f861ec6f1002232357l112e2396qd063fd1c1bbdb46@mail.gmail.com>

On Wed, Feb 24, 2010 at 08:57:27AM +0100, Manuel Lauss wrote:

> On Wed, Feb 24, 2010 at 12:06 AM, Ralf Baechle <ralf@linux-mips.org> wrote:
> > On Tue, Feb 23, 2010 at 09:22:14PM +0100, Manuel Lauss wrote:
> >
> >> On Alchemy the PCMCIA area lies at the end of the chips 36bit system
> >> bus area.  Currently, addresses at the far end of the 32bit area
> >> are assumed to belong to the PCMCIA area and fixed up to the real
> >> 36bit address before being passed to ioremap().
> >>
> >> A previous commit enabled 64 bit physical size for the resource
> >> datatype on Alchemy and this allows to use the correct
> >> 36bit addresses when registering the PCMCIA sockets.
> >>
> >> This patch removes the 32-to-36bit address fixup and registers the
> >> Alchemy demoboard pcmcia socket with the correct 36bit physical
> >> addresses.
> >>
> >> Tested on DB1200, with a CF card (ide-cs driver) and a 3c589 pcmcia
> >> ethernet card.
> >>
> >> Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
> >
> > Thanks, queued for 2.6.34.
> 
> Please drop this one for now, I forgot to change the XXS1500 board
> and driver code.  I'll resend an updated version.

Done.

  Ralf

      reply	other threads:[~2010-02-24 11:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 20:22 [PATCH -queue v2] MIPS: Alchemy: use 36bit addresses for PCMCIA resources Manuel Lauss
2010-02-23 23:06 ` Ralf Baechle
2010-02-24  7:57   ` Manuel Lauss
2010-02-24  7:57     ` Manuel Lauss
2010-02-24 11:39     ` Ralf Baechle [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=20100224113943.GA14446@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=manuel.lauss@gmail.com \
    --cc=manuel.lauss@googlemail.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 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.