Need help EHCI host driver on Linux 2.6.29
Dear Experts, I am developing a EHCI host driver for Linux kernel 2.6.29 on a proprietary SoC. But for weeks now, I am troubleshooting a time out error from khubd. I believe it's related to the client device not being able to update the qtd struct which has been set at some Dma addresses, say 0x87xxxxxx. Is this possible? The main issue is the register address for chip lies in 0x5a800000 range, so is the on-chip memory. If I set the qtd structs to on chip memory(internal sram), kernel paging error will occur. So I am at a loss of what I can. Please kindly advise. Best regards, CL
On Wed, Dec 22, 2010 at 07:18:35AM +0800, CL Lee wrote:
Dear Experts,
I am developing a EHCI host driver for Linux kernel 2.6.29 on a proprietary SoC. But for weeks now, I am troubleshooting a time out error from khubd.
Ick, you do realize how old 2.6.29 is, right? It's many years old, and way out of date and unsupported. If you are stuck with it, you are on your own, sorry.
I believe it's related to the client device not being able to update the qtd struct which has been set at some Dma addresses, say 0x87xxxxxx. Is this possible?
The main issue is the register address for chip lies in 0x5a800000 range, so is the on-chip memory. If I set the qtd structs to on chip memory(internal sram), kernel paging error will occur.
So I am at a loss of what I can. Please kindly advise.
Care to try your driver out on .36 or .37-rc6? and post your code? Without that, there's not much we can do, sorry. good luck, greg k-h
On Tue, Dec 21, 2010 at 5:18 PM, CL Lee <pelangi15@gmail.com> wrote:
Dear Experts,
I am developing a EHCI host driver for Linux kernel 2.6.29 on a proprietary SoC. But for weeks now, I am troubleshooting a time out error from khubd.
Which SoC? what arch? What is the error message you see?
I believe it's related to the client device not being able to update the qtd struct which has been set at some Dma addresses, say 0x87xxxxxx. Is this possible?
are you referring to qtd_dma in qdt_struct?
The main issue is the register address for chip lies in 0x5a800000 range, so is the on-chip memory. If I set the qtd structs to on chip memory(internal sram), kernel paging error will occur.
If this register address range are actual hw addresses, then yes you will see kernel paging error, unless you have ioremapped them. -syed
Hi CL Lee, I agree with Greg. The bug what you have encountered may have been fixed in latest kernels .36 or .37-rc.
I am developing a EHCI host driver for Linux kernel 2.6.29 on a proprietary SoC. But for weeks now, I am troubleshooting a time out error from khubd. The arch should be one which linux supports. Also, if it is proprietary Soc make sure you have the mach-<machine> directory in arch folder.
*- Bharath H S* On Wed, Dec 22, 2010 at 10:46 AM, Syed Khader <sk.syed2@gmail.com> wrote:
On Tue, Dec 21, 2010 at 5:18 PM, CL Lee <pelangi15@gmail.com> wrote:
Dear Experts,
I am developing a EHCI host driver for Linux kernel 2.6.29 on a proprietary SoC. But for weeks now, I am troubleshooting a time out error from khubd.
Which SoC? what arch? What is the error message you see?
I believe it's related to the client device not being able to update the qtd struct which has been set at some Dma addresses, say 0x87xxxxxx. Is this possible?
are you referring to qtd_dma in qdt_struct?
The main issue is the register address for chip lies in 0x5a800000 range, so is the on-chip memory. If I set the qtd structs to on chip memory(internal sram), kernel paging error will occur.
If this register address range are actual hw addresses, then yes you will see kernel paging error, unless you have ioremapped them.
-syed
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
participants (4)
-
Bharath H S -
CL Lee -
Greg KH -
Syed Khader