Changeset 560eccf in rtems-libbsd for libbsd.txt
- Timestamp:
- 03/12/12 12:02:00 (12 years ago)
- Branches:
- 4.11, 5, 5-freebsd-12, 6-freebsd-12, freebsd-9.3, master
- Children:
- 7326d96
- Parents:
- ec94238
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
libbsd.txt
rec94238 r560eccf 44 44 archive used is located at http://www.rtems.org/ftp/pub/rtems/people/joel/freebsd 45 45 46 == To Do 46 == Issues and To Do 47 * Sebastian Huber: mentioned some simple test code which would verify 48 that the BSD code/and or USB stack was initialized. This has been 49 sent to Joel Sherrill and is pending merger. 50 51 * Sebastian Huber and Joel Sherrill discussed the need for a a basic USB 52 functionality test that is known to work on qemu pc. 53 47 54 * Adapt generic IRQ PIC interface code to Simple Vectored Interrupt Model 48 55 so that those architectures can use new TCP/IP and USB code. 56 49 57 * in_cksum implementations for architectures not supported by FreeBSD. 50 58 This will require figuring out where to put implementations that do 51 59 not originate from FreeBSD and are populated via the script. 52 * generic in_cksum implementation is missing in_cksum_split so currently 53 cannot be used. 60 61 * FreeBSD generic in_cksum implementation is missing in_cksum_split so 62 currently cannot be used. 63 64 * How does one initialize the TCP/IP stack? 65 66 * linker section issues: I have undefined symbols for 67 _bsd__start_set_sysinit_set and _bsd__stop_set_sysinit_set. 68 Is this the only type of new section magic? What about the old sysctl_set? 69 I added this to my linkcmds. 70 71 [listing] 72 ---- 73 /* sysinit section? */ 74 . = ALIGN (16); 75 _bsd__start_set_sysinit_set = .; 76 *(set_sys_init_*); 77 _bsd__stop_set_sysinit_set = .; 78 79 ---- 80 81 * Convert all BSP linkcmds to use a linkcmds.base so the sections are 82 easier to insert. 83 84 * rtems-bsd-init-with-irq.c: 85 rtems_bsd_initialize_with_interrupt_server() has reference to 86 rtems_interrupt_server_initialize() and this method is unimplemented 87 - XXX BSP implements pieces 88 - BSPs using this software stack must support it apparently. 89 - What about Simple Vectored architectures? 90 91 * maxproc variable referenced by rtems-bsd-resource.c. What should it 92 be set to? 93 94 * ngroups_max variable referenced by rtems-bsd-prot.c. - What should 95 it be set to? 54 96 55 97 == FreeBSD Source … … 80 122 Any changes to sources in the freebsd or contrib directories will need to 81 123 be merged upstream into our master FreeBSD svn checkout. 124 125 The FreeBSD sources managed in RTEMS libbsd git repository (e.g. contrib 126 and freebsd directories) contain the "managed" version of the 127 FreeBSD source. The FreeBSD SVN source is the "master" version. The 128 freebsd-to-rtems.py script is used to transfer files between the two 129 trees. In general terms, if you have modified FreeBSD in the RTEMS libbsd 130 tree, you want to run the script in "revert" or "reverse" mode to move 131 the source back so you can run an "svn diff" against the upstream FreeBSD 132 source. If you want to transfer source from the FreeBSD SVN checkout to 133 the RTEMS libbsd tree, then you want to run the script in "forward" or 134 default mode. 82 135 83 136 === Building RTEMS libbsd source
Note: See TracChangeset
for help on using the changeset viewer.