3 messages, 3 authors, 2001-12-18 · open the first message on its own page
From: Ralf Baechle <hidden>
Date: 2001-12-18 20:31:40
On Tue, Dec 18, 2001 at 11:16:24AM -0800, Jun Sun wrote:
I see. So isa_slot_offset is for isa_read/isa_write, although I still don't see what kind of drivers would use isa_read/isa_write.
Dumb answer - ISA drivers. Ralf
From: Jun Sun <hidden>
Date: 2001-12-18 20:37:01
Ralf Baechle wrote:
On Tue, Dec 18, 2001 at 11:16:24AM -0800, Jun Sun wrote:quoted
I see. So isa_slot_offset is for isa_read/isa_write, although I still don't see what kind of drivers would use isa_read/isa_write.Dumb answer - ISA drivers.
(Hmm, do you mean "dumb question"? :-0) I was thinking most ISA dirvers should simply use inb/outb to access ioports. Don't really any ISA devices have their own memory space. But, anyway, who can still remember those dark ages? Jun
From: Maciej W. Rozycki <hidden>
Date: 2001-12-18 21:31:04
On Tue, 18 Dec 2001, Jun Sun wrote:
I was thinking most ISA dirvers should simply use inb/outb to access ioports. Don't really any ISA devices have their own memory space. But, anyway, who can still remember those dark ages?
The so called "shared memory" (mapped in the ISA space; usually below 1MB) for frame storage existed on a few models of better ISA Ethernet boards. And, of course, VGA boards have memory mapped in the ISA space. Certain implementations occupy up to 4MB of ISA space when used in a SVGA mode. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +