source: rtems-libbsd/libbsd.txt @ 241fc32

4.115-freebsd-12freebsd-9.3
Last change on this file since 241fc32 was 241fc32, checked in by Sebastian Huber <sebastian.huber@…>, on Nov 4, 2013 at 8:12:59 AM

Use a local MSIZE of 256

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