Changes between Initial Version and Version 1 of Ticket #9807, comment 8


Ignore:
Timestamp:
Jun 29, 2013, 9:42:42 PM (11 years ago)
Author:
ttcoder

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9807, comment 8

    initial v1  
    1 @korli -- ok so the driver compiles, and... it behaves differently from the nightly image's driver: it complains about unsupported hardware and then bails out and unloads.
     1@korli -- ok so the driver compiles, and... it behaves differently from the nightly image's driver: it complains about unsupported hardware and then bails out and unloads:
     2
     3{{{
     4KERN: allocate_io_interrupt_vectors: allocated 1 vectors starting from 24
     5KERN: msi_allocate_vectors: allocated 1 vectors starting from 24
     6KERN: [rtl81xx] (re) Using 1 MSI message
     7KERN: [rtl81xx] (re) bus_alloc_resource(1, [1], 0x0, 0xffffffff, 0x1,0x2)
     8KERN: [rtl81xx] (re) Chip rev. 0x48000000
     9KERN: [rtl81xx] (re) MAC rev. 0x00000000
     10KERN: [rtl81xx] (re) Unknown H/W revision: 0x48000000
     11KERN: msi_free_vectors: freeing 1 vectors starting from 24
     12KERN: free_io_interrupt_vectors: freeing 1 vectors starting from 24
     13KERN: remove_memory_type_range(3086, 0xd0004000, 0x20000, 0)
     14
     15}}}
     16
     17
    218
    319I first thought it was my fault, maybe the freebsd compatibility layer has changed since I cloned the repository (I only updated the driver source, not the rest), but it seems my build of the driver is justified in complaining about unsupported hardware, as my Rtl8111 has ID {{{0x48000000}}} and that value is nowhere to be found in {{{if_rlreg.h}}}.. So I added some extra tracing, result attached down here. What I'm describing will be more clear when reading it.