----- Original Message -----
>Date: Wed, 03 Sep 2008 23:10:20 -0500
>From: Steven Stallion <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>CC: Masa Murayama <[EMAIL PROTECTED]>, [email protected]
>Subject: Re: [driver-discuss] DP8390 single-bus DMA alignment
>
>
>Well, I swapped everything over to re and moved over to 16-bit DMA. I'm
>now seeing the following:
>
>Sep  3 22:53:09 devel pcisch: [ID 876218 kern.warning] WARNING: re0 peer
>only dev 60015ae7e00
>Sep  3 22:53:09 devel pcisch: [ID 346402 kern.warning] WARNING: re0 peer
>only device bad attr
>Sep  3 22:53:09 devel re: [ID 179634 kern.warning] WARNING: re0 failed
>to allocate DMA resources!
>
>re_dma_attr is:
>
>114 static ddi_dma_attr_t re_dma_attr = {
>
>115         DMA_ATTR_V0,    /* dma_attr_version */
>
>116         0,              /* dma_attr_addr_lo */
>
>117         0xffff,         /* dma_attr_addr_hi */
>
>118         0xffff,         /* dma_attr_count_max */
>
>119         32768,          /* dma_attr_align */
>
>120         0x1f,           /* dma_attr_burstsizes */
>
>121         1,              /* dma_attr_minxfer */
>
>122         0xffff,         /* dma_attr_maxxfer */
>
>123         0xffff,         /* dma_attr_seg */
>
>124         1,              /* dma_attr_sgllen */
>
>125         1,              /* dma_attr_granular */
>
>126         0               /* dma_attr_flags */
>
>127 };
>
>
>Any ideas?
>

Typical sparc IOMMU DVMA range is 0xff000000 - 0xffffffff, the highest
16Mbyte in PCI memory sparce. Threfore,  PCI master devices *must*
support the range for dma.

 Recently I saw the same message for BCM4401 driver on sparc,
the divece only supports the dma range of 0x00000000 - 0x40000000,
the lowest 1Gbyte. So bcm4401 doesn't work on sparc. 

-masa


>Yet magic and hierarchy
>arise from the same source,
>and this source has a null pointer.
>
>Reference the NULL within NULL,
>it is the gateway to all wizardry.

_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to