source: rtems-libbsd/libbsd.txt @ c14bb23

4.115-freebsd-12freebsd-9.3
Last change on this file since c14bb23 was c14bb23, checked in by Sebastian Huber <sebastian.huber@…>, on Oct 21, 2013 at 12:12:20 PM

IFCONFIG(8): Disable IEEE80211 support

This module depends on a XML parser and mmap().

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