#asahi-dev · 2025-03-22 22:49
PaulFertserGood old strace can give a quick hint about the differences between minicom and pyserial, sometimes it's faster to view the log of syscalls to see what exactly happens there.#asahi-dev · 2025-03-20 23:29
PaulFertserfl0_id: it's kind of risky being passionate about something that can be ruined any moment by money-driven people who have the ultimate control after all.#asahi-dev · 2025-03-20 23:03
PaulFertserYou say it as if Linux isn't meant to be the product of full time paid developers these days.#asahi-dev · 2025-03-20 22:57
PaulFertserA practical way would be for someone to actually obtain at least the most popular brcmfmac devices and to test all the changes on all of them properly, and to become a real brcmfmac maintainer.#asahi-dev · 2025-03-20 22:55
PaulFertserfl0_id: such a large scale code duplication wouldn't be accepted either.#asahi-dev · 2025-03-20 22:54
PaulFertserAlso imagine the maintainers getting paid by Intel or similar, and the company requires certain performance and deadlines and such.#asahi-dev · 2025-03-20 22:53
PaulFertserfl0_id: those dberlin patches actually did regress functionality of the SDIO module I tried them on.#asahi-dev · 2025-03-20 22:52
PaulFertserRaspberryPi. What would justify the risk of breaking it unless the patch author is really convincing and also has tested important things on at least the most popular older models?#asahi-dev · 2025-03-20 22:52
PaulFertserfl0_id: well, it's supposed to happen that way but the whole subsystem thing changed lately too (Kalle Vallo quitting) and also imagine you're a maintainer of all the Linux wireless and you're offered a patch that potentially affects plenty of hardware without any proper documentation for the kernel <-> firmware API. And you know that the driver as it currently is works good enough on#asahi-dev · 2025-03-20 22:46
PaulFertserrrendec: also, brcmfmac was essentially unmaintained and I guess it still is, so the experience upstreaming anything to it might be frustating.#asahi-dev · 2025-03-20 22:43
PaulFertserrrendec: hi. I provided some feedback on brcmfmac patches testing it on AzureWave AW-CM256SM SDIO module (brcmfmac43455-sdio.bin firmware) but dberlin didn't really follow up.#asahi-dev · 2025-03-11 23:05
PaulFertserchaos_princess: dev as in "for those who want to develop support for it" and they semi-officially leaked schematics and some datasheets to make it easier.#asahi-dev · 2025-03-11 22:32
PaulFertserAnd running any OS on it doesn't require RE.#asahi-dev · 2025-03-11 22:32
PaulFertserAt least it doesn't have ever-changing firmware APIs.#asahi-dev · 2025-03-11 22:31
PaulFertserWished it was the most serious problem with that toy :/#asahi-dev · 2025-03-11 22:27
PaulFertserThe battery failing?#asahi-dev · 2025-03-11 22:15
PaulFertserOK. All three ports on PBP are capable of high speed.#asahi-dev · 2025-03-11 22:14
PaulFertserIs it expected to be a high speed device or super speed?#asahi-dev · 2025-03-11 22:11
PaulFertserfl0_id: you can test it with any other USB device to be sure, you'll see messages in dmesg right away even with that shitty pinebook pro.#asahi-dev · 2025-03-11 22:10
PaulFertserDo you confirm m1n1 should be detected as High Speed?#asahi-dev · 2025-03-11 22:10
PaulFertserAlso you can use Type-C to Type-C cable if you expect mac to be a USB Device.#asahi-dev · 2025-03-11 22:09
PaulFertserMachine can't matter there.#asahi-dev · 2025-03-11 22:09
PaulFertserNo output means neither D+ nor D- are pulled up, so no USB 2.0 communication can happen at all.#asahi-dev · 2025-03-11 22:08
PaulFertserfl0_id: probably only one of the ports on M3 is used that way, or probably it uses SuperSpeed? I suggest you check the commit that claims that it adds support for USB Device for that board you have there.#asahi-dev · 2025-03-11 22:06
PaulFertserfl0_id: I suggest you check dmesg to see what exactly happens from kernel point of view#asahi-dev · 2024-12-01 17:38
PaulFertserNo link visible in your last 3 messages.#asahi-dev · 2024-06-01 11:45
PaulFertserWhat's the voltage on failed battery btw?#asahi-dev · 2024-05-09 10:09
PaulFertserleio: guess you need to talk to your ISP about that, hope they're sane and can figure it out and ping the right people.#asahi-dev · 2024-05-09 10:08
PaulFertserMy traceroutes for the reference https://paste.debian.net/1316420/#asahi-dev · 2024-05-09 10:05
PaulFertserBut ICMPv6 pings are indeed ignored.#asahi-dev · 2024-05-09 10:04
PaulFertserOne can suspect HE<->Cogent peering dispute but in this case apparently there're alternative routes so it works from HE tunnel too.#asahi-dev · 2024-05-09 10:03
PaulFertserTested from two different locations, one native one HE.net, both work.#asahi-dev · 2024-03-26 21:17
PaulFertserInteresting, 500 ms is really plenty and I assume 300 worked less reliably so it might be not a simple debounce but also a meaningful delay that helps.#asahi-dev · 2024-03-26 21:16
PaulFertsertypo#asahi-dev · 2024-03-26 21:16
PaulFertseralso a type in deboune#asahi-dev · 2024-03-26 21:15
PaulFertserThe string in the dev_info says 300 not 500.#asahi-dev · 2024-03-19 12:51
PaulFertsercallmexd: feel free to ask on #asahi-alt but in general the idea is that Kali isn't that useful, you can have all the same tools on any mainstream distro, there's little added value in Kali afaik.#asahi-dev · 2023-12-27 10:36
PaulFertserWorth announcing on main non-dev channel probably?#asahi-dev · 2023-12-15 08:25
PaulFertserVery nice indeed.#asahi-dev · 2023-12-15 08:20
PaulFertserDo modern displays generate EDID on the fly somehow or is still a dedicated EEPROM IC inside which can be ~easily reflashed? Or probably there's a market for a small board which would pass through the video lines but allow to present a custom tweakable EDID?#asahi-dev · 2023-11-19 17:37
PaulFertserYes, with nick eiln but not right atm.#asahi-dev · 2023-11-08 19:41
PaulFertserPiR: https://github.com/AsahiLinux/docs/wiki/Yaks-in-need-of-shaving#asahi-dev · 2023-09-20 09:13
PaulFertserNice thing it has SWD working under reset. Not all MCU manufacturers did it right with cortex-m even though the specs require it iirc.#asahi-dev · 2023-09-18 13:15
PaulFertserAre you probably able to "halt" it?#asahi-dev · 2023-09-18 13:14
PaulFertserI mean if it's working at least somehow probably automating read attempts can get you all the data eventually.#asahi-dev · 2023-09-18 13:11
PaulFertserInstability can be worked around by scripting probably.#asahi-dev · 2023-09-18 13:11
PaulFertserIs that OpenOCD? Cool to see it working for that purpose :)#asahi-dev · 2023-09-17 18:43
PaulFertserjannau: on new line 16 should it really be "skpdet" (and not spkdet) https://github.com/AsahiLinux/alsa-ucm-conf-asahi/pull/4/commits/3ecdf4f4e1b24b74fd3fca18435781d7954590ad ?#asahi-dev · 2023-09-01 18:11
PaulFertserknedlik: what about "du -sh /lib/modules/<version>/*" ? I mean you should see where this all space goes for real. I'm not sure about -D option.#asahi-dev · 2023-09-01 18:07
PaulFertserknedlik: without source and build symlinks?