Subversion Repositories HelenOS

Rev

Show changed files | Details | Compare with Previous | Blame | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
4490 5633 d 15 h decky /trunk/kernel/ remove redundant index_t and count_t types (which were always quite ambiguous and not actually needed)  
4220 5695 d 3 h decky /trunk/kernel/ update for string changes  
4011 5726 d 13 h svoboda /trunk/kernel/ String functions should be declared in string.h (and implemented in string.c) in the kernel.  
3790 5779 d 22 h svoboda /trunk/kernel/ Make newlines in panic messages consistent. Add periods at end of messages so that it is obvious whether they are printed entirely.  
3655 5819 d 14 h jermar /trunk/kernel/ Add additional members to the irq_t structure so that an interrupt-driven driver
does not need to know how to clear the level interrupt. The z8530 was modified
in this way and is much more generic. The ns16550 driver has also been modified,
but awaits testing. The sparc64 interrupt mapping and dispatch code is now using
the new info and calls the clear-interrupt-routine itself.
 
2745 6095 d 23 h decky /trunk/ code cleanup (mostly signed/unsigned)
allow extra compiler warnings
 
2071 6501 d 14 h jermar /trunk/ (c) versus (C)  
1912 6603 d 23 h jermar /trunk/kernel/ Separate mapping of EBUS interrupts into two parts: EBUS and PCI.  
1910 6607 d 12 h jermar /trunk/kernel/ Rename INO to INR, for the sake of consistency with manuals.  
1909 6608 d 13 h jermar /trunk/ Extend the OFW device tree node with a void pointer. The boot loader is
supposed to reset all pointers in all nodes. The kernel uses the pointer
to recognize that a particular device has already been visited and initialized.

Read interrupt mapping from the OFW device tree for FHC devices (z8530) and
EBUS devices (ns16550). In case of FHC devices, remove hardwired values from
the code and use only values read from the tree. FHC initialization is started
when a FHC device wants to map its interrupt. In case of EBUS devices, map
the interrupt to INO. Interrupt enabling in the interrupt controller for that
specific interrupt is not implemented yet.
 
1896 6618 d 13 h jermar /trunk/ Convert sparc64 to detect keyboard and determine
its physical address by walking the memory representation
of the OpenFirmware device tree.

Add bus-specific functions that know how to apply the
"ranges" property to one component of the "reg" property.
Buses supported so far include FHC, EBUS and PCI.