source: rtems-libbsd/libbsd.txt @ 164c5f5

4.115-freebsd-12freebsd-9.3
Last change on this file since 164c5f5 was 164c5f5, checked in by Sebastian Huber <sebastian.huber@…>, on Jan 15, 2014 at 11:46:22 AM

UNIX(4): Import from FreeBSD

  • Property mode set to 100644
File size: 26.1 KB
Line 
1RTEMS BSD USB and TCP/IP Developers Guide
2=========================================
3Joel Sherrill <joel.sherrill@oarcorp.com>
4:Author Initials: JRS
5:toc:
6:icons:
7:numbered:
8:website: http://www.rtems.org/
9
10RTEMS uses FreeBSD as the source of its TCP/IP and USB stacks.
11This is a developers guide which captures information on the
12process of merging code from FreeBSD, building this library,
13RTEMS specific support files, and general guidelines on what
14modifications to the FreeBSD source are permitted.
15
16Goals of this effort are:
17
18* Update TCP/IP and provide USB in RTEMS
19* Ease updating to future FreeBSD versions
20* Ease tracking changes in FreeBSD code
21* Minimize manual changes in FreeBSD code
22* Define stable kernel/device driver API which is implemented
23by both RTEMS and FreeBSD. This is the foundation of the port.
24
25We will work to push our changes upstream to the FreeBSD Project
26and minimize changes required at each update point.
27
28**************************************************************
29This is a work in progress and is very likely to be incomplete.
30Please help by adding to it.
31**************************************************************
32
33== Source Code Version Information
34
35* FreeBSD 8.2 SVN r255967
36* RTEMS 4.11
37  - BSP must have support for all new BSD sys sections
38  - It is preferable if the BSP uses linkcmds.base.
39  - BSP must be from an architecture with Programmable Interrupt Controller
40    interrupt model.
41
42The latest port uses the FreeBSD sources as a Git submodule which will
43generally be referred to as the FreeBSD source in this document.  Previously a
44FreeBSD 8.2 SVN checkout was used.  The SVN checkout command corresponding to
45the current Git submodule commit is this
46  svn co http://svn.freebsd.org/base/releng/8.2 -r255967 freebsd-8.2
47
48== Issues and To Do
49* Per-CPU data should be enabled once the new stack is ready for SMP.
50
51* Per-CPU NETISR(9) should be enabled onece the new stack is ready for SMP.
52
53* Multiple routing tables are not supported.  Every FIB value is set to zero
54  (= BSD_DEFAULT_FIB).
55
56* Process identifiers are not supported.  Every PID value is set to zero
57  (= BSD_DEFAULT_PID).
58
59* User credentials are not supported.  The following functions allow the
60  operation for everyone
61  - prison_equal_ip4(),
62  - chgsbsize(),
63  - cr_cansee(),
64  - cr_canseesocket() and
65  - cr_canseeinpcb().
66
67* Sebastian Huber and Joel Sherrill discussed the need for a a basic USB
68  functionality test that is known to work on qemu pc.
69
70* Adapt generic IRQ PIC interface code to Simple Vectored Interrupt Model
71  so that those architectures can use new TCP/IP and USB code.
72
73* freebsd-userspace/rtems/include/sys/syslog.h is a copy from the old
74  RTEMS TCP/IP stack. For some reason, the __printflike markers do not
75  compile in this environment. We may want to use the FreeBSD syslog.h
76  and get this addressed.
77
78* in_cksum implementations for architectures not supported by FreeBSD.
79  This will require figuring out where to put implementations that do
80  not originate from FreeBSD and are populated via the script.
81
82* linker section issues: I have undefined symbols for
83  `_bsd__start_set_sysinit_set` and `_bsd__stop_set_sysinit_set`.
84  Is this the only type of new section magic?  What about the old sysctl_set?
85  I added this to my linkcmds. 
86
87* MAC support functions are not thread-safe ("freebsd/lib/libc/posix1e/mac.c").
88
89* IFCONFIG(8): IEEE80211 support is disabled.  This module depends on a XML
90  parser and mmap().
91
92* get_cyclecount(): The implementation is a security problem.
93
94* What to do with the priority parameter present in the FreeBSD synchronization
95  primitives and the thread creation functions?
96
97* TASKQUEUE(9): Support spin mutexes.
98
99* ZONE(9): Review allocator lock usage in rtems-bsd-chunk.c.
100
101* KQUEUE(2): Choose proper lock for global kqueue list.
102
103* TIMEOUT(9): Maybe use special task instead of timer server to call
104  callout_tick().
105
106* sysctl_handle_opaque(): Implement reliable snapshots.
107
108* PING6(8): What to do with SIGALARM?
109
110* <sys/param.h>: Update Newlib to use a MSIZE of 256.
111
112* BPF(4): Add support for zero-copy buffers.
113
114* UNIX(4): Fix race conditions in the area of socket object and file node
115  destruction.  Add support for file descriptor transmission via control
116  messages.
117
118[listing]
119----
120    /* sysinit section? */
121    . = ALIGN (16);
122    _bsd__start_set_sysinit_set = .;
123    *(set_sys_init_*);
124    _bsd__stop_set_sysinit_set = .;
125
126----
127
128* Why is the interrupt server used?  The BSD interrupt handlers can block on
129synchronization primitives like mutexes.  This is in contrast to RTEMS
130interrupt service routines.  The BSPs using the generic interrupt support must
131implement the `bsp_interrupt_vector_enable()` and
132`bsp_interrupt_vector_disable()` routines.  They normally enable/disable a
133particular interrupt source at the interrupt controller.  This can be used to
134implement the interrupt server.  The interrupt server is a task that wakes-up
135in case an associated interrupt happens.  The interrupt source is disabled in
136a generic interrupt handler that wakes-up the interrupt server task.   Once the
137postponed interrupt processing is performed in the interrupt server the
138interrupt source is enabled again.
139
140* Convert all BSP linkcmds to use a linkcmds.base so the sections are
141easier to insert.
142
143* rtems-bsd-init-with-irq.c:
144  rtems_bsd_initialize_with_interrupt_server() has reference to
145    rtems_interrupt_server_initialize() and this method is unimplemented
146    - XXX BSP implements pieces
147    - BSPs using this software stack must support it apparently.
148    - What about Simple Vectored architectures?
149
150* We carried over use of notepad 0 for per task information. This should
151be changed.
152
153* maxproc variable referenced by rtems-bsd-resource.c.  What should it
154be set to?
155
156* ngroups_max variable referenced by rtems-bsd-prot.c.  - What should
157it be set to?
158
159* NIC Device Drivers
160- Only common PCI NIC drivers have been included in the initial set. These
161do not include any system on chip or ISA drivers.
162- PCI configuration probe does not appear to happen to determine if a
163NIC is in I/O or memory space. We have worked around this by using a
164static hint to tell the fxp driver the correct mode. But this needs to
165be addressed.
166- The ISA drivers require more BSD infrastructure to be addressed. This was
167outside the scope of the initial porting effort.
168
169== FreeBSD Source
170
171You should be able to rely on FreebSD manual pages and documentation
172for details on the code itself.
173
174=== Automatically Generated FreeBSD Files
175
176The FreeBSD source tarball includes a file named Makefile.rtems which
177has stanzas to automatically generate some files using awk. For details
178on this, see http://www.freebsd.org/cgi/man.cgi?query=kobj&apropos=0&sektion=0&manpath=FreeBSD+9.0-RELEASE&arch=default&format=html
179
180XXX This needs more detail.
181
182=== Rules for Modifying FreeBSD Source
183
184* Only add lines.  Subtract code by added "ifndef __rtems__". This makes
185merging easier in the future.
186
187== libbsd Source
188
189=== What is in git
190
191The git source is a self-contained kit with FreeBSD and RTEMS components
192pre-merged. The Makefile in this kit is automatically generated.
193
194Any changes to sources in the freebsd or contrib directories will need to
195be merged upstream into our master FreeBSD svn checkout.
196
197The FreeBSD sources managed in the rtems-libbsd git repository (e.g. contrib
198and freebsd directories) contain the "managed" version of the
199FreeBSD source.  The FreeBSD SVN source is the "master" version. The
200freebsd-to-rtems.py script is used to transfer files between the two
201trees. In general terms, if you have modified FreeBSD (i.e. anything in the
202freebsd directory) in the rtems-libbsd tree, you will need to run the script
203in "revert" or "reverse" mode using the -R switch. This will copy the source
204back to your local copy of the FreeBSD source so you can run "svn diff" against
205the upstream FreeBSD source. If you want to transfer source files from the
206FreeBSD SVN checkout to the rtems-libbsd tree, then you must run the script in
207"forward" mode (the default).
208
209=== Building rtems-libbsd source
210
211You need to configure RTEMS for the desired BSP and install it. The
212following is the script used to build the powerpc/psim BSP for our
213internal testing purposes:
214
215[listing]
216----
217#! /bin/sh
218
219cd ${HOME}/newbsd
220rm -rf b-psim
221mkdir b-psim
222cd b-psim
223../git/rtems/configure --target=powerpc-rtems4.11 \
224  --enable-rtemsbsp=psim --disable-networking \
225  --enable-tests=samples \
226  --prefix=${HOME}/newbsd/bsp-install >c.log 2>&1 && \
227  make >b.log 2>&1 && \
228  make install >i.log 2>&1
229echo $?
230----
231
232Then edit the file config.inc to set RTEMS_MAKEFILE_PATH appropriately
233to indicate the ${prefix}/${target}/${BSP}.  Continuing on the above,
234the config.inc used to match the above is:
235
236[listing]
237----
238RTEMS_MAKEFILE_PATH = ${HOME}/newbsd/bsp-install/powerpc-rtems4.11/psim/
239INSTALL_BASE = ${HOME}/newbsd/install
240----
241
242The above installs the rtems-libbsd kit into a separate place from
243RTEMS and the BSP. The rtems-libbsd tests are built against an installed
244image of the rtems-libbsd. By keeping it in a separate installation point
245from RTEMS itself, this makes it easier to remove a libbsd installation
246and have a clean test point.
247
248[listing]
249----
250make
251make install
252make -C testsuite
253----
254
255At this point, we expect multiple linker errors. That is what we are
256currently working on.
257
258=== Organization
259
260The top level directory contains a few directories and files. The following
261are important to understand:
262
263* freebsd-to-rtems.py - script to convert to and free FreeBSD and RTEMS trees
264* Makefile - automatically generated
265* contrib/ - from FreeBSD by script.
266* freebsd/ - from FreeBSD by script.
267* rtemsbsd/ - RTEMS specific implementations of FreeBSD kernel support routines.
268* testsuite/ - RTEMS specific tests
269* libbsd.txt - Documentation in Asciidoc
270
271== Moving Code Between FreeBSD SVN and rtems-libbsd
272
273The script freebsd-to-rtems.py is used to copy code from FreeBSD to the
274rtems-libbsd tree and to reverse this process. This script attempts to
275automate this process as much as possible and performs some transformations
276on the FreeBSD code. Its command line arguments are shown below:
277
278[listing]
279----
280freebsd-to-rtems.py [args]
281  -?|-h|--help     print this and exit
282  -d|--dry-run     run program but no modifications
283  -D|--diff        provide diff of files between trees
284  -e|--early-exit  evaluate arguments, print results, and exit
285  -m|--makefile    just generate Makefile
286  -R|--reverse     default FreeBSD -> RTEMS, reverse that
287  -r|--rtems       RTEMS directory
288  -f|--freebsd     FreeBSD directory
289  -v|--verbose     enable verbose output mode
290----
291
292In its default mode of operation, freebsd-to-rtems.py is used to copy code
293from FreeBSD to the rtems-libbsd tree and perform transformations.  In forward
294mode, the script may be requested to just generate the Makefile.
295
296In "reverse mode", this script undoes those transformations and copies
297the source code back to the FreeBSD SVN tree. This allows us to do
298'svn diff', evaluate changes made by the RTEMS Project, and report changes
299back to FreeBSD upstream.
300
301In either mode, the script may be asked to perform a dry-run or be verbose.
302Also, in either mode, the script is also smart enough to avoid copying over
303files which have not changed. This means that the timestamps of files are
304not changed unless the contents change. The script will also report the
305number of files which changed. In verbose mode, the script will print
306the name of the files which are changed.
307
308The following is an example forward run with no changes.
309
310[listing]
311----
312$ ~/newbsd/git/libbsd-8.2/freebsd-to-rtems.py \
313    -r /home/joel/newbsd/git/libbsd-8.2 \
314    -f /home/joel/newbsd/libbsd/freebsd-8.2 -v
315Verbose:                yes
316Dry Run:                no
317Only Generate Makefile: no
318RTEMS Directory:        /home/joel/newbsd/git/libbsd-8.2
319FreeBSD Directory:      /home/joel/newbsd/libbsd/freebsd-8.2
320Direction:              forward
321Generating into /home/joel/newbsd/git/libbsd-8.2
3220 files were changed.
323----
324
325The script may also be used to generate a diff in either forward or reverse
326direction.
327
328== Initialization of rtems-libbsd
329
330The initialization of the rtems-libbsd is based on the FreeBSD SYSINIT(9)
331infrastructure.  The key to initializing a system is to ensure that the desired
332device drivers are explicitly pulled into the linked application.  This plus
333linking against the libbsd library will pull in the necessary FreeBSD
334infrastructure.
335
336The FreeBSD kernel is not a library like the RTEMS kernel.  It is a bunch of
337object files linked together.  If we have a library, then creating the
338executable is simple.  We begin with a start symbol and recursively resolve all
339references.  With a bunch of object files linked together we need a different
340mechanism.  Most object files don't know each other.  Lets say we have a driver
341module.  The rest of the system has no references to this driver module.  The
342driver module needs a way to tell the rest of the system: Hey, kernel I am
343here, please use my services!
344
345This registration of independent components is performed by SYSINIT(9) and
346specializations:
347
348http://www.freebsd.org/cgi/man.cgi?query=SYSINIT
349
350The SYSINIT(9) uses some global data structures that are placed in a certain
351section.  In the linker command file we need this:
352
353[listing]
354----
355.robsdsets : {
356    _bsd__start_set_modmetadata_set = .;
357    *(_bsd_set_modmetadata_set);
358    _bsd__stop_set_modmetadata_set = .;
359    _bsd__start_set_sysctl_set = .;
360    *(_bsd_set_sysctl_set);
361    _bsd__stop_set_sysctl_set = .;
362} > REGION_RODATA AT > REGION_RODATA_LOAD
363
364.rwbsdsets : {
365    _bsd__start_set_sysinit_set = .;
366    *(_bsd_set_sysinit_set);
367    _bsd__stop_set_sysinit_set = .;
368} > REGION_DATA AT > REGION_DATA_LOAD
369----
370
371Here you can see, that these global data structures are collected into
372continuous memory areas.  This memory area can be identified by start and stop
373symbols.  This constructs a table of uniform items.
374
375The low level FreeBSD code calls at some time during the initialization the
376mi_startup() function (machine independent startup).  This function will sort
377the SYSINIT(9) set and call handler functions which perform further
378initialization.  The last step is the scheduler invocation.
379
380The SYSINIT(9) routines are run in mi_startup() which is called by
381rtems_bsd_initialize().
382
383This is also explained in "The Design and Implementation of the FreeBSD
384Operating System" section 14.3 "Kernel Initialization".
385
386In RTEMS we have a library and not a bunch of object files.  Thus we need a way
387to pull-in the desired services out of the libbsd.  Here the
388"rtems-bsd-sysinit.h" comes into play.  The SYSINIT(9) macros have been
389modified and extended for RTEMS in "sys/kernel.h":
390
391[listing]
392----
393#ifndef __rtems__
394#define    C_SYSINIT(uniquifier, subsystem, order, func, ident) \
395    static struct sysinit uniquifier ## _sys_init = { \
396        subsystem, \
397        order, \
398        func, \
399        (ident) \
400    }; \
401    DATA_SET(sysinit_set,uniquifier ## _sys_init)
402#else /* __rtems__ */
403#define    SYSINIT_ENTRY_NAME(uniquifier) \
404    _bsd_ ## uniquifier ## _sys_init
405#define    SYSINIT_REFERENCE_NAME(uniquifier) \
406    _bsd_ ## uniquifier ## _sys_init_ref
407#define    C_SYSINIT(uniquifier, subsystem, order, func, ident) \
408    struct sysinit SYSINIT_ENTRY_NAME(uniquifier) = { \
409        subsystem, \
410        order, \
411        func, \
412        (ident) \
413    }; \
414    DATA_SET(sysinit_set,SYSINIT_ENTRY_NAME(uniquifier))
415#define    SYSINIT_REFERENCE(uniquifier) \
416    extern struct sysinit SYSINIT_ENTRY_NAME(uniquifier); \
417    static struct sysinit const * const \
418    SYSINIT_REFERENCE_NAME(uniquifier) __used \
419    = &SYSINIT_ENTRY_NAME(uniquifier)
420#define    SYSINIT_MODULE_REFERENCE(mod) \
421    SYSINIT_REFERENCE(mod ## module)
422#define    SYSINIT_DRIVER_REFERENCE(driver, bus) \
423    SYSINIT_MODULE_REFERENCE(driver ## _ ## bus)
424#endif /* __rtems__ */
425----
426
427Here you see that the SYSINIT(9) entries are no longer static.  The
428*_REFERENCE() macros will create references to the corresponding modules which
429are later resolved by the linker.  The application has to provide an object
430file with references to all required FreeBSD modules.
431
432The FreeBSD device model is quite elaborated (with follow-ups):
433
434http://www.freebsd.org/cgi/man.cgi?query=driver
435
436The devices form a tree with the Nexus device at a high-level.  This Nexus
437device is architecture specific in FreeBSD.  In RTEMS we have our own Nexus
438device, see "rtems-bsd-nexus.c".  It uses a table to add child devices:
439
440[listing]
441----
442const char *const _bsd_nexus_devices [] = {
443    #ifdef NEED_USB_OHCI
444        "ohci",
445    #endif
446    #ifdef NEED_USB_EHCI
447        "ehci",
448    #endif
449    #ifdef NEED_SDHC
450        "sdhci",
451    #endif
452    NULL
453};
454----
455
456This table must be provided by the application.
457
458=== SYSCTL_NODE Example
459
460During development, we had an undefined reference to
461_bsd_sysctl__net_children that we had trouble tracking down. Thanks to
462Chris Johns, we located it. He explained how to read SYSCTL_NODE
463definitions. This line from freebsd/netinet/in_proto.c is attempting
464to add the "inet" node to the parent node "_net".
465
466[listing]
467----
468SYSCTL_NODE(_net,      PF_INET,         inet,   CTLFLAG_RW, 0,
469        "Internet Family");
470----
471
472Our problem was that we could not find where _bsd_sysctl__net_children
473was defined. Chris suggested that when in doubt compile with -save-temps
474and look at the preprocessed .i files. But he did not need that. He
475explained that this the symbol name _bsd_sysctl__net_children was
476automatically generated by a SYSCTL_NODE as follows:
477
478* _bsd_ - added by RTEMS modifications to SYSCTL_NODE macro
479* sysctl_ - boilerplace added by SYSCTL_NODE macro
480* "" - empty string for parent node
481* net - name of SYSCTL_NODE
482* children - added by SYSCTL macros
483 
484This was all generated by a support macro declaring the node as this:
485
486[listing]
487----
488struct sysctl_oid_list SYSCTL_NODE_CHILDREN(parent, name);
489----
490
491Given this information, we located this SYSCTL_NODE declaration in
492kern/kern_mib.c
493
494[listing]
495----
496SYSCTL_NODE(, CTL_KERN,   kern,   CTLFLAG_RW, 0,
497        "High kernel, proc, limits &c");
498----
499
500== Core FreeBSD APIs and RTEMS Replacements ==
501
502=== SX(9) (Shared/exclusive locks) ===
503
504http://www.freebsd.org/cgi/man.cgi?query=sx
505
506Binary semaphores (this neglects the ability to allow shared access).
507
508=== MUTEX(9) (Mutual exclusion) ===
509
510http://www.freebsd.org/cgi/man.cgi?query=mutex
511
512Binary semaphores (not recursive mutexes are not supported this way).
513
514=== RWLOCK(9) (Reader/writer lock) ===
515
516http://www.freebsd.org/cgi/man.cgi?query=rwlock
517
518POSIX r/w lock.
519
520=== RMLOCK(9) (Reader/writer lock optimized for mostly read access patterns) ===
521
522Note:  This object was implemented as a wrapper for RWLOCK in the rm_lock header file.
523
524http://www.freebsd.org/cgi/man.cgi?query=rmlock
525
526POSIX r/w lock.
527
528=== CONDVAR(9) (Condition variables) ===
529
530http://www.freebsd.org/cgi/man.cgi?query=condvar
531
532POSIX condition variables with modifications (hack).
533
534=== CALLOUT(9) (Timer functions) ===
535
536http://www.freebsd.org/cgi/man.cgi?query=callout
537
538Timer server.
539
540=== TASKQUEUE(9) (Asynchronous task execution) ===
541
542http://www.freebsd.org/cgi/man.cgi?query=taskqueue
543
544TBD.
545
546=== KTHREAD(9), KPROC(9) (Tasks) ===
547
548http://www.freebsd.org/cgi/man.cgi?query=kthread
549
550http://www.freebsd.org/cgi/man.cgi?query=kproc
551
552Tasks.
553
554=== ZONE(9) (Zone allocator) ===
555
556http://www.freebsd.org/cgi/man.cgi?query=zone
557
558TBD.
559
560=== devfs (Device file system) ===
561
562Dummy, IMFS or new implementation (currently dummy).
563
564=== psignal (Signals) ===
565
566TBD.  Seems to be not needed.
567
568=== poll, select ===
569
570TBD.  Seems to be not needed.
571
572=== RMAN(9) (Resource management) ===
573
574http://www.freebsd.org/cgi/man.cgi?query=rman
575
576TBD.  Seems to be not needed.
577
578=== DEVCLASS(9), DEVICE(9), DRIVER(9), MAKE_DEV(9) (Device management) ===
579
580http://www.freebsd.org/cgi/man.cgi?query=devclass
581
582http://www.freebsd.org/cgi/man.cgi?query=device
583
584http://www.freebsd.org/cgi/man.cgi?query=driver
585
586http://www.freebsd.org/cgi/man.cgi?query=make_dev
587
588Use FreeBSD implementation as far as possible.  FreeBSD has a nice API for
589dynamic device handling.  It may be interesting for RTEMS to use this API
590internally in the future.
591
592=== BUS_SPACE(9), BUS_DMA(9) (Bus and DMA access) ===
593
594http://www.freebsd.org/cgi/man.cgi?query=bus_space
595
596http://www.freebsd.org/cgi/man.cgi?query=bus_dma
597
598Likely BSP dependent.  A default implementation for memory mapped linear access
599is easy to provide.  The current heap implementation supports all properties
600demanded by bus_dma (including the boundary constraint).
601
602== RTEMS Replacements by File Description ==
603
604Note:  Files with a status of USB are used by the USB test and have at least
605been partially tested.  If they contain both USB and Nic, then they are used
606by both and MAY contain methods that have not been tested yet.  Files that
607are only used by the Nic test are the most suspect.
608
609[listing]
610----
611rtems-libbsd File:      rtems-bsd-assert.c
612FreeBSD File:           rtems-bsd-config.h redefines BSD_ASSERT.
613Description:            This file contains the support method rtems_bsd_assert_func().
614Status:                 USB, Nic
615
616rtems-libbsd File:      rtems-bsd-autoconf.c
617FreeBSD File:           FreeBSD has BSP specific autoconf.c
618Description:            This file contains configuration methods that are used to setup the system.
619Status:                 USB
620
621rtems-libbsd File:      rtems-bsd-bus-dma.c
622FreeBSD File:           FreeBSD has BSP specific busdma_machdep.c
623Description:           
624Status:                 USB, Nic
625
626rtems-libbsd File:      rtems-bsd-bus-dma-mbuf.c       
627FreeBSD File:           FreeBSD has BSP specific busdma_machdep.c
628Description:           
629Status:                 Nic
630
631rtems-libbsd File:      rtems-bsd-callout.c             
632FreeBSD File:           kern/kern_timeout.c
633Description:           
634Status:                 USB, Nic
635
636rtems-libbsd File:      rtems-bsd-cam.c
637FreeBSD File:           cam/cam_sim.c
638Description:           
639Status:                 USB
640
641rtems-libbsd File:      rtems-bsd-condvar.c             
642FreeBSD File:           kern/kern_condvar.c
643Description:           
644Status:                 USB
645
646rtems-libbsd File:      rtems-bsd-copyinout.c
647FreeBSD File:           bsp specific copyinout.c )
648Description:            Note: The FreeBSD file is split with some methods being in rtems-bsd-support
649Status:                 Nic
650
651rtems-libbsd File:      rtems-bsd-delay.c
652FreeBSD File:           bsp specific file with multiple names
653Description:           
654Status:                 USB, Nic
655
656rtems-libbsd File:      rtems-bsd-descrip.c
657FreeBSD File:           kern/kern_descrip.c
658Description:           
659Status:                 Nic
660
661rtems-libbsd File:      rtems-bsd-generic.c             
662FreeBSD File:           kern/sys_generic.c
663Description:           
664Status:                 Nic
665
666rtems-libbsd File:      rtems-bsd-init.c
667FreeBSD File:           N/A
668Description:           
669Status:                 USB, Nic
670
671rtems-libbsd File:      rtems-bsd-init-with-irq.c
672FreeBSD File:           N/A
673Description:           
674Status:                 USB, Nic
675
676rtems-libbsd File:      rtems-bsd-jail.c
677FreeBSD File:           kern/kern_jail.c
678Description:           
679Status:                 USB, Nic
680
681rtems-libbsd File:      rtems-bsd-lock.c
682FreeBSD File:           kern/subr_lock.c
683Description:           
684Status:                 USB, Nic
685
686rtems-libbsd File:      rtems-bsd-log.c         
687FreeBSD File:           kern/subr_prf.c
688Description:           
689Status:                 Nic
690
691rtems-libbsd File:      rtems-bsd-malloc.c
692FreeBSD File:           kern/kern_malloc.c
693Description:           
694Status:                 USB, Nic
695
696rtems-libbsd File:      rtems-bsd-mutex.c
697FreeBSD File:           kern/kern_mutex.c
698Description:           
699Status:                 USB, Nic
700
701rtems-libbsd File:      rtems-bsd-newproc.c
702FreeBSD File:           N/A
703Description:           
704Status:                 Nic
705
706rtems-libbsd File:      rtems-bsd-nexus.c
707FreeBSD File:           bsp specific nexus.c
708Description:           
709Status:                 USB
710
711rtems-libbsd File:      rtems-bsd-panic.c               
712FreeBSD File:           boot/common/panic.c
713Description:           
714Status:                 USB, Nic
715
716rtems-libbsd File:      rtems-bsd-rwlock.c             
717FreeBSD File:           kern_rwlock.c
718Description:           
719Status:                 USB, Nic
720
721rtems-libbsd File:      rtems-bsd-shell.c               
722FreeBSD File:           N/A
723Description:           
724Status:                 USB
725
726rtems-libbsd File:      rtems-bsd-signal.c             
727FreeBSD File:           kern/kern_sig.c
728Description:           
729Status:                 Nic
730
731rtems-libbsd File:      rtems-bsd-smp.c                 
732FreeBSD File:           N/A
733Description:           
734Status:                 Nic
735
736rtems-libbsd File:      rtems-bsd-support.c             
737FreeBSD File:           bsp specific copyinout.c
738Description:            Note: the FreeBSD file is split with some methods being in rtems-bsd-copyinout.
739Status:                 USB, Nic
740
741rtems-libbsd File:      rtems-bsd-sx.c                 
742FreeBSD File:           kern/kern_sx.c
743Description:            Status: USB, Nic
744
745rtems-libbsd File:      rtems-bsd-synch.c               
746FreeBSD File:           kern/kern_synch.c
747Description:           
748Status:                 USB, Nic
749
750rtems-libbsd File:      rtems-bsd-syscalls.c           
751FreeBSD File:           User API for kern/uipc_syscalls.c
752Description:           
753Status:                 Nic
754
755rtems-libbsd File:      rtems-bsd-sysctlbyname.c       
756FreeBSD File:           User API for sysctlbyname(3)
757Description:           
758Status:
759
760rtems-libbsd File:      rtems-bsd-sysctl.c             
761FreeBSD File:           User API for sysctl(8)
762Description:           
763Status:
764
765rtems-libbsd File:      rtems-bsd-sysctlnametomib.c     
766FreeBSD File:           User API for sysctlnametomib
767Description:           
768Status:
769
770rtems-libbsd File:      rtems-bsd-taskqueue.c           
771FreeBSD File:           kern/subr_taskqueue.c
772Description:           
773Status:                 Nic
774
775rtems-libbsd File:      rtems-bsd-thread.c                     
776FreeBSD File:           kern/kern_kthread.c
777Description:           
778Status:                 USB, Nic
779
780rtems-libbsd File:      rtems-bsd-timeout.c             
781FreeBSD File:           kern/kern_timeout.c
782Description:           
783Status:                 Nic
784
785rtems-libbsd File:      rtems-bsd-timesupport.c         
786FreeBSD File:           kern/kern_clock.c
787Description:           
788Status:                 Nic
789
790rtems-libbsd File:      rtems-bsd-vm_glue.c             
791FreeBSD File:           vm/vm_glue.c
792Description:           
793Status:                 USB, Nic
794----
795
796== Notes by File ==
797
798altq_subr.c - Arbitrary choices were made in this file that RTEMS would
799not support tsc frequency change.  Additionally, the clock frequency
800for machclk_freq is always measured for RTEMS.
801
802conf.h - In order to add make_dev and destroy_dev, variables in the cdev
803structure that were not being used were conditionally compiled out. The
804capability of supporting children did not appear to be needed and was
805not implemented in the rtems version of these routines.
806 
807== NICs Status ==
808
809[listing]
810----
811Driver                  Symbol                          Status
812======                  ======                          ======
813RealTek                 _bsd_re_pcimodule_sys_init      Links
814EtherExpress            _bsd_fxp_pcimodule_sys_init     Links
815DEC tulip               _bsd_dc_pcimodule_sys_init      Links
816Broadcom BCM57xxx       _bsd_bce_pcimodule_sys_init     Links
817Broadcom BCM4401        _bsd_bfe_pcimodule_sys_init     Links
818Broadcom BCM570x        _bsd_bge_pcimodule_sys_init     Needs Symbols (A)
819E1000 IGB               _bsd_igb_pcimodule_sys_init     Links
820E1000 EM                _bsd_em_pcimodule_sys_init      Links
821----
822
823
824Symbols (A)
825         pci_get_vpd_ident
826 
827== Problems to report to FreeBSD ==
828
829The MMAP_NOT_AVAILABLE define is inverted on its usage.  When it is
830defined the mmap method is called. Additionally, it is not used
831thoroughly. It is not used in the unmap portion of the source.
832The file rec_open.c uses the define MMAP_NOT_AVAILABLE to wrap
833the call to mmap and file rec_close.c uses the munmap method.
834
835
836
Note: See TracBrowser for help on using the repository browser.