PR 369/filesystem
* Makefile.am, shell/cmds.c, wrapup/Makefile.am: sample application to
show the use of the DOSFS functions
* fsmount/Makefile.am, fsmount/README, fsmount/fsmount.c,
fsmount/fsmount.h: New files.
PR 437/bsps
* irq/irc.c: calls to bspIo/printk must not use '%i' format which is
apparently not supported
* pci/pci.c: calls to bspIo/printk must not use '%i' format which is
apparently not supported
PR 441/filesystem
*src/dosfs/msdos.h: add rename support to DOSFS
*src/dosfs/msdos_create.c: add rename support to DOSFS
*src/dosfs/msdos_file.c: add rename support to DOSFS
*src/dosfs/msdos_init.c: add rename support to DOSFS
*src/dosfs/msdos_mknod.c: add rename support to DOSFS
PR 441/filesystem
*src/dosfs/msdos.h: add rename support to DOSFS
*src/dosfs/msdos_create.c: add rename support to DOSFS
*src/dosfs/msdos_file.c: add rename support to DOSFS
*src/dosfs/msdos_init.c: add rename support to DOSFS
*src/dosfs/msdos_mknod.c: add rename support to DOSFS
PR 288/rtems
* irq/irq_asm.S, startup/bspstart.c: _ISR_Nest_level is now properly
maintained and any BSP which does not do so will trip a panic in the
shared code.
PR 415/bsps
* pci/detect_raven_bridge.c, startup/bspstart.c:
This patch reverts enabling MCP interrupts for the motorola_powerpc
BSPs. REASON: pci config space scanning (as e.g. done by the DEC
Ethernet driver) would raise machine check exceptions.
PR 429/bsps
PR 432/bsps
* network/elnk.c: Due to a bug in the driver, if multiple packets
are queued onto an elnk board, the ISR will deadlock the device with
a tx complete interrupt. Lighter tx loads are not affected as they
end up submitting single packets to the device.
PR 428/bsps
PR 432/bsps
* bootloader/pci.c: Re-instated code that prevents remapping small
IO regions, which if remapped would cause i8259 registers to move
out from under the #define'd base addresses.
* startup/bspstart.c: Reduced BAT2 PCI memory allocation to 256
megs, I incorrectly had extended it which would cause problems with
PCI devices that defined prefetchable memory.
PR 430/rtems
* include/rtems/score/watchdog.h: _Watchdog_Ticks_since_boot should
be a VOLATILE variable.
* src/watchdoginsert.c: 'restart' algorithm needs to enforce
reloading the list head in case a TICK interrupt during ISR_Flash()
modified the list. This is achieved by a proper VOLATILE cast.
Also _Watchdog_Sync_count++ should be protected by _ISR_Disable
(prevent corruption in case ISR calls watchdoginsert)
* src/watchdogadjust.c: ISR protection added.
* src/watchdogtickle.c: ISR protection added.
NOTE: PowerPC BSPs using the new exception processing MUST BE UPDATED
to maintain _ISR_Nest_level. See also PR288 which provides fixes
for the affected BSPs distributed with RTEMS.
PR 433/tools
* mips-stub.c: Patch from C. M. Heard <heard@pobox.com> described as:
The purpose of the patch is to make the stub ignore all
characters except '+' (ack) or '-' (nak) when it has transmitted a
packet and expects an acknowledgment. Without the patch,
putpacket() will retransmit each time it receives anything other
than '+' when expecting an ack, and that, bitter experience has
found, frequently results in the stub failing to sync up when
initially attaching to gdb.
I think that rtems users will notice significant improvement in
the of the mips stub if this patch is incorporated in the
distribution; certainly I did in my stand-aline environment. I
should hasten to add that it is only an improvement and not a 100%
cure for synchronization problems because '+' characters can (and
do) during as message data, and it's still possible for these to
be mistaken as acks. I have no idea how to fix that short of
redesigning the gdb-remote protocol.
* aclocal/multi.m4: Don't add --enable-multilib.
Rename AC_ENABLE_MULTILIB into AM_ENABLE_MULTILIB.
Increment serial to 103 (automake's multi.m4 version + 100).
* configure.ac: Use AM_ENABLE_MULTILIB instead of
AC_ENABLE_MULTILIB.
2003-07-03 Joel Sherrill <joel@OARcorp.com>
* aclocal/version.m4: Updated to rtems-4.6.0pre4.
PR 416/bsps
* ppc403/ictrl/ictrl.c (ictrl_isr): We acknolwegde the interrupt in
interrupt controller (clr_exisr(mask)) before calling the interrupt
handler that will acnowledge the interrupt source. This results in
the interrupt beeing seen a second time by the interrupt controller.
Reported and fixed by El Kolli Yacine <yacine.elkolli@crf.canon.fr>.
