Honored Contributor
Honored ContributorI am now adding printk's to the kernel and re-building it ... I do know where it fails but need to track back as to why the dev-> resource's are start = 0, end = 0xFFFFF, for the first resource ... where I believe each resource is a block of memory map allocated to the BAR register.
To make it simple I first reduced the BAR size to be 20 bits .. from 28 bits since that amount of memory was not available in the map. I then tried making BAR 0 32 bits and not pre-fetchable. BAR 1 disabled and BAR 2 32 bits. I have now reduced to just BAR 0, non-prefetch ... I have to believe the system supports non-prefetch memory which is necessary for any control registers. The particular test that is failing is for the first dev->resource.start != 0 and dev->resource.end = 0xFFFFF. the first test fails and the printk reports a "resource collision". I need to work back to see why the start value isn't a meaningful number ... The dmesg outpus doesn't seem to have any particular errors. Any ideas on this ? Thanks BCD.
