Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update for present reality

This commit is contained in:
cgd 1996-04-25 04:28:04 +00:00
parent aff40e2a72
commit 72e70ce045
2 changed files with 79 additions and 66 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

101
sys/arch/alpha/STATUS
View File

@ -1,7 +1,10 @@
$NetBSD: STATUS,v 1.2 1995/11/23 02:33:26 cgd Exp $
$NetBSD: STATUS,v 1.3 1996/04/25 04:28:04 cgd Exp $
NetBSD/Alpha's Status
If you find an inaccuracy in this file, can clarify it in any place,
etc., please send mail to me (cgd@cs.cmu.edu).
Supported hardware:
@ -9,54 +12,70 @@ Supported hardware:
600, but the rest should "just work) using the following
peripherals:
Built-in serial ports
LANCE ethernet -- only the on-board interface. (see below.)
SCSI system -- it recognizes and can use both on-board SCSI
controller chips. However, it has trouble working with
both at the same time.
Supported hardware:
Built-in serial ports
Built-in LANCE ethernet.
Built-in SCSI chips (53c[f]94), though both
may not work at the same time.
Things that may work but haven't been tested:
TurboChannel option slot LANCE (PMAD-A)
Things are aren't supported:
No frame buffers of any type.
Devices in TurboChannel option slots (see the
Other TurboChannel option boards (see the
TODO.users file.)
The ISDN/Audio chip.
DEC 3000/300 family, with same hardware above.
*** NOTE THAT I HAVE NOT TESTED NEW KERNELS THOROUGHLY ON
DEC 3000/[3-900] SYSTEMS!
AlphaStation {200,250,400} systems using the following
AlphaStation {200,250,255,400} systems using the following
peripherals:
On-board NRC 53c810 SCSI.
On-board ns16550-based serial ports.
DC21040-based ethernet (on-board or in an option
slot).
DC21050-based PCI-PCI bridges (though other
types of PCI-PCI bridges should work).
PCI VGA video boards.
DEC ZLXp-E1 (DC21030-based, "TGA") video boards.
Keyboard.
Supported hardware:
NCR 53c810 SCSI (built-in or PCI board).
Built-in ns16550 serial ports.
DC21040-based ethernet (built-in or PCI board).
DC21140-based PCI ethernet boards.
DC21050-based PCI-PCI bridges (though other
types of PCI-PCI bridges should work).
PCI VGA video boards.
DEC ZLXp-E1 (DC21030-based, "TGA") video boards.
Keyboard.
PS/2-style mice.
Things that may work but haven't been tested:
Built-in parallel ports.
ISA ns16x50-family serial port boards.
ISA ns16x50 multi-port serial boards.
Other NCR 53c8xx SCSI boards.
Things that ARE NOT supported at this time:
DEC ZLXp-E2 and ZLXp-E3 video boards.
Mouse.
Sound hardware (Windows Sound System).
ISA VGA boards.
Sound hardware (including Windows Sound System
built-in on some machines).
DEC ZLXp-E2 and ZLXp-E3 PCI video boards.
Other PCI boards.
AlphaStation 600 systems, with the same supported hardware
list as the AlphaStation {200,250,400} systems. (NOTE THAT
THAT MEANS THE AlphaStation 600's BUILT-IN SCSI CONTROLLERS
DO NOT WORK. You'll need to get a 53c810 board, or
something.)
list as the AlphaStation {200,250,255,400} systems. (NOTE
THAT THAT MEANS THE AlphaStation 600's BUILT-IN SCSI
CONTROLLERS DO NOT WORK. You'll need to get a 53c810 board,
or run diskless.) AlphaStation 500 systems may work, but
have not been tested.
AXPpci systems, with the same supported hardware list as
the AlphaStation {200,250,400} systems. (AXPpci support
was written by Jeffrey Hsu. Thanks, Jeff!)
the AlphaStation {200,250,255,400} systems.
NOTE: As far as I know, testers have not tested current kernels
throughly on DEC 3000/[3-900] systems, or AT ALL AlphaStation 600
systems!
At this time none of the following systems are supported:
DECpc AXP systems (EISA-bus PC-like systems)
Alpha "server" systems
DECpc AXP 150 systems (EISA-bus PC-like systems)
Alpha "server" systems (other than perhaps the
AlphaServer 400, which might be an AlphaStation 400
in disguise).
Multiprocessor Alpha systems
I was hoping to get a DECpc AXP port working "for free" based on
@ -66,28 +85,30 @@ NetBSD/Alpha run on the DECpc AXP system, get in touch and I'll do
what I can to help you get started.
Console frame buffers & keyboard are supported only on the AlphaStation
and AXPpci families of machines. On the TurboChannel-baesd machines,
NetBSD/Alpha _must_ be used with a serial console. To configure various
Alpha systems to use a serial console, do the following depending on
the model:
Console frame buffers & keyboard are supported only with the frame
buffers and keyboards mentioned as supported above. On other systems
(including all TurboChannel-based machines), NetBSD/Alpha _must_ be used
with a serial console. To configure various Alpha systems to use a serial
console, do the following depending on the model:
DEC 3000/[4-9]00's:
Flip the appropriate switch on the back of the machine.
(See your owner's manual for more details.)
DEC 3000/300 family machines:
Boot the machine with the keyboard/mouse connector
unplugged.
DECpc AXPs, AXPpcis, and AlphaStations:
DECpc AXPs, AlphaStations, and AXPpci systems:
Get to the console prompt. Set the variable
"console" to be "serial", and "init" or power cycle
the system.
See your owner's manual for more details on how to set your machine
to use a serial console.
See the file src/sys/arch/alpha/README to find out how to get the
latest sources and/or binaries.
latest sources and binaries.
Please see the file src/sys/arch/alpha/TODO.users for a list of things
that users can do to help NetBSD/Alpha improve. If you're interested
@ -96,4 +117,4 @@ I'll do what I can to help.
Chris Demetriou
cgd@netbsd.org
cgd@cs.cmu.edu

44
sys/arch/alpha/TODO.users
View File

@ -1,14 +1,14 @@
$NetBSD: TODO.users,v 1.2 1995/11/23 02:33:29 cgd Exp $
$NetBSD: TODO.users,v 1.3 1996/04/25 04:28:05 cgd Exp $
The NetBSD/Alpha "User" To-Do List
The following are things that I'd like to see "users" of NetBSD/Alpha do.
It's unlikely that I'll get around to them in any reasonable time
frame, and I think they _should_ get done.
The following are things that I'd like to see "users" of NetBSD/Alpha
do. It's unlikely that I'll get around to them in any reasonable time
frame, and I think they should get done.
If you think of something that should be added to this list (and don't
want to do it yourself, right then 8-), send me mail and I'll add it.
If you think of something that should be added to this list send me
mail and I'll add it.
If you're planning to work on something on this list, send me mail and
tell me about it, so that I can keep people from duplicating work.
@ -16,35 +16,27 @@ Once you've done something on this list, send me context diffs.
Chris Demetriou
cgd@netbsd.org
cgd@cs.cmu.edu
--
Make GDB work.
(1) function arguments and local variables don't seem to work.
Test programs; find and fix bugs. In particular:
(1) make sure accounting works
(2) figure out why strip doesn't seem to work
(3) last i checked, 'file' core dumped
(4) /usr/games
(2) last i checked, 'file' core dumped
(3) /usr/games
Make TurboChannel option slots work reasonably. This will require
different sets of code to be written on the 3000/[4-9]00 and on the
3000/300 families. It shouldn't be too hard, but you will need some
devices that live in option slots.
Once TC option slots work, somebody with a TC ethernet board should
make it work, for completeness.
Test TurboChannel option slot support. Write TurboChannel option
board support. Test PMAD-A support.
Get the GNU tools to generate a.out binaries for the alpha. Once that
is done:
is done:
(1) make gprof work, then profile the kernel and tell me how
bad my assumptions lost.
bad my assumptions lost. (Actually, the gprof in the Cygnus
toolchain may already work.)
(2) make the rest of the NetBSD a.out-manipulation tools (e.g.
nm) work.
Make DDB work. (For completeness, may require a.out kernel binaries
and/or some ecoff symbol handling code to be written; the former
is strongly preferred.)
and/or some ecoff symbol handling code to be written; the former is
strongly preferred.)
Track down bugs caused by compiling the kernel with -O. (At least
some of these are likely to be code generation bugs.)
Track down any bugs caused by compiling the kernel with -O. (At least
some of these may be code generation bugs.)