Didj Enable Networking - Revision history

Jrspruitt: /* Hardware Needed */

2011-07-14T09:17:50Z

‎Hardware Needed

2011-07-12T00:39:36Z

2011-07-12T00:35:23Z

‎Set up TCP/IP

2011-07-09T00:39:03Z

‎Configure PTY device

2011-07-08T21:50:46Z

‎Building Kernel

2011-07-08T21:24:21Z

‎Kernel Configuration

2011-07-08T21:23:43Z

‎Kernel Configuration

2011-07-08T21:01:09Z

‎Mount /dev/pts

2011-07-08T21:00:34Z

‎Install and Configure

2011-07-08T20:59:51Z

@@ Line 16: / Line 16: @@
 == Hardware Needed ==
 [[LeapFrog_Pollux_Platform:_Console_Access| Console Access]]
 == Build Module ==

@@ Line 143: / Line 143: @@
   # adduser didj
   (this will prompt you for a password, can leave blank by hitting return twice, and ignoring the warnings.)
 [[Category:Didj]]
 [[Category:LeapFrog_Pollux_Platform]]

@@ Line 130: / Line 130: @@
 ==== Set up TCP/IP ====
 With the USB cable still connected to your host, configure an IP address (make sure this is a different subnet from your existing LAN).
-'' On Didj ''
+[[LeapFrog_Pollux_Platform:_Networking| Networking Setup]]
- # ifconfig usb0 10.0.0.2 netmask 255.255.255.0
-−
-'' On Host ''
- $ sudo ifconfig usb0 10.0.0.1 netmask 255.255.255.0
-−
-At this point you should be able to ping from one machine to the other.
-−
-'' On Host ''
- $ ping 10.0.0.2
-−
-'' On Didj ''
- # ping 10.0.0.1
-−
 ==== Add User ====

@@ Line 88: / Line 88: @@
 '' On Didj ''
   # mount -t devpts none /dev/pts
 ==== Installing g_ether.ko ====

@@ Line 66: / Line 66: @@
 ==== Building Kernel ====
-[[LeapFrog_Pollux_Platform:_Build_Environment| Set up your Build Environment]] and from inside the kernel directory linux-2.6-lf1000/
+[[LeapFrog_Pollux_Platform:_Build_Environment| Set up your Build Environment]] and from inside the kernel directory linux-2.6-lf1000/ run.
   $ ./install.sh
@@ Line 72: / Line 72: @@
 [[Didj_Boot_From_UART]]
 == Install and Configure ==

@@ Line 33: / Line 33: @@
   $ make lf1000_ff_eth_defconfig
-You config file is now loaded, and you are ready to proceed.
+Your config file is now loaded, and you are ready to proceed.
 ''' Using make menuconfig '''

@@ Line 23: / Line 23: @@
 ==== Kernel Configuration ====
-Out of the box, neither networking support nor the PTY devices used by busybox/telnetd are enabled in the stock Didj kernel
+Out of the box, neither networking support nor the PTY devices used by busybox/telnetd are enabled in the stock Didj kernel. There are two ways to enable this. You can manually configure the kernel with make menuconfig, or use a configuration included in the Didj sources, lf1000_tt_eth_defconfig.
-To add this support, make a custom kernel.
+''' Using alternate included config file '''
-'''Making a custom kernel for networking and PTY support'''
+More information on configuring [[LeapFrog_Pollux_Platform:_Kernel_Configuration#Using_Preexisting_Config| using preexisting config]]
-Next you need to configure your kernel using [[LeapFrog_Pollux_Platform:_Kernel_Configuration#Make_Menuconfig| make menuconfig]]
+'' On Host ''
   cd SOURCE_CODE/linux-2.6.20-lf1000
   $ make menuconfig
@@ Line 54: / Line 63: @@
 # Exit all the way out of the menu application, making sure to save the changes when prompted.
 ==== Building Kernel ====

@@ Line 67: / Line 67: @@
 These steps, except for creating the device, will need to be repeated on each boot. If you'd like to make the USB device an Ethernet device permanently, you'll want to look into modifying the start up scripts.
-==== Mount /dev/pts ====
+==== Configure PTY device ====
-Configuring PTY devices – Programs like telnetd and dropbear require these devices to be configured in order to run.
+Programs like telnetd and dropbear require these devices to be configured in order to run.
 If not already created, create the node and directory for PTS
@@ Line 78: / Line 78: @@
 '' On Didj ''
   # mount -t devpts none /dev/pts
-−
 ==== Installing g_ether.ko ====

@@ Line 65: / Line 65: @@
 == Install and Configure ==
 ==== Installing g_ether.ko ====
@@ Line 132: / Line 148: @@
 == Networking Applications ==
 ==== Set up telnetd ====
 Run Telnetd