Subject: Re: port-arm32/12120: arm32 wdc drivers should use wdc_print_modes for a bit more info
To: None <chris@paradox.demon.co.uk>
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
List: netbsd-bugs
Date: 02/04/2001 14:07:59
On Sat, Feb 03, 2001 at 01:58:42PM +0000, chris@paradox.demon.co.uk wrote:
>
> >Number: 12120
> >Category: port-arm32
> >Synopsis: arm32 wdc drivers should use wdc_print_modes for a bit more info
> >Confidential: no
> >Severity: non-critical
> >Priority: low
> >Responsible: port-arm32-maintainer
> >State: open
> >Class: change-request
> >Submitter-Id: net
> >Arrival-Date: Sat Feb 03 06:00:00 PST 2001
> >Closed-Date:
> >Last-Modified:
> >Originator:
> >Release: 02-02-2001
> >Organization:
> >Environment:
> System: NetBSD pinky.paradox.demon.co.uk 1.5R NetBSD 1.5R (PINKY2) #10: Fri Feb 2 23:47:51 GMT 2001 chris@pinky.paradox.demon.co.uk:/usr/src/src/sys/arch/i386/compile/PINKY2 i386
> Architecture: i386
> Machine: i386
> >Description:
> When booting the arm32 kernels do not output what mode the wdc device is running the channels/devices in. We should use the newish wdc_print_modes call
> >How-To-Repeat:
> Boot a kernel/check dmesg and note the lack of info on what mode wdc is running in.
I think this change is wrong, because none of these front-end support
WDC_CAPABILITY_MODE flag; so the infos printed by wdc_print_modes() will
not be accurate.
--
Manuel Bouyer <bouyer@antioche.eu.org>
--