source: rtems-libbsd/libbsd.txt @ c90c212

4.115-freebsd-12freebsd-9.3
Last change on this file since c90c212 was c90c212, checked in by Kevin Polulak <kpolulak@…>, on Jul 11, 2012 at 6:11:04 PM

Clarified information in libbsd.txt.

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