linuxpcie驅動

① linux下pcie驅動開發，該看些什麼資料

linux下pcie驅動開發大概可以分為4個階段，水平從低到高：
從安裝使用=>linux常用命令=>linux系統編程=>內核開發閱讀內核源碼
系統編程推薦《高級unix環境編程》；
還有《unix網路編程》；
內核開發閱讀內核源碼階段，從寫驅動入手逐漸深入linux內核開發
參考書如下：
1.《linux
device
drivers》
2.《linux
kernel
development》
3.《understading
the
linux
kernel》
4.《linux源碼情景分析》
然後還需要看資料理解elf文件格式，連接器和載入器，cmu的一本教材中文名為《深入理解計算機系統》比較好。

② 求教高手，LINUX 系統下PCIE 驅動移植

這個移植還可以教，驅動開發是不可能的，底層的東西得自己找資料，自己鑽研。應用還好搞，看看QT這方面的書。

③ linux下面pci設備驅動和pcie設備驅動的區別

PCI 設備上有三種地址空間： （1）PCI的I/O空間 （2）PCI的存儲空間 （3）PCI的配置空間。 CPU可以訪問PCI設備上的所有地址空間，其中I/O空間和存儲空間提供給設備驅動程序使用，而配置空間則由Linux內核中的PCI初始化代碼使用。內核在啟動時負...

④ linux下pcie設備卡驅動問題

lspci就可以看到了

⑤ 裝完linux系統重啟不停地提示「pciehp.....」，怎麼解決

未安裝成功，需要重裝。

⑥ 為啥PCIe卡被拔掉之後，lspci還能顯示其被拔掉前的信息呢

更正一點，呵呵，我們不是直接將PCIe卡從插座上拔掉，是關掉了PCIe卡上面的電源開關，從而達到拔掉卡的效果。不知道這種方式和直接拔掉卡效果是否一樣。另外，驅動是直接用的linux自帶的PCIe驅動。我自己感覺/sys/和/proc裡面的PCIe設備信息是系統在枚舉PCIe設備的時候生成的，所以即使將PCIe卡去除，系統也會保留這些信息，除非通過某種方式（比如系統重啟）讓系統重新枚舉PCIe設備。

⑦ LINUX系統下為什麼PCIE網卡可用而PCI網卡不可用

和什麼網卡沒關系，正好你的Linux版本有PCIE網卡的驅動，你PCI網卡的驅動沒有！~查下PCI網卡的驅動，經驅動程序安裝上就可以了！~

⑧ linux如何打開pcie設備

跟pc上的pcie一樣的一個匯流排而已啊，你有pcie設備的話插上你的板子上的pcie 插槽，就可以用了。當然你的系統中還得有pcie設備的驅動支持才行。

⑨ 安裝linux 出現realtek pcie gbe family controller ser

Realtek PCIE GBE family controller這個是你的網卡驅動~~建議你重新安裝一下網卡驅動。
安裝Realtek驅動時建議不要使用最新版的驅動，而是選擇穩定版本~

⑩ 在LINUX中如何載入驅動網卡

直接找好對應的驅動 一般都會有readme 或者install 之類的說明文檔來告訴你如何去安裝這個網卡驅動的

Linux* Base Driver for the Atheros(R) AR8121/AR8113 PCI-E Ethernet Adapter
==========================================================================

Contents
========

- In This Release
- Building and Installation
- Command Line Parameters
- Additional Configurations
- Known Issues
- Support

In This Release
===============

This file describes the Linux* Base Driver for the Atheros(R) AR8121/AR8113 PCI-E
Ethernet Adapter, version 1.0.0.5 This driver supports the 2.4.x and 2.6.x kernels.

This driver is only supported as a loadable mole at this time. Atheros is not
supplying patches against the kernel source to allow for static linking of
the driver. For questions related to hardware requirements, refer to the
documentation supplied with your Atheros(R) adapter. All hardware
requirements listed apply to use with Linux.

Building and Installation
=========================

To build a binary RPM* package of this driver, run 'rpmbuild -tb
<filename.tar.gz>'. Replace <filename.tar.gz> with the specific filename of
the driver.

NOTE: For the build to work properly, the currently running kernel MUST match
the version and configuration of the installed kernel sources. If you
have just recompiled the kernel reboot the system now.

RPM functionality has only been tested in Red Hat distributions.

1. Move the base driver tar file to the directory of your choice. For example,
use /home/username/arl1e or /usr/local/src/arl1e.

2. Untar/unzip archive:

tar zxf arl1e-x.x.x.x.tar.gz

3. Change to the driver src directory:

cd arl1e-x.x.x.x/src/

4. Compile the driver mole:

make install

The binary will be installed as:

