Subject: port-evbmips/31992: alchemy ICU is too Au1000 specific
To: None <,,>
From: None <>
List: netbsd-bugs
Date: 11/03/2005 17:18:00
>Number:         31992
>Category:       port-evbmips
>Synopsis:       alchemy ICU is too Au1000 specific
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-evbmips-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 03 17:18:00 +0000 2005
>Originator:     Garrett D'Amore
>Release:        -current (3.99.10)
Tadpole Computer, Inc.
The interrupt strings for the au_icu.c (and some of the identifiers, etc.) are really indicative of the specific Au1000 port, and do not reflect the general Alchemy family.

This can actually lead to confusing output, e.g. from vmstat -e, because the interrupts are not wired the same on all parts.

A better solution, IMO, is to generalize the strings to "irq XX".  This provides less information than the current port does, but at least the information is not incorrect!  (And someone familiar with a given board can easily lookup up the IRQ mappings if needed.  And the actual drivers print out the IRQ they are on at attach time, so it should all be good. :-)

vmstat -e on an Au1500, for example.
I will send the patch for this shortly.