Changeset 78e3181 in rtems-libbsd


Ignore:
Timestamp:
Jul 28, 2012, 12:13:43 PM (7 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.11, c1e05b9ea378b2971e3d7704779112b4bc4296da, freebsd-9.3, 4a77611a223ea883fb548679b516d326a020d447
Children:
116c6cf
Parents:
6e77c5a
Message:

libbsd.txt: Update some status

File:
1 edited

Legend:

Unmodified
Added
Removed
  • libbsd.txt

    r6e77c5a r78e3181  
    4848
    4949== Issues and To Do
    50 * Sebastian Huber: mentioned some simple test code which would verify
    51   that the BSD code/and or USB stack was initialized.  This has been
    52   sent to Joel Sherrill and is pending merger.
    53 
    5450* Sebastian Huber and Joel Sherrill discussed the need for a a basic USB
    5551  functionality test that is known to work on qemu pc.
     
    5753* Adapt generic IRQ PIC interface code to Simple Vectored Interrupt Model
    5854  so that those architectures can use new TCP/IP and USB code.
     55
     56* freebsd-userspace/rtems/include/sys/syslog.h is a copy from the old
     57  RTEMS TCP/IP stack. For some reason, the __printflike markers do not
     58  compile in this environment. We may want to use the FreeBSD syslog.h
     59  and get this addressed.
    5960
    6061* in_cksum implementations for architectures not supported by FreeBSD.
    6162  This will require figuring out where to put implementations that do
    6263  not originate from FreeBSD and are populated via the script.
    63 
    64 * FreeBSD generic in_cksum implementation is missing in_cksum_split so
    65   currently cannot be used.
    66 
    67 * How does one initialize the TCP/IP stack?
    6864
    6965* linker section issues: I have undefined symbols for
     
    104100    - What about Simple Vectored architectures?
    105101
     102* We carried over use of notepad 0 for per task information. This should
     103be changed.
     104
    106105* maxproc variable referenced by rtems-bsd-resource.c.  What should it
    107106be set to?
     
    111110
    112111* NIC Device Drivers
    113 - Only common NIC drivers have been included in the initial set. These do not
    114 include any system on chip or ISA drivers.
     112- Only common PCI NIC drivers have been included in the initial set. These
     113do not include any system on chip or ISA drivers.
     114- PCI configuration probe does not appear to happen to determine if a
     115NIC is in I/O or memory space. We have worked around this by using a
     116static hint to tell the fxp driver the correct mode. But this needs to
     117be addressed.
    115118- The ISA drivers require more BSD infrastructure to be addressed. This was
    116119outside the scope of the initial porting effort.
Note: See TracChangeset for help on using the changeset viewer.