linux-2.1.125 on Alpha 164LX

Andreas Haumer (andreas@xss.co.at)
Sun, 11 Oct 1998 01:31:39 +0200


Hi!

This is just a short report about compiling and running
Linux-2.1.125 on a 164LX Alpha machine.

1.) There are several modules unconditionally using x86 assembler
statements (SCSI drivers like in2000, but others, too)
At these modules the compilation process of course fails.
In order to get a working kernel, I used a very minimalistic
configuration and excluded all those modules giving me compile
errors. I'll try to set up a list of all modules in the next
couple of days.
It would be fine if either these assembler statements could be
used on x86 systems only (providing alternatives on the other
architectures), or the whole module would be disabled on all
other architectures.

2.) In file "kernel/dma.c" there is now included the definition
and initialization of a variable called "dma_spin_lock"
Unfortunately the type of this variable (spinlock_t) and the
initialization value (SPIN_LOCK_UNLOCKED) is unknown, as the
appropriate header file is not included (neither directly nor
indirectly)
I added a "#include <asm/spinlock.h>" statement, and the file
compiled cleanly.

3.) In the theader file "asm/machvec.h", which is included by
"asm/io.h", the types u8, u16, u32 and u64 are used.
These types are declared in "asm/types.h", but unfortunately
only when __KERNEL__ is defined. So all application programs
using "asm/io.h" break, because these types are unknown (thats
the case with "sane", for instance)

Despite these problems I could compile and install 2.1.125, and it's
running for about 90 minutes now without problems.

regards

- andreas

-- 
 Andreas Haumer         | email: andreas@xss.co.at | PGP key available
 *x Software + Systeme  | phone: +43.1.6001508     | on request.
 Buchengasse 67/8       |        +43.664.3004449   |   
 A-1100 Vienna, Austria |   fax: +43.1.6001507     | AH327-RIPE

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/