/lib/moles/<KERNEL VERSION>/kernel/drivers/net/arl1e.[k]o

The install locations listed above are the default locations. They might
not be correct for certain Linux distributions. For more information,
see the ldistrib.txt file included in the driver tar.

5. Install the mole:

insmod arl1e <parameter>=<value>

6. Assign an IP address to the interface by entering the following, where
x is the interface number:

ifconfig ethx <IP_address>

7. Verify that the interface works. Enter the following, where <IP_address>
is the IP address for another machine on the same subnet as the interface
that is being tested:

ping <IP_address>

Command Line Parameters
=======================

If the driver is built as a mole, the following optional parameters are
used by entering them on the command line with the modprobe or insmod command
using this syntax:

modprobe arl1e [<option>=<VAL1>,<VAL2>,...]

insmod arl1e [<option>=<VAL1>,<VAL2>,...]

For example, with two L001 PCIE adapters, entering:

insmod arl1e TxMemSize=80,128
loads the arl1e driver with 8KB TX memory for the first adapter and 10KB TX memory
for the second adapter.

The default value for each parameter is generally the recommended setting,
unless otherwise noted.

NOTES: A descriptor describes a data buffer and attributes related to the
data buffer. This information is accessed by the hardware.

media_type
Valid Range: 0-4
0 - auto-negotiate at all supported speeds
1 - only link at 1000Mbps Full Duplex
2 - only link at 100Mbps Full Duplex
3 - only link at 100Mbps Half Duplex
4 - only link at 10Mbps Full Duplex
5 - only link at 10Mbps Half Duplex
Default Value: 0
media_type forces the line speed/plex to the specified value in
megabits per second(Mbps). If this parameter is not specified or is set
to 0 and the link partner is set to auto-negotiate, the board will
auto-detect the correct speed.

int_mod_timer
Valid Range: 50-65000
Default Value: 100
This value represents the minmum interval between interrupts controller
generated.

RxMemBlock
Valid Range: 16-512
Default Value: 64
This value is the number of receice memory block allocated by the driver.
Increasing this value allows the driver to buffer more incoming packets.
Each memory block is 1536 bytes.

NOTE: Depending on the available system resources, the request for a
higher number of receive descriptors may be denied. In this case,
use a lower number.

TxMemSize
Valid Range: 4-64
Default Value: 8
This value is the number KB of transmit memory allocated by the driver.
Increasing this value allows the driver to queue more transmits.

NOTE: Depending on the available system resources, the request for a
higher number of transmit descriptors may be denied. In this case,
use a lower number.

FlashVendor
Valid Range: 0-2
Default Value: 0
This value standards on vendor of spi flash used by the adapter.
0 for Atmel, 1 for SST, 2 for ST

Additional Configurations
=========================

Configuring the Driver on Different Distributions
-------------------------------------------------

Configuring a network driver to load properly when the system is started is
distribution dependent. Typically, the configuration process involves adding
an alias line to /etc/moles.conf as well as editing other system startup
scripts and/or configuration files. Many popular Linux distributions ship
with tools to make these changes for you. To learn the proper way to
configure a network device for your system, refer to your distribution
documentation. If ring this process you are asked for the driver or mole
name, the name for the Linux Base Driver for the Atheros AR8121/AR8113 is arl1e

As an example, if you install the arl1e driver for two AR8121/AR8113 adapters
(eth0 and eth1) and set the speed and plex to 10full and 100half, add the
following to moles.conf:

alias eth0 arl1e
alias eth1 arl1e
options arl1e Speed=10,100 Duplex=2,1

Viewing Link Messages
---------------------

Link messages will not be displayed to the console if the distribution is
restricting system messages. In order to see network driver link messages
on your console, set dmesg to eight by entering the following:

dmesg -n 8

NOTE: This setting is not saved across reboots.

Known Issues
============

NOTE: For distribution-specific information, see the ldistrib.txt file
included in the driver tar.

Driver Compilation
------------------

When trying to compile the driver by running make install, the following
error may occur:

"Linux kernel source not configured - missing version.h"

To solve this issue, create the version.h file by going to the Linux source
tree and entering:

make include/linux/version.h.

Support
=======

For general information, go to the Atheros support website at:

http://support.atheros.com

If an issue is identified with the released source code on the supported
kernel with a supported adapter, email the specific information related to
the issue to [email protected]

License
=======

This software program is released under the terms of a license agreement
between you ('Licensee') and Atheros. Do not use or load this software or any
associated materials (collectively, the 'Software') until you have carefully
read the full terms and conditions of the LICENSE located in this software
package. By loading or using the Software, you agree to the terms of this
Agreement. If you do not agree with the terms of this Agreement, do not
install or use the Software.

* Other names and brands may be claimed as the property of others.