On Fri, Sep 03, 2010 at 11:27:14PM -0700, Pyun YongHyeon wrote:
On Fri, Sep 3, 2010 at 9:29 PM, Alexander Kabaev kab...@gmail.com wrote:
On Tue, 31 Aug 2010 17:33:48 + (UTC)
Pyun YongHyeon yong...@freebsd.org wrote:
Author: yongari
Date: Tue Aug 31 17:33:48 2010
New Revision:
On Fri, Sep 3, 2010 at 9:29 PM, Alexander Kabaev kab...@gmail.com wrote:
On Tue, 31 Aug 2010 17:33:48 + (UTC)
Pyun YongHyeon yong...@freebsd.org wrote:
Author: yongari
Date: Tue Aug 31 17:33:48 2010
New Revision: 212061
URL: http://svn.freebsd.org/changeset/base/212061
Log:
Split
Author: yongari
Date: Tue Aug 31 17:33:48 2010
New Revision: 212061
URL: http://svn.freebsd.org/changeset/base/212061
Log:
Split common parent DMA tag into ring DMA tag and TX/RX mbuf DMA
tag. All controllers that are not BCM5755 or higher have 4GB
boundary DMA bug. Previously bge(4) used
On Tuesday, August 31, 2010 1:33:48 pm Pyun YongHyeon wrote:
Author: yongari
Date: Tue Aug 31 17:33:48 2010
New Revision: 212061
URL: http://svn.freebsd.org/changeset/base/212061
Log:
Split common parent DMA tag into ring DMA tag and TX/RX mbuf DMA
tag. All controllers that are not
On Tuesday, August 31, 2010 1:54:49 pm Matthew Jacob wrote:
But not amd64 please.
Keep in mind the PAE case where you cannot effectively specify a 4GB
boundary. I used a 2GB boundary for twa(4) in the PAE case to deal
with the boundary issue. Probably though, bus_dma should just
