From: Marcel Holtmann <marcel@holtmann.org>
Date: Wed, 30 Mar 2011 14:54:44 +0000 (+0200)
Subject: doc: Reformat the dialup architecture layout a bit
X-Git-Tag: 0.46~92
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=6ff8e8b61b13ccdf3647b0bd19a8934c0a1f4827;p=platform%2Fupstream%2Fofono.git

doc: Reformat the dialup architecture layout a bit
---

diff --git a/doc/dialup-overview.txt b/doc/dialup-overview.txt
index f407560..be423ee 100644
--- a/doc/dialup-overview.txt
+++ b/doc/dialup-overview.txt
@@ -1,15 +1,17 @@
 DialUp Networking diagram
 =========================
 
-This diagram explains how oFono and ConnMan are interacting to
-handle a data call from a DUN client.
+This diagram explains how oFono and ConnMan are interacting to handle a data
+call from a DUN client.
+
 1) GAtServer receive ATD*99#.
 2) The GAtPPP server is setup.
 3) oFono through GAtPPP notify ConnMan that he needs a TUN/TAP interface.
 4) oFono is notified that TUN/TAP interface is created and can start exchanging
-PPP packets with DUN client. Those PPP packets are converted into IP stream
-and transmitted to/received from TUN/TAP interface.
-5) ConnMan is selecting which interface to send IP packets (WiFi, 3G, ethX, ...).
+   PPP packets with DUN client. Those PPP packets are converted into IP stream
+   and transmitted to/received from TUN/TAP interface.
+5) ConnMan is selecting which interface to send IP packets (WiFi, 3G, ...).
+
 
 *----------------*            *----------------*
 |                |  ATD*99#   |                |
@@ -44,4 +46,3 @@ and transmitted to/received from TUN/TAP interface.
             |  WiFi       |       |   Modem     |      |    EthX     |
             |             |       |             |      |             |
             *-------------*       *-------------*      *-------------*
-