rt-thread/components/drivers/phy/SConscript

from building import *

cwd     = GetCurrentDir()
CPPPATH = [cwd, cwd + '/../include']
src = Glob('*.c')
if GetDepend('RT_USING_OFW') == False:
    SrcRemove(src, ['ofw.c'])

if GetDepend('RT_USING_PHY_V2') == False:
    SrcRemove(src, ['general.c','mdio.c','ofw.c'])

if GetDepend('RT_USING_PHY_V2') == False:
    if GetDepend('RT_USING_PHY') == False:
        SrcRemove(src, ['phy.c'])

group = DefineGroup('DeviceDrivers', src, depend = [''], CPPPATH = CPPPATH)

Return('group')
1. 抽象了PHY的设备模型，在components中增加了PHY设备的相关代码以及KCONFIG配置和SConscript脚本 2. 在IMXRT的Libraries中增加了peripherals目录，用于具体型号的设备驱动相关的代码的实现，不应与MCU的平台相关，实现PHY的设备对象中的相关接口。 3. 修改了BSP中的Sconstruct文件，增加了peripherals目录的构建 4. 修改了KEIL环境的SCT文件，用于实现以太网功能 2020-10-12 18:15:01 +08:00			`from building import *`

			`cwd = GetCurrentDir()`
[components][driver]add phy and mdio bus old phy bus is too simple add phy_bus is not adapt rt_bus framework,so writer a stronger phy bus framework. here is my commit message: add mdio bus and phy bus to kernel,the phy bus use rt_bus framewok ,driver writer can write phy_driver first .when mac driver need to use phy they can register phy_device and pjhy_devie will serach for driver which match by uid and mask,if no driver match with the device that you register,phy_bus will return the genphy to you device,the genphy driver is the general driver for phy,so you can use it but it can not support the capcity of chip it may be cause performance is not up to peak 2024-11-20 10:34:03 +08:00			`CPPPATH = [cwd, cwd + '/../include']`
format Kconfig and sconscript 2023-01-08 21:14:23 -05:00			`src = Glob('*.c')`
add ofw api to of net,driver writer can use this api get phy modes or get mac address 2024-09-30 10:35:36 +08:00			`if GetDepend('RT_USING_OFW') == False:`
			`SrcRemove(src, ['ofw.c'])`
[components][driver]add phy and mdio bus old phy bus is too simple add phy_bus is not adapt rt_bus framework,so writer a stronger phy bus framework. here is my commit message: add mdio bus and phy bus to kernel,the phy bus use rt_bus framewok ,driver writer can write phy_driver first .when mac driver need to use phy they can register phy_device and pjhy_devie will serach for driver which match by uid and mask,if no driver match with the device that you register,phy_bus will return the genphy to you device,the genphy driver is the general driver for phy,so you can use it but it can not support the capcity of chip it may be cause performance is not up to peak 2024-11-20 10:34:03 +08:00
			`if GetDepend('RT_USING_PHY_V2') == False:`
			`SrcRemove(src, ['general.c','mdio.c','ofw.c'])`

			`if GetDepend('RT_USING_PHY_V2') == False:`
			`if GetDepend('RT_USING_PHY') == False:`
			`SrcRemove(src, ['phy.c'])`

			`group = DefineGroup('DeviceDrivers', src, depend = [''], CPPPATH = CPPPATH)`
1. 抽象了PHY的设备模型，在components中增加了PHY设备的相关代码以及KCONFIG配置和SConscript脚本 2. 在IMXRT的Libraries中增加了peripherals目录，用于具体型号的设备驱动相关的代码的实现，不应与MCU的平台相关，实现PHY的设备对象中的相关接口。 3. 修改了BSP中的Sconstruct文件，增加了peripherals目录的构建 4. 修改了KEIL环境的SCT文件，用于实现以太网功能 2020-10-12 18:15:01 +08:00
			`Return('group')`