All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: bh40@calva.net
Cc: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org
Subject: Re: Trying a Promise Ultra/66 on powerpc
Date: Mon, 9 Aug 1999 22:15:19 +0200 (CEST)	[thread overview]
Message-ID: <199908092015.WAA00324@piglet.cpu.lu> (raw)
In-Reply-To: <19990809085029.001336@smtp.calvacom.fr>


Hi gentlemen (any ladies around?),

On   9 Aug, this message from Benjamin Herrenschmidt echoed through cyberspace:
> On Mon, Aug 9, 1999, Paul Mackerras <paulus@cs.anu.edu.au> wrote:
>>Basically the problem is that the IDE driver assumes that you access
>>all IDE controllers via I/O ports.  When you have a controller that
>>has memory-mapped registers, there is a problem.  When you have a
>>system where one IDE controller has I/O ports and another has memory-
>>mapped registers, you have a bigger problem.  The current approach to
>>solving this problem is to map the addresses of the memory-mapped
>>registers into pseudo I/O port numbers (by subtracting _IO_BASE).  If
>>there is a better way, somebody let me know. :-)
> 
> Looks like the best way would be to store the port base or pointers to
> the in/out functions in the HWIF structure.

How about fixing this in the kernel's PCI bus structures, by adding any
required offsets in the pci_fixup() routines? This would make for clean
inb()/outb() definitions (no offset), and also accomodates multiple I/O
spaces behind more than one bridge. For instance, on the 7x00, both
bandit and chaos have I/O space; the one for the PCI cards, the other
for control (yes, control has an I/O port range! Not sure it serves,
though...).

Any fixed-offset approach would break with multiple I/O ranges.... Not
to mention the 9x00 machines (two separate host bridges, each three
slots), where you can't work around the problem by using hardcoded
addresses for the known motherboard chips.

I guess this approach could be made to work across the PPC
architecture, not only on the PMac, as the PPC in general lacks anything
special about I/O space... after all, those are just small memory
spaces ;-)

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.   ]]

  reply	other threads:[~1999-08-09 20:15 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 [this message]
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
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=199908092015.WAA00324@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=bh40@calva.net \
    --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 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.