[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#394032: tulip instead of de4x5 for 1011:0019



[Dann Frazier] 
> This was reported in but #235285 and fixed in 1.2004.02.08-2, but
> appears to have been reverted since. I couldn't find an explanation
> in the changelog/bts, so maybe this was intentional?
>
> fyi, HP ia64 servers w/ this nic crash when de4x5 is loaded instead
> of tulip.

Do you see this problem when using the discover binary from the
discover or discover1 package?

The fix is still present for discover1, but for discover, there is no
support for architecture-specific settings.  The discover1-data
package contain the manually updated pci-ia64.lst file, and this still
list the 'tulip' kernel module for this device.

In short, I believe this is correct for discover1-data, and to fix it
in discover-data, the discover v2 package need to be extended to
understand architectures as well as kernel versions.

The current discover-data entry look like this:

  <device vendor='1011' model='0019' model_name='DECchip 21142/43' busclass='0200
'>
    <data class='linux'>
      <data class='module'>
        <data class='name'>de4x5</data>
      </data>
    </data>
  </device>

I suggest we extend discover v2 to read something like this, to select
the correct architecture override:

  <device vendor='1011' model='0019' model_name='DECchip 21142/43' busclass='0200
'>
    <data class='linux' arch='ia64'>
      <data class='module'>
        <data class='name'>de4x5</data>
      </data>
    </data>
  </device>

I'm not sure how much work it would be to implement this.

Friendly,
-- 
Petter Reinholdtsen



Reply to: