peter 593dd5803d loadandclear() uses an atomic instruction (even on SMP, where it's an ...

implicitly LOCK'ed instruction), so there shouldn't be any harm in making
it volatile pointer compatable for one of the users of it.  It seems to
generate the same code regardless.

1999-05-09 23:30:01 +00:00

..

amd64

s/main/mi_startup/ for the kernel entry point so that egcs doesn't get

1999-05-09 19:01:49 +00:00

conf

Major lobotomy of config(8). The

1999-05-09 16:46:01 +00:00

include

loadandclear() uses an atomic instruction (even on SMP, where it's an

1999-05-09 23:30:01 +00:00

isa

Move the declaration of the interrupt type from the driver structure

1999-05-08 21:59:43 +00:00

pci

Make the class code checks in function pci_cfgcheck less strict.

1997-12-20 09:04:25 +00:00

Makefile

Update to know about current kernel directory layout.

1999-02-28 22:14:16 +00:00