docs: net: convert two README files to ReST format

There are two README files there with doesn't have a .txt
extension nor are at ReST format.

In order to help with the docs conversion to ReST, rename those
and manually convert them to ReST format.

As there are lot more to be done for networking to be part of
the documentation body, for now mark those two files with
:orphan:, in order to supress a build warning.

Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Mauro Carvalho Chehab 2019-07-26 09:51:34 -03:00 committed by Jonathan Corbet
parent 47359e5734
commit e15d5a53ea
3 changed files with 83 additions and 39 deletions

View File

@ -1,18 +1,31 @@
Copyright (C) ST-Ericsson AB 2010 :orphan:
Author: Sjur Brendeland/ sjur.brandeland@stericsson.com
License terms: GNU General Public License (GPL) version 2
---------------------------------------------------------
=== Start === .. SPDX-License-Identifier: GPL-2.0
If you have compiled CAIF for modules do: .. include:: <isonum.txt>
$modprobe crc_ccitt
$modprobe caif
$modprobe caif_socket
$modprobe chnl_net
=== Preparing the setup with a STE modem === ================
Using Linux CAIF
================
:Copyright: |copy| ST-Ericsson AB 2010
:Author: Sjur Brendeland/ sjur.brandeland@stericsson.com
Start
=====
If you have compiled CAIF for modules do::
$modprobe crc_ccitt
$modprobe caif
$modprobe caif_socket
$modprobe chnl_net
Preparing the setup with a STE modem
====================================
If you are working on integration of CAIF you should make sure If you are working on integration of CAIF you should make sure
that the kernel is built with module support. that the kernel is built with module support.
@ -32,24 +45,30 @@ module parameter "ser_use_stx".
Normally Frame Checksum is always used on UART, but this is also provided as a Normally Frame Checksum is always used on UART, but this is also provided as a
module parameter "ser_use_fcs". module parameter "ser_use_fcs".
$ modprobe caif_serial ser_ttyname=/dev/ttyS0 ser_use_stx=yes ::
$ ifconfig caif_ttyS0 up
PLEASE NOTE: There is a limitation in Android shell. $ modprobe caif_serial ser_ttyname=/dev/ttyS0 ser_use_stx=yes
$ ifconfig caif_ttyS0 up
PLEASE NOTE:
There is a limitation in Android shell.
It only accepts one argument to insmod/modprobe! It only accepts one argument to insmod/modprobe!
=== Trouble shooting === Trouble shooting
================
There are debugfs parameters provided for serial communication. There are debugfs parameters provided for serial communication.
/sys/kernel/debug/caif_serial/<tty-name>/ /sys/kernel/debug/caif_serial/<tty-name>/
* ser_state: Prints the bit-mask status where * ser_state: Prints the bit-mask status where
- 0x02 means SENDING, this is a transient state. - 0x02 means SENDING, this is a transient state.
- 0x10 means FLOW_OFF_SENT, i.e. the previous frame has not been sent - 0x10 means FLOW_OFF_SENT, i.e. the previous frame has not been sent
and is blocking further send operation. Flow OFF has been propagated and is blocking further send operation. Flow OFF has been propagated
to all CAIF Channels using this TTY. to all CAIF Channels using this TTY.
* tty_status: Prints the bit-mask tty status information * tty_status: Prints the bit-mask tty status information
- 0x01 - tty->warned is on. - 0x01 - tty->warned is on.
- 0x02 - tty->low_latency is on. - 0x02 - tty->low_latency is on.
- 0x04 - tty->packed is on. - 0x04 - tty->packed is on.
@ -58,13 +77,17 @@ There are debugfs parameters provided for serial communication.
- 0x20 - tty->stopped is on. - 0x20 - tty->stopped is on.
* last_tx_msg: Binary blob Prints the last transmitted frame. * last_tx_msg: Binary blob Prints the last transmitted frame.
This can be printed with
$od --format=x1 /sys/kernel/debug/caif_serial/<tty>/last_rx_msg.
The first two tx messages sent look like this. Note: The initial
byte 02 is start of frame extension (STX) used for re-syncing
upon errors.
- Enumeration: This can be printed with::
$od --format=x1 /sys/kernel/debug/caif_serial/<tty>/last_rx_msg.
The first two tx messages sent look like this. Note: The initial
byte 02 is start of frame extension (STX) used for re-syncing
upon errors.
- Enumeration::
0000000 02 05 00 00 03 01 d2 02 0000000 02 05 00 00 03 01 d2 02
| | | | | | | | | | | |
STX(1) | | | | STX(1) | | | |
@ -73,7 +96,9 @@ There are debugfs parameters provided for serial communication.
Command:Enumeration(1) Command:Enumeration(1)
Link-ID(1) Link-ID(1)
Checksum(2) Checksum(2)
- Channel Setup:
- Channel Setup::
0000000 02 07 00 00 00 21 a1 00 48 df 0000000 02 07 00 00 00 21 a1 00 48 df
| | | | | | | | | | | | | | | |
STX(1) | | | | | | STX(1) | | | | | |
@ -86,13 +111,18 @@ There are debugfs parameters provided for serial communication.
Checksum(2) Checksum(2)
* last_rx_msg: Prints the last transmitted frame. * last_rx_msg: Prints the last transmitted frame.
The RX messages for LinkSetup look almost identical but they have the
bit 0x20 set in the command bit, and Channel Setup has added one byte The RX messages for LinkSetup look almost identical but they have the
before Checksum containing Channel ID. bit 0x20 set in the command bit, and Channel Setup has added one byte
NOTE: Several CAIF Messages might be concatenated. The maximum debug before Checksum containing Channel ID.
NOTE:
Several CAIF Messages might be concatenated. The maximum debug
buffer size is 128 bytes. buffer size is 128 bytes.
== Error Scenarios: Error Scenarios
===============
- last_tx_msg contains channel setup message and last_rx_msg is empty -> - last_tx_msg contains channel setup message and last_rx_msg is empty ->
The host seems to be able to send over the UART, at least the CAIF ldisc get The host seems to be able to send over the UART, at least the CAIF ldisc get
notified that sending is completed. notified that sending is completed.
@ -103,7 +133,9 @@ There are debugfs parameters provided for serial communication.
- if /sys/kernel/debug/caif_serial/<tty>/tty_status is non-zero there - if /sys/kernel/debug/caif_serial/<tty>/tty_status is non-zero there
might be problems transmitting over UART. might be problems transmitting over UART.
E.g. host and modem wiring is not correct you will typically see E.g. host and modem wiring is not correct you will typically see
tty_status = 0x10 (hw_stopped) and ser_state = 0x10 (FLOW_OFF_SENT). tty_status = 0x10 (hw_stopped) and ser_state = 0x10 (FLOW_OFF_SENT).
You will probably see the enumeration message in last_tx_message You will probably see the enumeration message in last_tx_message
and empty last_rx_message. and empty last_rx_message.

View File

@ -1,5 +1,13 @@
:orphan:
.. SPDX-License-Identifier: GPL-2.0
.. include:: <isonum.txt>
===================================================================
mac80211_hwsim - software simulator of 802.11 radio(s) for mac80211 mac80211_hwsim - software simulator of 802.11 radio(s) for mac80211
Copyright (c) 2008, Jouni Malinen <j@w1.fi> ===================================================================
:Copyright: |copy| 2008, Jouni Malinen <j@w1.fi>
This program is free software; you can redistribute it and/or modify This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License version 2 as it under the terms of the GNU General Public License version 2 as
@ -7,6 +15,7 @@ published by the Free Software Foundation.
Introduction Introduction
============
mac80211_hwsim is a Linux kernel module that can be used to simulate mac80211_hwsim is a Linux kernel module that can be used to simulate
arbitrary number of IEEE 802.11 radios for mac80211. It can be used to arbitrary number of IEEE 802.11 radios for mac80211. It can be used to
@ -43,6 +52,7 @@ regardless of channel.
Simple example Simple example
==============
This example shows how to use mac80211_hwsim to simulate two radios: This example shows how to use mac80211_hwsim to simulate two radios:
one to act as an access point and the other as a station that one to act as an access point and the other as a station that
@ -50,17 +60,19 @@ associates with the AP. hostapd and wpa_supplicant are used to take
care of WPA2-PSK authentication. In addition, hostapd is also care of WPA2-PSK authentication. In addition, hostapd is also
processing access point side of association. processing access point side of association.
::
# Build mac80211_hwsim as part of kernel configuration
# Load the module # Build mac80211_hwsim as part of kernel configuration
modprobe mac80211_hwsim
# Run hostapd (AP) for wlan0 # Load the module
hostapd hostapd.conf modprobe mac80211_hwsim
# Run wpa_supplicant (station) for wlan1 # Run hostapd (AP) for wlan0
wpa_supplicant -Dnl80211 -iwlan1 -c wpa_supplicant.conf hostapd hostapd.conf
# Run wpa_supplicant (station) for wlan1
wpa_supplicant -Dnl80211 -iwlan1 -c wpa_supplicant.conf
More test cases are available in hostap.git: More test cases are available in hostap.git:

View File

@ -9578,7 +9578,7 @@ F: Documentation/networking/mac80211-injection.txt
F: include/net/mac80211.h F: include/net/mac80211.h
F: net/mac80211/ F: net/mac80211/
F: drivers/net/wireless/mac80211_hwsim.[ch] F: drivers/net/wireless/mac80211_hwsim.[ch]
F: Documentation/networking/mac80211_hwsim/README F: Documentation/networking/mac80211_hwsim/mac80211_hwsim.rst
MAILBOX API MAILBOX API
M: Jassi Brar <jassisinghbrar@gmail.com> M: Jassi Brar <jassisinghbrar@gmail.com>