Hi,
On 08/12/13 03:19, aseem.jolly wrote:
if (EHCI_HCC_64BIT(cparams)) {
DPRINTF(HCC uses 64-bit structures\n);
/* MUST clear segment register if 64 bit capable */
EWRITE4(sc, EHCI_CTRLDSSEGMENT, 0);
}
On 08/11/13 04:47, aseem.jolly wrote:
I'm trying to allocate memory from 4GB-8GB range and have modified the memory
structure(QH,iTD etc) to support 64 bit addressing. I am constantly hitting
the following issues and I am not sure about the exact meaning of the error
message(timed out waiting
if (EHCI_HCC_64BIT(cparams)) {
DPRINTF(HCC uses 64-bit structures\n);
/* MUST clear segment register if 64 bit capable */
EWRITE4(sc, EHCI_CTRLDSSEGMENT, 0);
}
sc-sc_bus.usbrev = USB_REV_2_0;
/* Reset the controller
After making the above said changes, I ran into another problem
Root mount waiting for: usbus0
ehci_timeout: xfer=0xff8001e6c148
ehci_device_done: xfer=0xff8001e6c148, endpoint=0xff001fef28f8,
error=20
ehci_device_done: xfer=0xff8001e6c148, endpoint=0xff001fef28f8,
error=5
I'm trying to allocate memory from 4GB-8GB range and have modified the memory
structure(QH,iTD etc) to support 64 bit addressing. I am constantly hitting
the following issues and I am not sure about the exact meaning of the error
message(timed out waiting for BIOS).
ehci1: [ITHREAD]
usbus0:
On 08/07/13 04:32, aseem.jolly wrote:
I have gone through EHCI specification(was pretty long so couldn't finish it
though) and below is what that I have understood.
Control Data Structure Segment Register 'CTRLDSSEGMENT', This register
allows the host software to locate all control data
On 08/06/13 03:24, aseem.jolly wrote:
I don't want to play around with 'kern.maxbcache', can we actually allow
driver to support 64 bit DMA?
In future we can use a bootarg/sysctl to enable this support if someone
comes across this issue else we will use 32 bit DMA allocations.
I am willing to
I have gone through EHCI specification(was pretty long so couldn't finish it
though) and below is what that I have understood.
Control Data Structure Segment Register 'CTRLDSSEGMENT', This register
allows the host software to locate all control data structures within the
same 4 Gigabyte memory
I don't want to play around with 'kern.maxbcache', can we actually allow
driver to support 64 bit DMA?
In future we can use a bootarg/sysctl to enable this support if someone
comes across this issue else we will use 32 bit DMA allocations.
I am willing to enable this support, please guide me.
To: freebsd-usb@freebsd.org mailto:freebsd-usb@freebsd.org
Subject: RE: USB DMA memory Allocation
I am getting the following error 'USB_ERR_NOMEM' when I try to allocate DMA
memrory from [0 4GB] range, I have to enable 64 bit memory allocation.
Can you please briefly explain what I need to do
Hi,
I think there are a few bits to put the high 32-bits into the transfer
descriptors and such missing. You are right we don`t really need to use 32-bit
only for the USB controllers. Though we`ve seen a couple of times that even
32-bit controllers don`t implement the full 32-address lines.
I am getting the following error 'USB_ERR_NOMEM' when I try to allocate DMA
memrory from [0 4GB] range, I have to enable 64 bit memory allocation.
Can you please briefly explain what I need to do to enable this support?
--
View this message in context:
12 matches
Mail list logo