Changeset 78e3181 in rtems-libbsd for libbsd.txt
- Timestamp:
- 07/28/12 12:13:43 (12 years ago)
- Branches:
- 4.11, 5, 5-freebsd-12, 6-freebsd-12, freebsd-9.3, master
- Children:
- 116c6cf
- Parents:
- 6e77c5a
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
libbsd.txt
r6e77c5a r78e3181 48 48 49 49 == Issues and To Do 50 * Sebastian Huber: mentioned some simple test code which would verify51 that the BSD code/and or USB stack was initialized. This has been52 sent to Joel Sherrill and is pending merger.53 54 50 * Sebastian Huber and Joel Sherrill discussed the need for a a basic USB 55 51 functionality test that is known to work on qemu pc. … … 57 53 * Adapt generic IRQ PIC interface code to Simple Vectored Interrupt Model 58 54 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. 59 60 60 61 * in_cksum implementations for architectures not supported by FreeBSD. 61 62 This will require figuring out where to put implementations that do 62 63 not originate from FreeBSD and are populated via the script. 63 64 * FreeBSD generic in_cksum implementation is missing in_cksum_split so65 currently cannot be used.66 67 * How does one initialize the TCP/IP stack?68 64 69 65 * linker section issues: I have undefined symbols for … … 104 100 - What about Simple Vectored architectures? 105 101 102 * We carried over use of notepad 0 for per task information. This should 103 be changed. 104 106 105 * maxproc variable referenced by rtems-bsd-resource.c. What should it 107 106 be set to? … … 111 110 112 111 * 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 113 do not include any system on chip or ISA drivers. 114 - PCI configuration probe does not appear to happen to determine if a 115 NIC is in I/O or memory space. We have worked around this by using a 116 static hint to tell the fxp driver the correct mode. But this needs to 117 be addressed. 115 118 - The ISA drivers require more BSD infrastructure to be addressed. This was 116 119 outside the scope of the initial porting effort.
Note: See TracChangeset
for help on using the changeset viewer.