* github/pr/99:
fix an out-dated comment in the array filter code
add macro dbfl_pfield to db_field_log.h and use it in dbGet
fix in dbGet: decide use of db_field_log based on whether it has copy or not
add macro dbfl_has_copy to db_field_log.h and use it in dbAccess.c
refactor db_field_log and filters to get rid of dbfl_type_rec
make it clearer what the result of wrapArrayIndices will be
This replaces an implementation that used a header guard being defined
to indicate BSP specific options. Hopefully this method is more
explicit when config options should be set for specific BSPs.
This looks like a merge issue, where we included ne2kpci possibly
twice, based on CPU being i386 and BSP being pc686. Just
checking CPU as i386 should be sufficient for all cases.
The Soft Channel device support requests pass-1 initialization.
It no longer needs to initialize the INP link or allocate the
array buffer itself, these are taken care of elsewhere.
The record code uses PACT to remember that the device must be
initialized again in pass 1.
Allowing this while expanding DBD files for IOCs can insert other
device supports before of the Base "Soft Channel" ones, making the
other type the default. Adds a note that DBD file order matters.
Fixes lp: #1908305
rtems_init.c will write out a dhcpcd.conf if one doesn't already
exist, but if there's a filesystem including this file, don't write
over it, use whatever's there instead.
This fixes github issue #97:
Reading into an aai record from a compress or histogram or subArray record
could cause a segfault if the aai record was initialized before the
linked one.
Use strtok_r rather than strtok
Use strlen() rather than harcoded string size. GCC should optimize
this to the hardcoded string size, so the result should be the same
but maybe prevents future mistakes.
replace strncpy() with snprintf() to avoid issues with NULL terminated
strings.
In the future, it would be nice to add an ioc shell command to launch
into an RTEMS shell, but for now, it can be helpful when debugging to
enable this section for poking around in an RTEMS shell check network
configuration and stuff like that.
RTEMS dhcp will wait indefinitely for a response.
rtems_init.c will wait on DHCP for 10 minutes, before timing out and
starting main(). Note that rtems should still be waiting in the
background and a dhcp connection could still come up after this timeout.