Changeset c90c212 in rtems-libbsd


Ignore:
Timestamp:
Jul 11, 2012, 6:11:04 PM (7 years ago)
Author:
Kevin Polulak <kpolulak@…>
Branches:
4.11, c1e05b9ea378b2971e3d7704779112b4bc4296da, freebsd-9.3, 4a77611a223ea883fb548679b516d326a020d447
Children:
1b13f69
Parents:
9fc8b41
git-author:
Kevin Polulak <kpolulak@…> (07/11/12 18:11:04)
git-committer:
Jennifer Averett <jennifer.averett@…> (07/11/12 18:11:04)
Message:

Clarified information in libbsd.txt.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • libbsd.txt

    r9fc8b41 rc90c212  
    144144be merged upstream into our master FreeBSD svn checkout.
    145145
    146 The FreeBSD sources managed in RTEMS libbsd git repository (e.g. contrib
     146The FreeBSD sources managed in the rtems-libbsd git repository (e.g. contrib
    147147and freebsd directories) contain the "managed" version of the
    148148FreeBSD source.  The FreeBSD SVN source is the "master" version. The
    149149freebsd-to-rtems.py script is used to transfer files between the two
    150 trees. In general terms, if you have modified FreeBSD in the RTEMS libbsd
    151 tree, you want to run the script in "revert" or "reverse" mode to move
    152 the source back so you can run an "svn diff" against the upstream FreeBSD
    153 source. If you want to transfer source from the FreeBSD SVN checkout to
    154 the RTEMS libbsd tree, then you want to run the script in "forward" or
    155 default mode.
    156 
    157 === Building RTEMS libbsd source
     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
    158159
    159160You need to configure RTEMS for the desired BSP and install it. The
     
    188189----
    189190
    190 The above installs the RTEMS libbsd kit into a separate place from
    191 RTEMS and the BSP. The RTEMS libbsd tests are built against an installed
    192 image of the RTEMS libbsd. By keeping it in a separate installation point
     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
    193194from RTEMS itself, this makes it easier to remove a libbsd installation
    194195and have a clean test point.
     
    217218* libbsd.txt - Documentation in Asciidoc
    218219
    219 == Moving Code Between FreeBSD SVN and RTEMS libbsd
     220== Moving Code Between FreeBSD SVN and rtems-libbsd
    220221
    221222The script freebsd-to-rtems.py is used to copy code from FreeBSD to the
    222 RTEMS libbsd tree and to reverse this process. This script attempts to
     223rtems-libbsd tree and to reverse this process. This script attempts to
    223224automate this process as much as possible and performs some transformations
    224225on the FreeBSD code. Its command line arguments are shown below:
     
    239240
    240241In its default mode of operation, freebsd-to-rtems.py is used to copy code
    241 from FreeBSD to the RTEMS libbsd tree and perform transformations.  In forward
     242from FreeBSD to the rtems-libbsd tree and perform transformations.  In forward
    242243mode, the script may be requested to just generate the Makefile.
    243244
     
    274275direction.
    275276
    276 == Initialization of RTEMS libbsd
    277 
    278 The initialization of the RTEMS libbsd is based on the FreeBSD SYSINIT(9)
     277== Initialization of rtems-libbsd
     278
     279The initialization of the rtems-libbsd is based on the FreeBSD SYSINIT(9)
    279280infrastructure.  The key to initializing a system is to ensure that the desired
    280281device drivers are explicitly pulled into the linked application.  This plus
Note: See TracChangeset for help on using the changeset viewer.