Messages in this thread | | | Subject | Re: [RFC] PCI bridge driver rewrite | From | Adam Belay <> | Date | Mon, 28 Feb 2005 19:13:17 -0500 |
| |
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?
I think a "struct isa_device" would be be useful. Would a pointer to the "struct pci_bus" do the trick?
> > > Also is the legacy IO space mapped to IO Memory on the other side of the > > bridge? > > How do you mean? Legacy I/O port accesses just become strongly ordered memory > transactions, afaik, and legacy memory accesses are dealt with the same way. > > Jesse
I was just wondering if we have to reserve a memory range for this?
Thanks, Adam
- 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/
| |