From: Benjamin Herrenschmidt <bh40@calva.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
linuxppc-dev@lists.linuxppc.org, linux-fbdev@vuser.vu.union.edu
Subject: Re: [linux-fbdev] Retrace
Date: Tue, 8 Feb 2000 22:30:45 +0100 [thread overview]
Message-ID: <20000208223045.004499@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10002081749540.27293-100000@callisto.of.borg>
On Tue, Feb 8, 2000, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>The BAR values in PCI config space may be the same, but the BAR values in
>struct pci_dev can be made different by the machine-specific fixup code.
This would work as long as no one reads the BAR directly. I know no-one
should do it, but I've seen some time ago (can't remember where) some
drivers reading BARs directly. Also, I don't know for the X server.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-08 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10002071812050.1142-100000@cassiopeia.home>
2000-02-07 19:02 ` [linux-fbdev] Retrace 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 [this message]
2000-02-08 21:39 ` Geert Uytterhoeven
2000-02-08 10:02 Geert Uytterhoeven
2000-02-09 2:45 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2000-02-08 16:00 Andy
2000-02-08 21:29 Benjamin Herrenschmidt
2000-02-09 9:57 ` Gabriel Paubert
2000-02-09 13:45 Patrick Lerda
2000-02-09 14:09 ` Gabriel Paubert
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=20000208223045.004499@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).