All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Brower <ebrower@gmail.com>
To: sparclinux@vger.kernel.org
Subject: Re: ebus & ioremap?
Date: Fri, 11 Mar 2005 18:47:10 +0000	[thread overview]
Message-ID: <ec7cefb05031110473741aae6@mail.gmail.com> (raw)
In-Reply-To: <Pine.SOC.4.61.0503101440500.12047@math.ut.ee>

From asm/io.h:

/* On sparc64 we have the whole physical IO address space accessible
 * using physically addressed loads and stores, so this does nothing.
 */
static inline void __iomem *ioremap(unsigned long offset, unsigned long size)
{
    return (void __iomem *)offset;
}

It is nice to use ioremap to remain idiomatic with other
architectures, though, esp. in drivers and the like.

E



On Thu, 10 Mar 2005 14:42:56 +0200 (EET), Meelis Roos <mroos@linux.ee> wrote:
> While trying to see if I can cleanly fix the iomem warnings for sparc
> floppy, I came to stop ath this code at asm/floppy.5:653
> 
>                  /* XXX ioremap */
>                  sun_pci_fd_ebus_dma.regs = edev->resource[1].start;
> 
> I can understand why someone did put a XXX there but why does it work
> this way?
> 
> --
> Meelis Roos (mroos@linux.ee)
> -
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
E

      parent reply	other threads:[~2005-03-11 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 12:42 ebus & ioremap? Meelis Roos
2005-03-10 19:40 ` David S. Miller
2005-03-11 18:47 ` Eric Brower [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=ec7cefb05031110473741aae6@mail.gmail.com \
    --to=ebrower@gmail.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.