Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Dec 1997 22:58:35 -0800
From:      Amancio Hasty <hasty@rah.star-gate.com>
To:        wakkym@juno.com (Lee Cremeans)
Cc:        hackers@FreeBSD.ORG
Subject:   Re: Beginning SPARC port 
Message-ID:  <199712140658.WAA09916@rah.star-gate.com>
In-Reply-To: Your message of "Sun, 14 Dec 1997 01:31:56 EST." <19971214.012956.5303.3.wakkym@juno.com> 

next in thread | previous in thread | raw e-mail | index | archive | help

Which is fine for most PCI devices that I have at least programmed
the registers are i/o mapped registers.
pci_conf_read/pci_conf_write is  a high level interface to the 
PCI registers now if you are looking for a higher abstraction 
please elaborate.

	Amancio

> 
> On Sat, 13 Dec 1997 21:51:10 -0800 Amancio Hasty
> <hasty@rah.star-gate.com> writes:
> >The functions is already there:
> >
> >        old_irq = pci_conf_read(tag, PCI_INTERRUPT_REG);
> >        pci_conf_write(tag, PCI_INTERRUPT_REG, BROOKTREE_IRQ);
> >
> >And usually PCI devices have i/o mapped registers.
> 
> On the i386, this is true, but (as has been said before, but I guess not
> as clearly) there are architectures out there that don't have an
> Intel-style I/O vs. memory addressing distinction (the 680x0s are like
> this, and I think the SPARC and PowerPC are also; not sure about Alpha),
> so they map all the device registers into physical memory space. 
> 





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712140658.WAA09916>