All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Gabriel Paubert <paubert@iram.es>,
	linuxppc-dev@lists.linuxppc.org, linux-fbdev@vuser.vu.union.edu
Subject: Re: [linux-fbdev] Retrace
Date: Tue, 8 Feb 2000 22:29:16 +0100	[thread overview]
Message-ID: <20000208222916.011600@mailhost.mipsys.com> (raw)


On Tue, Feb 8, 2000, Gabriel Paubert <paubert@iram.es> wrote:

>	deviobase = ioport_ptr(dev->resource[0]);
>
>	data = inl(deviobase+register_offset);
>
>and for an MMIO mapped area:
>
>	mmioptr = ioremap(ioremap_ptr(dev->resource[1]));
>
>	data = readl(mmioptr+register_offset);

Is it possible to "walk up" the resource tree from dev->resource[0] ? I
mean, the ioport_ptr function, to work on those weird Apple bridges, need
to go thru a special routine that looks up the device in OF device tree
to find out on which sub-bridge it is.
In order to do that, it needs the pci dev_fn. Can this be retreived from
dev->resource[0] ?

Also, this doesn't solve the userland problem.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-02-08 21:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-08 21:29 Benjamin Herrenschmidt [this message]
2000-02-09  9:57 ` [linux-fbdev] Retrace Gabriel Paubert
  -- strict thread matches above, loose matches on Subject: below --
2000-02-09 13:45 Patrick Lerda
2000-02-09 14:09 ` Gabriel Paubert
2000-02-08 16:00 Andy
2000-02-08 10:02 Geert Uytterhoeven
2000-02-09  2:45 ` Paul Mackerras
     [not found] <Pine.LNX.4.10.10002071812050.1142-100000@cassiopeia.home>
2000-02-07 19:02 ` Benjamin Herrenschmidt
2000-02-08  9:29   ` Gabriel Paubert
2000-02-08 14:56     ` Benjamin Herrenschmidt
2000-02-08 16:47       ` Gabriel Paubert
2000-02-08 16:51       ` Geert Uytterhoeven
2000-02-08 17:09         ` Gabriel Paubert
2000-02-08 21:30         ` Benjamin Herrenschmidt
2000-02-08 21:39           ` Geert Uytterhoeven

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=20000208222916.011600@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linux-fbdev@vuser.vu.union.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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.