source: rtems-libbsd/libbsd.txt @ 549488b

4.115-freebsd-12freebsd-9.3
Last change on this file since 549488b was 549488b, checked in by Sebastian Huber <sebastian.huber@…>, on Oct 10, 2013 at 12:45:09 PM

Disable alternative routing tables

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