And here is another riddle for you:
After checking the devu-DDK-drivers step-by-step whether they do everything correctly, I found out that the only thing that doesn’t work, is creating the device-file in my /dev-directory.
After changing the path to /root the driver works fine and I could read out beautiful data with my Testapplikation.
So the problem, why my USB-devices won’t work, must be that there are no device-files created.
But I can’t even create/remove directories or files in my /dev-directory manually.
Has that something to to with:
(extract of the printout of pci -vvv)
Class = Serial Bus (Universal Serial Bus)
Vendor ID = 8086h, Intel Corporation
Device ID = 7112h, 82371AB/EB/MB PIIX4/4E/4M USB Interface
PCI index = 0h
Class Codes = 0c0300h
Revision ID = 1h
Bus number = 0
Device number = 7
Function num = 2
Status Reg = 280h
Command Reg = 5h
I/O space access enabled
Memory space access disabled <— LOOK HERE
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
or is it system-specific and I have to ask my Admin, what the write-settings for the /dev-directories are???
Anyway, if anybody knows what the disabled memory space access effects (or prevents) please tell me!!! And please tell me, how to change it (None of my colleagues could yet tell me that!!!
And if you want to be the first one, who gives me a reply to any of my topics… here is your chance 