triord.blogg.se

Loopback devices
Loopback devices




  1. #Loopback devices driver
  2. #Loopback devices archive
  3. #Loopback devices trial

+ * delay between soft reset and loopback enablement.

#Loopback devices trial

+ /* FIXME: Based on trial and error test, it seem 1G need to have + /* Need soft reset to have speed configuration takes effect */ + phy_modify_paged(phydev, MII_MARVELL_MSCR_PAGE, + phy_modify(phydev, MII_BMCR, ~0, bmcr_ctl) +static int marvell_loopback(struct phy_device *phydev, bool enable)

loopback devices

#define -1932,6 +1934,48 static void marvell_get_stats(struct phy_device *phydev, For loopback enabled, add bit-6 and bit-13 configuration in both PageĠ Register 0 and Register 21. Signed-off-by: Mohammad Athari Bin Ismail Tested working on Marvell88E1510 PHY for all speeds (1000/100/10Mbps).įIXME: Based on trial and error test, it seem 1G need to have delay betweenįixes: 014068dcb5b1 ("net: phy: genphy_loopback: add link speed configuration") Register 21 (MAC Specific Control Register 2) according to speed of Register), it is also required to configure same bits in BesidesĬonfiguring bit-6 and bit-13 in Register 0 (Copper Control Miller, Jakub Kicinski, Oleksij Rempel,Ĭc: netdev, linux-kernel,, stableĮxisting genphy_loopback() is not applicable for Marvell PHY. 13:12 ` Russell King (Oracle) 0 siblings, 1 reply 3+ messages in threadįrom: Mohammad Athari Bin Ismail 9:33 UTC ( / raw)

#Loopback devices archive

# dd if=/dev/zero of= ~/file.Net: phy: marvell: add Marvell specific PHY loopback Netdev Archive on help / color / mirror / Atom feed * net: phy: marvell: add Marvell specific PHY loopback 9:33 Mohammad Athari Bin Ismail The following commands can be used as an example of using the loop device. Prevented determining the status of the device. Loop device, it returns 1 if the device is not configured and 2 if an error occurred which RETURN VALUE losetup returns 0 on success, nonzero on failure. show Display the name of the assigned loop device if the -f option and a file argumentĮNCRYPTION Cryptoloop is no longer supported in favor of dm-crypt. The data end is set to no more than size bytes after the data start. Specify the columns that are to be printed for the -list output.įorce the kernel to scan the partition table on a newly created loop device. The data start is moved offset bytes into the specified file or device. See also -output, -noheadings -json and -raw.ĭon't print headings for -list output format. If a loop device or the -a option is specified, print the default columns forĮither the specified loop device or all loop devices the default is to print infoĪbout all devices. Show the status of all loop devices associated with the given file. If a file argument is present, use the foundĭevice as loop device.

loopback devices loopback devices

This allows for the file to be used as a.

loopback devices

#Loopback devices driver

The old output format (as printed withoutįorce the loop driver to reread the size of the file associated with the specifiedĭetach the file or device associated with the specified loop device(s).įind the first unused loop device. Linux supports a special block device called the loop device, which maps a normal file onto a virtual block device. Note that not all information is accessibleįor non-root users. MiB (=1024*1024), and so on for GiB, TiB, PiB, EiB, ZiB and YiB (the "iB" is optional,Į.g., "K" has the same meaning as "KiB") or the suffixes KB (=1000), MB (=1000*1000), and The size and offset arguments may be followed by the multiplicative suffixes KiB (=1024), losetup -a) with comma-delimited strings isĭeprecated in favour of the -list output format. Given, the status of the corresponding loop device is shown. Loop devices, and to query the status of a loop device. Losetup -c loopdev DESCRIPTION losetup is used to associate loop devices with regular files or block devices, to detach Print the name of the first unused loop device: Losetup - set up and control loop devices






Loopback devices