source: rtems-libbsd/libbsd.txt @ 3e29388

4.115-freebsd-12freebsd-9.3
Last change on this file since 3e29388 was 3e29388, checked in by Sebastian Huber <sebastian.huber@…>, on Oct 25, 2013 at 1:09:17 PM

ZONE(9): Add and use red-black tree chunk alloc

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