>> > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT,
>> > /*highaddr*/BUS_SPACE_MAXADDR,
>>
>> low and high address of the region that the DMA engine cannot access.
>
>Meaning e.g. the 16Mbyte barrier that ISA DMA has?
>For PCI this would be
>> > /*lowaddr*/BUS_SPACE_MAXADDR_32BIT,
>> > /*highaddr*/BUS_SPACE_MAXADDR,
>>
>> low and high address of the region that the DMA engine cannot access.
>
>Meaning e.g. the 16Mbyte barrier that ISA DMA has?
>For PCI this would b
As Justin T. Gibbs wrote ...
Excellent help, thanks. Some more questions inserted below.
> >shared memory stuff? I found some DMA stuff in ahc_pci.c:
> >
> > /* Allocate a dmatag for our SCB DMA maps */
> >/* XXX Should be a child of the PCI bus dma tag */
> >error = bus_dma_tag_c
As Justin T. Gibbs wrote ...
Excellent help, thanks. Some more questions inserted below.
> >shared memory stuff? I found some DMA stuff in ahc_pci.c:
> >
> > /* Allocate a dmatag for our SCB DMA maps */
> >/* XXX Should be a child of the PCI bus dma tag */
> >error = bus_dma_tag_
>> bus_dma related stuff is only required if the device has a DMA engine
>> you wish to use. To access the shared memory on the card (e.g. map
>
>Eh, sorry, I was confused. It has *both* shared memory and a DMA engine.
>
>> it into the kernel's virtual address space), you will need to use
>> the r
>> bus_dma related stuff is only required if the device has a DMA engine
>> you wish to use. To access the shared memory on the card (e.g. map
>
>Eh, sorry, I was confused. It has *both* shared memory and a DMA engine.
>
>> it into the kernel's virtual address space), you will need to use
>> the
As Justin T. Gibbs wrote ...
> In article <199907201904.vaa03...@yedi.iaf.nl> you wrote:
> > I'm currently trying to hack a driver together for a PCI card that uses
> > shared memory to communicate to the host.
> >
> > If I'm not completely offtrack I need to use (under newbus/-current)
> > bus_dm
In article <199907201904.vaa03...@yedi.iaf.nl> you wrote:
> I'm currently trying to hack a driver together for a PCI card that uses
> shared memory to communicate to the host.
>
> If I'm not completely offtrack I need to use (under newbus/-current)
> bus_dma_tag_create, bus_dma_alloc etc to get ac
As Justin T. Gibbs wrote ...
> In article <[EMAIL PROTECTED]> you wrote:
> > I'm currently trying to hack a driver together for a PCI card that uses
> > shared memory to communicate to the host.
> >
> > If I'm not completely offtrack I need to use (under newbus/-current)
> > bus_dma_tag_create, b
In article <[EMAIL PROTECTED]> you wrote:
> I'm currently trying to hack a driver together for a PCI card that uses
> shared memory to communicate to the host.
>
> If I'm not completely offtrack I need to use (under newbus/-current)
> bus_dma_tag_create, bus_dma_alloc etc to get access to the car
I'm currently trying to hack a driver together for a PCI card that uses
shared memory to communicate to the host.
If I'm not completely offtrack I need to use (under newbus/-current)
bus_dma_tag_create, bus_dma_alloc etc to get access to the cards shared
memory.
I'm looking for more detailed info
I'm currently trying to hack a driver together for a PCI card that uses
shared memory to communicate to the host.
If I'm not completely offtrack I need to use (under newbus/-current)
bus_dma_tag_create, bus_dma_alloc etc to get access to the cards shared
memory.
I'm looking for more detailed inf
12 matches
Mail list logo
