source: rtems-libbsd/libbsd.txt @ 1bc2756

4.115-freebsd-12freebsd-9.3
Last change on this file since 1bc2756 was 1bc2756, checked in by Sebastian Huber <sebastian.huber@…>, on Oct 24, 2013 at 8:51:38 AM

Add TODO item

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