| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
initialization.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
are a dummy for linking programs together when you are primarily
concerned with tricking another package into building.
This may grow into something which could help link programs on
the command line by having a default start sequence.
|
| |
|
|
|
|
| |
<mark@ramix.com> of RAMIX.
|
|
|
|
| |
pack warnings in uemf.h.
|
|
|
|
|
|
|
|
|
|
| |
<valette@crf.canon.fr> to add a port of the GoAhead web server
(httpd) to the RTEMS build tree. They have successfully used
this BSP on i386/pc386 and PowerPC/mcp750.
Mark and Joel spoke with Nick Berliner <nickb@goahead.com> on
26 Oct 1999 about this port and got verbal approval to include
it in RTEMS distributions.
|
| |
|
| |
|
|
|
|
|
| |
readdir support. The next step is to add a mount table and configure
either the miniIMFS or the full IMFS at the application level.
|
|
|
|
|
| |
disabled on exit to ISR Thread dispatching. This allows a
context switch to finish under high high interrupt rates.
|
|
|
|
|
|
|
|
|
|
|
|
| |
rdir=/opt/rtems
cd $idir
find . -type f | while read file
do
if [ ! -f ${file} ] ; then
echo ${file} missing
fi
done
|
|
|
|
| |
c/src/lib/libmisc to c/src/libmisc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
report from Philip A. Prindeville <philipp@zembu.com>:
I was working on a device driver for a certain ethernet chipset that
occassionally wraps in its buffer, and causes a resulting mbuf chain
with only a few dozen bytes in the first mbuf of the chain.
I wouldn't have thought this would be a problem, until I ran some
stress tests that flooded the ethernet receiver with packets and
started to get panics here:
250
251 if (m->m_pkthdr.len < sizeof(struct ip))
252 goto tooshort;
253
254 #ifdef DIAGNOSTIC
255 if (m->m_len < sizeof(struct ip))
256 panic("ipintr mbuf too short");
257 #endif
258
259 if (m->m_len < sizeof (struct ip) &&
260 (m = m_pullup(m, sizeof (struct ip))) == 0) {
261 ipstat.ips_toosmall++;
262 return;
263 }
264 ip = mtod(m, struct ip *);
and the panic was at line 256. But if I #undef'd DIAGNOSTICS,
then the m_pullup() at line 260 does the right thing and the packet
ends up being processed just fine.
So I started wondering, (a) why was the test checking for
something that apparently wasn't a fatal condition but rather
one that is subsequently recovered from a couple of lines later
and (b) why panic as a diagnostic "aid" from a recoverable
condition rather than just (say) log a message to the console?
All of this seems overly severe for no reason that is readily
apparent to me.
|
|
|
|
|
| |
to initialize the pthread cancellation fields. This is a patch to
_POSIX_Threads_Create_extension that fixes the problem.
|
|
|
|
| |
<raguet@crf.canon.fr> to use a local variable.
|
|
|
|
| |
process.
|
| |
|
| |
|
| |
|
|
|
|
| |
CONFIGURE_POSIX_INIT_THREAD_STACK_SIZE because in POSIX they are threads.
|
| |
|
| |
|
|
|
|
| |
Eric Norum.
|
| |
|
|
|
|
| |
Renamed IMFS handler tables to include IMFS prefix.
|
|
|
|
|
| |
places to make sure memory allocated for filesystem specifif nodes
gets freed.
|
| |
|
|
|
|
| |
routine imfs_fcntl.c
|
|
|
|
| |
node used to manage file access.
|
| |
|
|
|
|
|
| |
avoid cyclic dependencies generated when moving packages to the
top level.
|
|
|
|
| |
to its own top level package.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
now prototypes the malloc family in stdlib.h. This causes conflicts
with the way the network stack overrides the definitions of malloc.
As best I (being Joel) can tell, commenting stdlib.h out keeps the
files compiling and referencing the desired malloc/free but results
in more warnings.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and not likely to become so. Comments on each configuration
are below.
+ Force CPU386 - This BSP was developed as part of the initial
port of RTEMS to the i386. This board has been unavailable
for a long time now.
+ GO32 - This BSP and some CPU code supported djgpp v1.x. This
version is now quite old. No one has stepped forward to
update the code to v2.x which may be technically impossible
anyway. More importantly, go32 has been superceded by the pc386 BSP.
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm working on code to mount my host based file system on the base file
system (imfs) and have a suggestion for a change to eval.c in the
c/src/lib/libc directory of the 8/20/1999 snapshot. The current version
does not test the result value returned from the evalpath callback (line 47)
in the case where follow_link is true. Attached is my suggested change.
Without this test the node_type callback may be called after evalpath
failed. node_type could set the type to some value other then
RTEMS_FILESYSTEM_HARD_LINK or RTEMS_FILESYSTEM_SYM_LINK but it seems cleaner
to add the check on result.
|
|
|
|
|
|
| |
sigemptyset(&old_mask) needed to be added on glibc2 systems. Ian
Lance Taylor pointed out that sigemptyset() is portable so Joel removed
all conditionals around calls to sigemptyset().
|
|
|
|
| |
where wrapup left pieces out of the librtemsall.a.
|
|
|
|
| |
where wrapup left pieces out of the librtemsall.a.
|