From: Michel Lanners <mlan@cpu.lu>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: Paul.Mackerras@cs.anu.edu.au, drow@false.org, mj@ucw.cz,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Trying a Promise Ultra/66 on powerpc
Date: Thu, 12 Aug 1999 19:30:24 +0200 (CEST) [thread overview]
Message-ID: <199908121730.TAA03489@piglet.cpu.lu> (raw)
In-Reply-To: <Pine.LNX.4.10.9908101455510.32043-100000@mercator.cs.kuleuven.ac.be>
On 10 Aug, this message from Geert Uytterhoeven echoed through cyberspace:
>> One way might be to adjust the base addresses in all the pci_dev
>> structs and then make sure all drivers use the address from the
>> pci_dev struct rather than reading config space themselves.
>
> Which will make our /proc/ioports look funny.
[mlan@piglet ~]$ cat /proc/ioports
f2000480-f2000487 : ide2
f2000488-f200048f : ide3
f2000490-f20004bf : PDC20262
I don't see why this would be funny.... except if you're used to the
PeeCee definition of IO ports being below 64 k ;-))
In any case, I still find it much better to adjust pci_dev, than to
play with offsets in inb()/outb().
But most important, adjusting struct pci_dev is the only way I see to
support IO space on more than one host bridge.
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-12 17:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19990727112137.A897@drow.res.cmu.edu>
[not found] ` <Pine.LNX.3.96.990727160229.10158B-100000@Astro.Dyer.Vanderbilt.Edu>
[not found] ` <19990727102627.A370@drow.res.cmu.edu>
[not found] ` <Pine.LNX.3.96.990727093644.6993B-100000@Astro.Dyer.Vanderbilt.Edu>
[not found] ` <19990727235430.D1046@albireo.ucw.cz>
1999-07-28 3:04 ` Trying a Promise Ultra/66 on powerpc Daniel Jacobowitz
1999-07-28 5:48 ` Michel Lanners
1999-07-28 7:17 ` Andre M. Hedrick
1999-08-08 19:54 ` Michel Lanners
1999-08-08 20:55 ` Tom Rini
1999-08-08 21:01 ` Michel Lanners
1999-08-09 3:22 ` Daniel Jacobowitz
1999-08-09 6:02 ` Paul Mackerras
1999-08-09 19:28 ` Tom Rini
1999-08-09 20:06 ` Michel Lanners
1999-08-09 3:26 ` Daniel Jacobowitz
1999-08-09 21:13 ` Michel Lanners
1999-08-12 20:05 ` Michel Lanners
1999-08-13 8:43 ` Geert Uytterhoeven
1999-08-09 5:13 ` Paul Mackerras
1999-08-09 5:18 ` David A. Gatwood
1999-08-09 5:33 ` Paul Mackerras
1999-08-09 5:38 ` David A. Gatwood
1999-08-09 6:50 ` Benjamin Herrenschmidt
1999-08-09 20:15 ` Michel Lanners
1999-08-09 20:23 ` Michel Lanners
1999-08-10 0:10 ` Paul Mackerras
1999-08-10 5:38 ` Michel Lanners
1999-08-10 8:45 ` Benjamin Herrenschmidt
1999-08-15 9:20 ` Martin Mares
1999-08-10 12:56 ` Geert Uytterhoeven
1999-08-12 17:30 ` Michel Lanners [this message]
1999-07-28 6:18 ` Tom Rini
1999-07-28 8:07 ` Martin Mares
1999-07-29 0:31 ` Andre M. Hedrick
1999-08-01 7:23 ` Michel Lanners
1999-07-29 9:16 Benjamin Herrenschmidt
1999-08-08 20:00 ` Michel Lanners
1999-08-08 20:52 ` Geert Uytterhoeven
1999-08-08 21:21 ` Michel Lanners
1999-08-08 21:27 ` Geert Uytterhoeven
1999-08-15 9:23 ` Martin Mares
-- strict thread matches above, loose matches on Subject: below --
1999-08-13 14:28 Justin McKillican
[not found] <199908092022.WAA00327@piglet.cpu.lu>
1999-08-15 9:39 ` Martin Mares
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=199908121730.TAA03489@piglet.cpu.lu \
--to=mlan@cpu.lu \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=drow@false.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mj@ucw.cz \
/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).