Support #374
loading of the driver takes 10 minutes on some hardware
| Status: | Closed | Start date: | 08/24/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ben Collins |
% Done: | 100% |
|
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
I just tried the card and driver in another computer, and the loading of the driver takes about 10 minutes there. Everytime. Then I loaded the old driver: this was finished in 6 seconds. I unloaded the old driver, and afterwards the loading of the new driver was done in some seconds. I unload and loaded the new driver a couple of times: always just some seconds.
I concluded that some code in the old driver has fixed some hardware setting, so that from this point the new driver can be loaded without trouble. In the code I found:
pci_write_config_byte(pdev, 0x40, 0x00); // Retry Timeout disable
pci_write_config_byte(pdev, 0x41, 0x00); // TRDY Timeout disable
These 2 lines are in the old driver, but not in the new driver. I inserted these lines in solo6010-core.c,
solo6010_pci_probe(...). This fixed the problem.
So my question is: What does PCI config byte 0x40 and 0x41 mean? In http://tldp.org/LDP/tlk/dd/pci.html I find "PCI Configuration Header" to be defined only up to address 0x3F.
History
Updated by Curtis Hall over 1 year ago
- Status changed from New to Assigned
We haven't seen this issue on systems we have direct access to. Is it possible to setup remote access to this machine so we can look at it?
Updated by Johannes Gajdosik over 1 year ago
I am sorry, I would really get in trouble with our IT security department. Can you not just tell me what to do, what commands to run, and I just send you the output? This would really make things much easier for me.
Updated by Ben Collins about 1 year ago
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
After discussion with Junho, this seems to be needed in normal operation. It's now added to our driver.
Thanks