source: rtems-libbsd/libbsd.txt @ e8b7066

4.115-freebsd-12freebsd-9.3
Last change on this file since e8b7066 was e8b7066, checked in by Sebastian Huber <sebastian.huber@…>, on Oct 1, 2013 at 2:23:35 PM

Add FreeBSD sources as a submodule

The current version corresponds to SVN r255967 of:

http://svn.freebsd.org/base/releng/8.2

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