From linux-kernel Tue Mar 01 00:34:04 2005 From: Jesse Barnes Date: Tue, 01 Mar 2005 00:34:04 +0000 To: linux-kernel Subject: Re: [RFC] PCI bridge driver rewrite Message-Id: <200502281634.05197.jbarnes () sgi ! com> X-MARC-Message: https://marc.info/?l=linux-kernel&m=110963800018275 On Monday, February 28, 2005 4:13 pm, Adam Belay wrote: > On Mon, 2005-02-28 at 15:38 -0800, Jesse Barnes wrote: > > On Monday, February 28, 2005 3:27 pm, Adam Belay wrote: > > > How can we specify which bus to target? > > > > Maybe we could have a list of legacy (ISA?) devices for drivers like > > vgacon to attach to? The bus info could be stuffed into the legacy > > device structure itself so that the platform code would know what to do. > > Are these devices actually legacy, or PCI with compatibility interfaces? So far I've only tried VGA cards, like radeons and r128s. > I think a "struct isa_device" would be be useful. Would a pointer to > the "struct pci_bus" do the trick? Yeah, that would work for me. > I was just wondering if we have to reserve a memory range for this? Sure, each bus can have that address range reserved. The ia64 specific HAVE_PCI_LEGACY code (in arch/ia64/sn/pci/pci_dma.c I think) might illuminate things a bit. Basically, each bus has legacy base addresses, we could reserve 64k for port space and 1M for memory. Jesse - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/