Diff for /wikisrc/ports/evbarm/raspberry_pi.mdwn between versions 1.58 and 1.59

version 1.58, 2017/10/21 23:50:25 version 1.59, 2017/10/21 23:52:26
Line 46  Initial, limited, Raspberry Pi support w Line 46  Initial, limited, Raspberry Pi support w
   
 Note that one can also use code for earlier models on later models.  Note that one can also use code for earlier models on later models.
   
   - Raspberry Pi 1 uses "earmv6hf".   - Raspberry Pi 1 uses "earmv6hf".
   - Raspberry Pi 2 uses "earmv7hf".   - Raspberry Pi 2 uses "earmv7hf".
   - Raspberry Pi 3 uses "earmv7hf".  (NetBSD does not yet have 64-bit support.)   - Raspberry Pi 3 uses "earmv7hf".  (NetBSD does not yet have 64-bit support.)
   
 # Installation  # Installation
   
Line 69  an FFS partition for NetBSD. Line 69  an FFS partition for NetBSD.
   
 Getting sources and building a release with build.sh is not special for evbarm.  Getting sources and building a release with build.sh is not special for evbarm.
 Pick a CPU type alias and pass it to build.sh with -m.  Examples:  Pick a CPU type alias and pass it to build.sh with -m.  Examples:
     - ./build.sh -m earmv6hf -u release   - ./build.sh -m earmv6hf -u release
     - ./build.sh -m evbarm -a earmv6hf -u release   - ./build.sh -m evbarm -a earmv6hf -u release
     - ./build.sh -m evbarm -a earmv7hf -u release   - ./build.sh -m evbarm -a earmv7hf -u release
   
 ### NetBSD FTP servers  ### NetBSD FTP servers
   
 NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.  NetBSD provides nightly builds on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).  These are equivalent to building yourself.
   
     - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.   - The 'evbarm-earmv6hf/binary/gzimg/' directory contains an rpi.img file that can be used as a single image for both boards.
     - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2.   - The 'evbarm-earmv7hf/binary/gzimg/' directory contains an armv7.img file that is optimized for Raspberry Pi 2.
     - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg)       - The stable build directory will be under netbsd-7/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-7/201710201440Z/evbarm-earmv6hf/binary/gzimg)    
     - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)   - The not-yet-released stable build directory will be under netbsd-8/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/netbsd-8/201710211010Z/evbarm-earmv6hf/binary/gzimg/)
     - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)   - The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example, http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201710202210Z/evbarm-earmv7hf/binary/gzimg/)
   
 ## Installing to uSD  ## Installing to uSD
   
 Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for examples  Once you have rpi.img.gz, put it on a uSD card using gunzip and dd, for examples
   
    - dd if=rpi.img of=/dev/disk1   - dd if=rpi.img of=/dev/disk1
   
 ### Serial Console  ### Serial Console
   
 By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, first mount the FAT32 partition and then  By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, first mount the FAT32 partition and then
 edit cmdline.txt and remove '"console=fb"'.  edit cmdline.txt and remove '"console=fb"'.
   
    - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".      - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
   
       In Kermit, the command is "set flow none".        In Kermit, the command is "set flow none".
   

Removed from v.1.58  
changed lines
  Added in v.1.59


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb