Ok, I found something called Thesycon USB Descriptor Dumper – very handy tool. Ok, go back to Linux, lets check what kernel knows about this device $ lsusb -vd 040d:3401īus 001 Device 003: ID 040d:3401 VIA Technologies, Inc.īDeviceClass 0 (Defined at Interface level) And yes, after I’ve changed it to point to the older firmware bin, I can flash it with the new loader. It looks like only four files is changed: flasher exe and dll, VIAFwUpd.ini and one of the bin files. Ok, lets compare this two firmware archives. Going back to previous firmware. Except firmware flasher attached with older firmware won’t flash my updated card. My system tells me again that I have only two audio channels.
My second step was to check official website for newer firmware updates. It was better – system detects proper 5.1 device. So of course I asked Google for help, and found firmware that should work.
#Zyxel nsa310 firmware update usb drives windows
Audiotrak supports only Windows and OSX, but since this is standard USB audio device it should run under everything. System recognized this device as stereo card, sound went down randomly, volume control was not always working. As you probably guessed – it didn’t went well. Then, one day I tried to use it under Linux. I bought one to use it with my Windows computer. It has pretty decent sound quality to price ratio. Maya U5 is an USB sound card with 5.1 channels support. TL/DR: I’ve fixed Maya’s firmware to work better under Linux: Audiotrak-Maya-U5-firmware-mod.zip Part 1: whats broken in My projects, My soft, Others | | 230 Words | Comment Fixing Audiotrak Maya U5 firmware Or not, if I’ll have some great feature idea. Further changes will be mainly polishing and bug fixing, I think. I was also cleaning up the code, refactoring build system and adding unit tests. Of course gripgen can do it after it reads entire list, thus feeding it with find will not show you percentages until find ends. Excluding binary files might help, I guess.Īnd since file list is read asynchronously, now I could print pretty percentage progress. It looks like Defender is scanning every file that I am opening for indexing. And under Windows indexing is painfully slow due to Windows Defender (at least during my test on Windows 10).
Unfortunately, mechanical drive is usually the bottleneck itself, so it will be not much difference. As a result indexing over SSD drive is several times faster. Also memory organisation was changed to play nicer with cache. Now reading file names is not blocking indexer. There is also significant performance improvement of index generation (gripgen). I will probably replace it with Boost code, eventually. This version could have issues when grepping file with lines longer than 16 kB due to my simplified implementation of getline. There are build for Windows in the release page. Now it could be used with Boost library, as alternative to POSIX. Recently I was working on my indexed grep.
0 kommentar(er)
