Steven Stallion wrote: > Garrett D'Amore wrote: >> Steven Stallion wrote: >>> 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: >>> >> The attributes you give below are probably horribly wrong. they >> indicate that the memory has to be 32K aligned, and in the lower 64K. >> That's probably not what you intended. >> >> My guess is you want to set addr_high to some fairly large value >> (0xffffffff if the device can address the entire 32-bit address space -- >> which if it can take a 16-bit segment pointer, and a 16-bit offset, >> should be correct). The attr_count_max should probably still be set to >> 0xffff though. > > Unless I am misreading the DP8390 spec, the device can only address the > lower 64K in dual 16-bit mode. It expects the upper 8 bits of a 16-bit > address to be programmed into the DMA engine (in this case the PSTART, > and PSTOP registers). > > Steve > _______________________________________________ > driver-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/driver-discuss
I should mention that I changed the alignment to 256 from 32768 with the same results (bad conversion from 32-bit). -- 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
