The statement "The Linux kernel 3.4 also contains a basic DisplayLink driver" seems to indicate to me that Linux kernels since 3.4 have built-in support (even if it is very limited basic support) for DisplayLink certified USB3 devices (no external kernel module needed).Īm I misreading or misunderstanding this statement on Wikipedia? There are also unofficial reverse-engineered specifications available for older revisions of DisplayLink technology. There was a DisplayLink-supported open source project called libdlo with the goal of bringing support to Linux and other platforms. The Linux kernel 3.4 also contains a basic DisplayLink driver.ĭisplayLink driver installer for Debian and Ubuntu based Linux distribution (Elementary OS, Mint, Kali, Deeping and et cetera) is available as part of displaylink-debian project. So, in theory at least, it just opens up the possibilities for much that could be done with a router that cannot be done easily right now.Ĭurrent generation of USB3 chips is supported by binary-only driver on Ubuntu. You would also get to, in theory at least, see the router bootup messages when you reboot or poweron the router, and in theory, modify the bootloader command line much like a regular linux computer user could. It would also eliminate the problem of your router ssh connection disconnecting for the numerous reasons that it could. This would make trouble-shooting any connectivity issue much easier - as you would not need to ssh in, in case you are not able to.Īnd if users believe they might have accidentally "bricked" their router, they might be able to verify that more easily by connecting a monitor and keyboard directly - if the monitor/keyboard does work to access the router's linux virtual terminal - then it is not a bricked router but rather a connection-related problem (which could either be a hardware problem or software-configuration problem). to be able to use the router like a regular directly-connected virtual terminal linux computer. Not to be critical in any way (because this project is enormously useful in the amount of features/packages that it adds to routers, and so, has tremendous value), but this seems to me that it would be an obvious feature that users would want - i.e. I just did a 'du -hxcs /lib/modules/"$(uname -r)"' on another Ubuntu (Desktop) computer to reveal that it takes disk space of about 237MB - So, this is well within the space limits of most routers made after 2016. So, space is clearly not an issue any more for packaging the same number of kernel modules that comes with most desktop distributions of Linux such as Ubuntu. over USB) include Printersīut much more to the point, if openwrt comes with a vanilla (or close-to-vanilla) Linux kernel version 4.14.195, then should it not already have all the packaged kernel modules within '/lib/modules' and all the hardware-autodetect features (and kernel module auto-loading) of the vanilla kernel?Īnd even if it is far from a vanilla kernel - routers now come with 512MB to 1024MB of RAM with the option of connecting a disk of any available size via USB3/eSATA. OpenWrt supports any hardware that has Linux support devices that can be connected (e.g. The Wikipedia article about Openwrt states the following text (within quotes):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |