am335x system upgrade kernel ec20 simcom7600ce

1      Scope of Document

This document describes 4G hardware design, support quectel ec20 4G module/ Simcom 7600 CE 4G module

2      Requiremen

2.1     Function Requirement

support ec20 qmi driver/ simcom 7600 ce ndis driver

2.2     Performance Requirement

NA

3      Hardware Overview

 

                  Figure 1 4g interface block diagram

4      Functional Description

4.1     Functional Block Diagram

PCIE-USB connect to 4G module. Port4 connect usb hub, usb hub connect to CPU usb port0

                    

4.2      USB-CDC

4.2.1 Overview QMI

              Qualcomm MSM Interface(QMI) is a messaging format used to communicate

       between software components in the modem and other peripheral subsystems.

       This document proposes an architecture to introduce the QMI messaging

       into the kernel. This document proposes introducing a QMI encode/decode

       library to enable QMI message marshaling and an interface library to enable

       sending and receiving QMI messages through MSM IPC Router.

 

https://android.googlesource.com/kernel/msm/+/android-7.1.0_r0.2/Documentation/arm/msm/msm_qmi.txt

4.2.2 Overview NDIS

 

It was jointly developed by Microsoft and 3Com Corporation and is mostly used in Microsoft Windows. However, the open-source NDISwrapper and Project Evil driver wrapper projects allow many NDIS-compliant NICs to be used with Linux, FreeBSD and NetBSD. magnussoft ZETA, a derivative of BeOS, supports a number of NDIS drivers.

 

The NDIS forms the logical link control (LLC) sublayer, which is the upper sublayer of the OSI data link layer (layer 2). Therefore, the NDIS acts as the interface between the media access control (MAC) sublayer, which is the lower sublayer of the data link layer, and the network layer (layer 3).

 

The NDIS is a library of functions often referred to as a "wrapper" that hides the underlying complexity of the NIC hardware and serves as a standard interface for level 3 network protocol drivers and hardware level MAC drivers. Another common LLC is the Open Data-Link Interface (ODI).

 

The NDIS versions supported by various Windows versions are as follows:

 

NDIS 2.0: MS-DOS, Windows for Workgroups 3.1, OS/2

NDIS 3.0: Windows for Workgroups 3.11

NDIS 3.1: Windows 95

NDIS 4.0: Windows 95 OSR2, NT 4.0, Windows CE 3.0

NDIS 5.0: Windows 98, 98 SE, Me, 2000

NDIS 5.1: Windows XP, Server 2003, Windows CE 4.x, 5.0, 6.0[1]

NDIS 5.2: Windows Server 2003 SP2

NDIS 6.0: Windows Vista

NDIS 6.1: Windows Vista SP1, Server 2008, Windows Embedded Compact 7,[2] Windows Embedded Compact 2013

NDIS 6.20: Windows 7, Server 2008 R2

NDIS 6.30: Windows 8, Windows Server 2012

NDIS 6.40: Windows 8.1, Windows Server 2012 R2

NDIS 6.50: Windows 10, version 1507[3]

NDIS 6.60: Windows Server 2016 and Windows 10, version 1607[3]

NDIS 6.70: Windows 10, version 1703[3]

NDIS 6.80: Windows 10, version 1709[3]

NDIS 6.81: Windows 10, version 1803[3]

NDIS 6.82: Windows 10, version 1809[3]

The traffic accepted by the NIC is controlled by an NDIS miniport Driver while various protocols, such as TCP/IP, are implemented by NDIS Protocol Drivers. A single miniport may be associated with one or more protocols. This means that traffic coming into the miniport may be received in parallel by several protocol drivers. For example, Winpcap adds a second protocol driver on the selected miniport in order to capture incoming packets. Furthermore, it is possible to simulate several virtual NICs by implementing virtual miniport drivers that send and receive traffic from a single physical NIC. One example of virtual miniport driver usage is to add virtual NICs, each with a different Virtual LAN. Because implementations cannot assume that other drivers received the same buffers, one must treat the incoming buffers as read only and a driver that changes the packet content must allocate its own buffers.

 

A miniport is a type of hardware driver, part of the Windows Driver Model. These are USB, Audio, SCSI and network card adapters. They should usually be source and binary compatible between Windows 98 and Windows 2000 and are hardware specific but control access to the hardware through a specific bus class driver. [4]

 

Another driver type is NDIS Intermediate Driver. Intermediate drivers sit in-between the MAC and IP layers and can control all traffic being accepted by the NIC. In practice, intermediate drivers implement both miniport and protocol interfaces. The miniport driver and protocol driver actually communicate with the corresponding miniport and protocol interfaces that reside in the intermediate driver. This design enables adding several chained intermediate drivers between the miniport and protocol drivers. Therefore, driver vendors cannot assume that the interface that they send traffic to is implemented by the last driver in the chain. In order to write applications using NDIS one can use samples that accompany Microsoft's Windows Driver Kit (WDK). The "PassThru" sample is a good starting point for intermediate drivers as it implements all the necessary details required in this driver type, but just passes the traffic through to the next driver in the chain.

 

https://en.wikipedia.org/wiki/Network_Driver_Interface_Specification

5      Porting

5.1     Uboot porting

NA

5.2     Kernel porting

 for ec20

Index: trunk/linux-4.14.40/drivers/net/usb/qmi_wwan.c
================================================================