From: Benjamin Herrenschmidt <bh40@calva•net>
To: Kostas Gewrgiou <gewrgiou@imbc•gr>,
Linux/PowerPC Devel List <linuxppc-dev@lists•linuxppc.org>
Subject: Re: dual head r128
Date: Thu, 12 Oct 2000 17:13:52 +0200 [thread overview]
Message-ID: <19340906084536.29942@192.168.1.2> (raw)
In-Reply-To: <Pine.LNX.4.21.0010121542340.18328-100000@idd-01.imbc.gr>
>
>Since the card is a x86 one int10 is needed to initialize it, don't expect
>the int10 code to work under linux/ppc though, it needs ISA IO and memory
>access which don't work.
>I have code to fix PIO for machines with only one iobase, but it
>doesn't work with Uni-N machines (i have no idea how to handle code like
>inb(0x3C3) in this machines and until someone figures out how to handle it
>don't expect int10 to work....)
I'm updating the PCI code in linuxppc_2_5 tree (which is more or less
meant to be merged in _2_3 soon). I'm adding a couple of cases to the
sys_pciconfig_iobase syscall to return the ISA mem and IO bases (if they
exist).
On the kernel side, one of the PCI IO busses will be mapped to ISA. What
I'll do is basically to change the kernel inb/outb functions to do
something like
if (addr < 64k)
do_io(isa_io_base + addr)
else
do_io(addr)
This way, PCI IOs will be able to use real physical addresses that will
have been put by the fixup code in the IO resources, while legacy IOs
will tap the IO bus that we have decided is the "legacy" bus.
It's a bit ugly, but AFAIK, we don't have any arch where IOs are memory
mapped below 64K physical. I would have prefered Paul's mecanism for
appending the IO spaces, but...
Unfortunately, there's no simple way to allow two busses to have the
legacy IOs. That means on UniN machines that they'll be available either
on the AGP bus, or the external PCI bus, but not both.
What you might do is to consider the ISA io base to be the IO base of the
bus that holds the card for which you are trying to run the BIOS. (By
using the syscall to retreive this IO base for the VGA card) instead of
asking the kernel for the "legacy" IO base.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-12 15:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-11 18:17 dual head r128 Josh Huber
2000-10-11 18:43 ` Michel Dänzer
2000-10-11 18:52 ` Josh Huber
2000-10-11 19:04 ` Tom Rini
2000-10-11 19:09 ` Michel Dänzer
2000-10-11 19:26 ` Josh Huber
2000-10-11 22:48 ` Michel Dänzer
2000-10-13 17:16 ` Josh Huber
2000-10-12 13:09 ` Kostas Gewrgiou
2000-10-12 15:13 ` Benjamin Herrenschmidt [this message]
2000-10-12 15:49 ` Gabriel Paubert
2000-10-12 16:40 ` David Edelsohn
2000-10-17 0:12 ` Paul Mackerras
2000-10-17 5:56 ` Michel Lanners
2000-10-17 10:41 ` Benjamin Herrenschmidt
2000-10-17 13:45 ` Geert Uytterhoeven
2000-10-17 17:17 ` Benjamin Herrenschmidt
2000-10-12 16:44 ` Kostas Gewrgiou
2000-10-11 21:01 ` Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2000-10-12 13:41 Hendricks, Kevin
2000-10-12 14:10 ` Kostas Gewrgiou
2000-10-12 14:30 Hendricks, Kevin
2000-10-12 16:11 ` Kostas Gewrgiou
2000-10-12 17:22 ` Michel Dänzer
2000-10-12 17:44 ` Kostas Gewrgiou
2000-10-12 21:25 ` Michel Dänzer
2000-10-13 15:26 ` Kostas Gewrgiou
2000-10-13 16:21 ` Geert Uytterhoeven
2000-10-12 16:25 Hendricks, Kevin
[not found] <200010121619.TAA27476@ns0.imbc.gr>
2000-10-12 17:08 ` Kostas Gewrgiou
[not found] <19340906102959.14429@192.168.1.2>
2000-10-12 17:57 ` Gabriel Paubert
[not found] <Pine.LNX.4.10.10010132302530.381-100000@cassiopeia.home>
2000-10-13 21:36 ` Benjamin Herrenschmidt
2000-10-13 21:47 ` Michel Lanners
2000-10-14 10:13 ` Benjamin Herrenschmidt
2000-10-14 10:21 ` 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=19340906084536.29942@192.168.1.2 \
--to=bh40@calva$(echo .)net \
--cc=gewrgiou@imbc$(echo .)gr \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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