Yeah, somehow nobody invented HCI for Wi-Fi chips. USB has it, Bluetooth has it, but not Wi-Fi.
1,446 karma · joined December 29, 2014
Atheros (now Qualcomm) released its firmware source: https://github.com/qca/open-ath9k-htc-firmware
I have many, many these dongles :)
I'd argue it's "silent" though: aliexpress wakes up my audio card if nothing plays, which results in a very faint "pop" sound every time I open the tab.
It's been this way for ~3+ years at least.
Or vice-versa: you're free to sell publicly available free stuff.
There's technical open source (code licensed under free license), social open source (accepting contributions, working towards the user, maintaining), and stewarded open source ("the product" with the team, roadmaps, release cycles, but the code is open and free).
Technical vs social: many projects are made to solve the issue of the author, and just published on the internet under a FOSS license for everyone, nothing more. For a random project on the internet, you should not by default assume that the author is willing to fix the issue you report, implement the feature you'd like to have, or merge your contributed code — author may not be interested in solving your issue, they already solved theirs. That's open source which does not have social component.
What you have here is a stewarded open source: a Google project which have a team on a salary. The team has their own plans and goals on their product, and in addition they accept contributions. They might not be interested in them, or even be hostile to external contributions, because some PRs just disrupt their plans, not suitable in their architecture view, or could be seen as a maintenance burden which they didn't ask for. Check CONTRIBUTING.md in the repository: the code contribution is in the bottom of the list, and they have a hour and a half movie on how to contribute!
Since this is a team on a salary, your task is first and foremost to explain the issue you have, and make it clear what is wrong currently, why is it wrong, and how it could be improved. The code contribution should follow only after you've been understood and the issue has been confirmed as an issue. Only then you can make a suggestion PR if you feel so ("I fixed it this way, it works for me, take a look").
Issues with your PR:
- Minor one: used only what-have-been-done technical description instead of just describing the issue in plain words. Not "Reduce iOS pointer latency by dispatching pending input before BeginFrame" and a wall of refactoring later, but "Faster vsync and pointer painting performance", with short technical summary inside of PR message (maybe even video/tests of vsync latency before/after), and all the meat inside the commit message. Keep PR worded in a simple terms.
- Used PR comments as a chat: you wrote like 8 messages one after another in an hour. Give the developers some time to think, to maybe reconsider their decision or vision. The person might just had a bad day and you're just nagging them with questions which require thinking and remembering the code. Wait at least a day, or better a week, before responding to the message with outcome you did not expect.
- After "the infrastructure is broken, we're trying to remove it completely" message it'd better to ask if the developers have ideas, plans, or maybe draft implementation on how it could be improved, and if anybody is working on that already, instead of defending your position when you received decline.
You've got frustrated and disappointed that your PR did not get merged. I understand you and I was in your shoes. However keep in mind what I wrote about stewarded projects and take a closer look where are you contributing at: a project which requires you to sign CLA, which means to give your code authorship to the company. Do you really want to improve the product which is developed for money, without you getting money and giving away code authorship?
Won't write anything in addition, just recommend reading these two articles:
https://sneak.berlin/20250720/the-agpl-is-nonfree/, it's about completely different topic, but read from "Gifts absolutely do not work like that". And https://dri.es/license-only-versus-stewarded-open-source
One of mine: if there's something resembling postal tracking number according to regexp, add "Print label" item which prints its barcode on my Bluetooth thermoprinter.
And set shortcut for "Next History Item" and "Previous History Item".
Believe me, it would be much better.
Configure WIN+A and WIN+S for example.
In other words, if you want 3rd history item from the top, unlike on Windows, where you need to press Win+V, down, down, enter, here I press CTRL+W, W.
Network/Wi-Fi printers have at least 16 MB of RAM, usually 64+ MB nowadays.
I've spent 3 years on improving all the underlying stack and drivers to make it work reliably and bug-free, but the current RAM prices resulting in 2x price increase for the cheapest SBC, which makes the project economically infeasible to continue.
People on Reddit told me that in US there just "is'nt any non-wifi models". I'm not sure how true this is. If you have anything to comment, please do: https://old.reddit.com/r/printers/comments/1v09kb8/usbtowifi...
You need to manually download a color profile data (getweb script) though. Make sure there's /usr/share/foo2zjs/icm/hp-cp1025-rgb-392-bpp1.icm file.
If you tried to use foo2zjs in Fedora / Redhat or similar distro, they now require additional configuration with obscure error message: https://fedoraproject.org/wiki/Changes/FoomaticRipRejectsUnk...
If you have MATRIX PRINTER, please consider running GhostScript regression tests per release (twice a year).
The developer is looking for volunteers.
Otherwise upcoming GhostScript version will remove widely used LQ850 driver and you won't be able to use it in the next Debian/Ubuntu/whatever.
https://bugs.ghostscript.com/show_bug.cgi?id=709659
!!!
With 64GB HBM2e RAM physically, it's locked down to 8GB with the fuse.
2 months ago, a paper describing security bypass w/ code execution appeared, and a driver patch released a month ago.
You could get these "3090 64GB" for $250 or so only. Now they are $700+.
What's baffling is that hardly any major English tech publisher wrote about this hack of a century!
All the info in Russian: https://habr.com/ru/news/1060032/
Recent LLM tests @ Reddit: https://old.reddit.com/r/LocalLLaMA/comments/1vlwjr8/i_teste...
It was initially assumed that the RAM is also binned and the rest of it is bad in one way or another (doesn't work on expected frequencies, flip bits, etc). On 8GB (64GB) model we haven't seen bad RAM so far. The tests are all OK. 10GB versions supposedly have 80GB of physical memory, but only 40GB is unlockable (don't know the reason).
Upgrade to PCIe 2.0 16x possible. 2.0 4x is a software unlock with a driver patch, 16x requires capacitors soldering.
For some reason Windows handled increased memory consumption the least gracefully.
Many people continued to use v1.2 which use regular files.
V2.1 ended up using pread/pwrite nowz it's fine now.
The issue continued for 3 years more or less.
But these are mmaped, I don't know any easy debugging or monitoring solution besides writing kprobes/systemtap hooks.
How would you debug it?
systemd is a stewarded FOSS, which means there's a team behind it, who are getting paid, and develop this software with release cycles, backwards compatibility guarantees, architectural decisions, and such.
These people know better. I usually only prepare fixes for FOSS one-man-show which have little to no maintenance, otherwise I prefer professionals to handle it. Sometimes "suggestion" PR is worse than a triaged issue IMO.
https://github.com/systemd/systemd/blob/199f75205b9c0625bf56...
It's my third attempt to make my regular Linux desktop less disk-chatty. This is a huge issue for btrfs and for COW FS in general, because they have massive write amplification for small and frequent writes (38,7 TB written to my idle desktop SSD in 2 years).
If you're interested, here are my findings this time so far:
- workrave: 60 second stat sync https://github.com/rcaelers/workrave/pull/717
- kde klipper: saves to disk on every copy, even if permanent storage is disabled https://bugs.kde.org/show_bug.cgi?id=501030
- kde plasmashell: saves qt shader cache each time notification popup disappears https://bugs.kde.org/show_bug.cgi?id=523805
- bitwarden firefox extension: tries to connect to desktop application every 10 seconds, writes about every failure to browser's WebStorage 14+ KB https://github.com/bitwarden/clients/issues/22192
- firefox datareporting/glean: very chatty .mozilla/firefox/xxx/datareporting/glean/db/data.safe
- ipfs: writes every received DHT announce to disk, 20 GB in 3 hours https://discuss.ipfs.tech/t/constant-writes-to-datastore-log/20316
- mailcow: redis saves data every 5 minutes https://github.com/mailcow/mailcow-dockerized/pull/7405When I asked CyberShadow why, he replied that CD-ROM case claims Win9x compatibility, that's why any new update should not break it.
Just install "Chess VCL" component, drop it onto the form, compile, and you're ready to go!
If your board needs custom build, it's probably because there's no SPI flash with the bootloader. The board can't describe itself.
This could be solved https://sd-card-images.johang.se/ style: single kernel+rootfs OS image, with the small board-specific bootloader + dtb, which you concatenate to the OS image.
The majority of ARM SBCs can boot UEFI (TianoCore) as a u-boot payload, there are ports for many SoCs/platforms. Raspberry Pi has a port. Libre.computer ships Amlogic and Rockchip with UEFI out of the box.
Nobody just usually bothers because modern u-boot handles all aspects of boot process, incl. display and user interaction. Unless you want Windows on ARM, or want to use beefy server/desktop hardware (ARM non-SBC, non-embedded) with external PCI-e boards which may want to run its embedded .efi rom, you probably don't want UEFI.
I don't get it when the software author choses the license they don't see suitable in full, only because it's one of a common FOSS licenses, and than wiggle around it. There's nothing wrong with making open-source with exception, or dual licenses, or non-free software.
>you can do whatever you want with my work except profit.
GPL doesn't prohibit that.
https://www.gnu.org/philosophy/selling.html
> If a license does not permit users to make copies and sell them, it is a nonfree license.
I've seen https://v-it.org/ here on hackernews. Same idea, different wording.