ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2025-06-20 16:10:29 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove '_drv' suffix

Browse Source 
Issue #4420
This commit is contained in:
Norman Feske
2024-05-30 15:46:57 +02:00
parent cb88c2c3e2
commit 8943a3e949
329 changed files with 1062 additions and 1063 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
repos/dde_linux/src/drivers/usb_hid/target.inc
View File

@ -1,4 +1,4 @@
TARGET = usb_hid_drv
TARGET = usb_hid
LIBS = base jitterentropy virt_lx_emul
INC_DIR = $(PRG_DIR)/../.. $(REP_DIR)/src/lib/usb_client

6
repos/dde_linux/src/drivers/usb_net/README
View File

@ -18,7 +18,7 @@ NIC configuration
Configuration snippet:
!<start name="usb_net_drv">
!<start name="usb_net">
! <resource name="RAM" quantum="10M"/>
! <config mac="2e:60:90:0c:4e:01 configuration="2" />
! <route>
@ -44,11 +44,11 @@ LTE modem configuration
Currently there is support for MBIM (Mobile Broadband Interface Model) devices.
Tested devices:
Huawai ME906s (P/V: 12d1:15c1) - "configuration=3" for 'usb_net_drv'
Huawai ME906s (P/V: 12d1:15c1) - "configuration=3" for 'usb_net'
Fibocom L830-EB-00 (P/V: 2cb7:0210) - automatically detected
!<start name="usb_nic_drv">
!<start name="usb_nic">
! <resource name="RAM" quantum="10M"/>
! <provides>
! <service name="Terminal"/>

2
repos/dde_linux/src/drivers/usb_net/target.inc
View File

@ -1,4 +1,4 @@
TARGET = usb_net_drv
TARGET = usb_net
LIBS = base jitterentropy virt_lx_emul
INC_DIR = $(PRG_DIR)/../..

14
repos/dde_linux/src/drivers/wifi/README
View File

@ -1,4 +1,4 @@
The wifi_drv component is a port of the Linux mac802.11 stack as well as
The wifi component is a port of the Linux mac802.11 stack as well as
libnl and wpa_supplicant to Genode. Depending on the used platform it
features a selection of drivers for wireless devices. For example on the
PC platform it contains the ath9k, iwlwifi and rtlwifi drivers for PCI(e)
@ -6,14 +6,14 @@ devices.
In contrast to other DDE Linux based drivers the actual driver portion is
confined to its own library to better isolate the various parts of the driver.
The 'wifi_drv' binary is the generic management part that includes the Wifi
The 'wifi' binary is the generic management part that includes the Wifi
configuration interface and the 'wpa_supplicant'. A suitable driver library
is loaded at run-time (see section [Debugging]).
To start the component on the PC platform the following configuration snippet
can be used:
!<start name="wifi_drv" caps="250">
!<start name="wifi" caps="250">
! <resource name="RAM" quantum="32M"/>
! <provides><service name="Nic"/></provides>
! <config>
@ -41,7 +41,7 @@ can be used:
On other platforms the wifi library will be different. The following
snippet illustrates the use of the driver on the PinePhone:
!<start name="wifi_drv" caps="250">
!<start name="wifi" caps="250">
! <resource name="RAM" quantum="32M"/>
! <provides><service name="Nic"/></provides>
! <config>
@ -118,7 +118,7 @@ a better fit accesspoint for the configured network.
Also, the driver can be switched to verbose logging during runtime
by setting the 'verbose' or 'verbose_state' attribute to 'true'.
The wifi_drv creates two distinct reports to communicate its state and
The wifi driver creates two distinct reports to communicate its state and
information about the wireless infrastructure to other components. The
first one is a list of all available accesspoints. The following examplary
report shows its general structure:
@ -166,7 +166,7 @@ label "devices" if requested in the config as depicted.
Debugging
~~~~~~~~~
As mentioned in the introduction the 'wifi_drv' component is special in the
As mentioned in the introduction the 'wifi' component is special in the
regard that the actual driver is provided as a shared-object to better isolate
it from the the driver binary that is a Libc::Component managing the
'wpa_supplicant'. Since this code and in return the binary is the same for each
@ -185,7 +185,7 @@ is necessary to link the driver binary directly against the driver library
rather then stub ABI library. This is achieved by adapting the driver's
'target.mk' file. In
!TARGET := wifi_drv
!TARGET := wifi
!SRC_CC := main.cc wpa.cc access_firmware.cc
!LIBS := base wifi
![…]

2
repos/dde_linux/src/drivers/wifi/frontend.h
View File

@ -1650,7 +1650,7 @@ struct Wifi::Frontend : Wifi::Rfkill_notification_handler
/**
* Trigger RFKILL notification
*
* Used by the wifi_drv to notify front end.
* Used by the wifi driver to notify front end.
*/
void rfkill_notify() override
{

2
repos/dde_linux/src/drivers/wifi/target.mk
View File

@ -1,4 +1,4 @@
TARGET := wifi_drv
TARGET := wifi
SRC_CC := main.cc wpa.cc access_firmware.cc
LIBS := base wifi
LIBS += libc

2
repos/dde_linux/src/lib/wpa_driver_nl80211/symbol.map
View File

@ -12,7 +12,7 @@
poll;
/* needed by wpa_supplicant lib for wifi_drv */
/* needed by wpa_supplicant lib for the wifi driver */
nl_set_wpa_ctrl_fd;
local:

2
repos/dde_linux/src/lib/wpa_supplicant/symbol.map
View File

@ -4,7 +4,7 @@
{
global:
/* needed by wifi_drv */
/* needed by wifi driver */
wpa_main;
wpa_reporter_init;
wpa_ctrl_set_fd;