Back out the twa device:

- if allocated in the MI range, it breaks the builds for ports that do
  not use it
- if allocated in the MD range, 3ware's tw_cli tool will break because it
  hardcodes the major
This commit is contained in:
manu 2006-09-24 03:46:30 +00:00
parent 4c8d1c711c
commit 2a6884acfb
2 changed files with 2 additions and 9 deletions

View File

@ -1,5 +1,5 @@
#!/bin/sh -
# $NetBSD: MAKEDEV.tmpl,v 1.64 2006/09/23 22:24:51 manu Exp $
# $NetBSD: MAKEDEV.tmpl,v 1.65 2006/09/24 03:46:30 manu Exp $
#
# Copyright (c) 2003 The NetBSD Foundation, Inc.
# All rights reserved.
@ -278,7 +278,6 @@
# systrace syscall tracer
# tap* virtual Ethernet device
# tun* network tunnel driver
# twa* 3ware Apache control device
# twe 3ware Escalade control interface
# uk* unknown SCSI device
# veriexec verified executable fingerprint loader
@ -1105,11 +1104,6 @@ mly*)
mkdev mly$unit c %mly_chr% $unit
;;
twa*)
unit=${i#twa}
mkdev twa$unit c %twa_chr% $unit
;;
twe*)
unit=${i#twe}
mkdev twe$unit c %twe_chr% $unit

View File

@ -1,4 +1,4 @@
# $NetBSD: majors,v 1.28 2006/09/23 21:58:15 manu Exp $
# $NetBSD: majors,v 1.29 2006/09/24 03:46:30 manu Exp $
#
# Device majors for Machine-Independent drivers.
#
@ -27,4 +27,3 @@ device-major utoppy char 174 utoppy
device-major bthub char 175 bthub
device-major amr char 176 amr
device-major lockstat char 177 lockstat
device-major twa char 187