#
…

2023-12-13

00:00holiday has quit [Quit: WeeChat 4.1.2]
00:02Wubbzy04 has joined #asahi
00:13Wubbzy04 has quit [Ping timeout: 480 seconds]
00:21Wubbzy04 has joined #asahi
00:35Wubbzy04 has quit [Ping timeout: 480 seconds]
00:37crabbedhaloablut has quit []
00:58ah- has quit [Read error: Connection reset by peer]
00:58ah- has joined #asahi
01:02Wubbzy04 has joined #asahi
01:10Wubbzy04 has quit [Ping timeout: 480 seconds]
01:13kidplayer666 has quit [Quit: Connection closed for inactivity]
01:20Wubbzy04 has joined #asahi
01:29Wubbzy04 has quit [Ping timeout: 480 seconds]
01:32Brainium has quit [Quit: Konversation terminated!]
01:36littlebit670 has joined #asahi
01:37littlebit670 has quit []
01:38littlebit670 has joined #asahi
01:38Wubbzy04 has joined #asahi
01:39littlebit670 has quit []
01:48Wubbzy04 has quit [Ping timeout: 480 seconds]
01:53zalyx has quit [Quit: Ping timeout (120 seconds)]
01:53zalyx has joined #asahi
02:00DragoonAethis has quit [Quit: hej-hej!]
02:00DragoonAethis has joined #asahi
03:01denysonique has quit [Quit: .]
03:01denysonique has joined #asahi
03:02KxCORP has quit [Quit: Bye!]
03:02KxCORP has joined #asahi
03:25malte_ has joined #asahi
03:26malte has quit [Ping timeout: 480 seconds]
03:43Wubbzy04 has joined #asahi
03:44jnn has joined #asahi
03:48jn has quit [Ping timeout: 480 seconds]
03:54Wubbzy04 has quit [Ping timeout: 480 seconds]
04:07lanodan has quit [Ping timeout: 480 seconds]
04:40marvin24_ has joined #asahi
04:43marvin24 has quit [Ping timeout: 480 seconds]
05:32mcint has joined #asahi
05:32jeisom has quit [Ping timeout: 480 seconds]
06:01psykose has quit [Remote host closed the connection]
06:09psykose has joined #asahi
06:15janrinze has quit [Read error: Connection reset by peer]
06:18janrinze has joined #asahi
06:43VeeBop has quit [Ping timeout: 480 seconds]
06:52jerrardpang has joined #asahi
06:52VeeBop has joined #asahi
06:52jerrardpang has left #asahi [#asahi]
07:08VeeBop has quit [Ping timeout: 480 seconds]
07:20chadmed has quit [Quit: Konversation terminated!]
07:21chadmed has joined #asahi
07:25chadmed has quit []
07:25chadmed has joined #asahi
07:28chadmed has quit []
07:28chadmed has joined #asahi
07:34aead has quit [Ping timeout: 480 seconds]
07:40aead has joined #asahi
08:00greenbeard has joined #asahi
08:17VeeBop has joined #asahi
08:17VeeBop has quit []
08:18VeeBop has joined #asahi
08:21greenbeard has quit [Ping timeout: 480 seconds]
08:36Compassion0 has joined #asahi
08:42Compassion has quit [Ping timeout: 480 seconds]
08:42Compassion0 is now known as Compassion
08:44kidplayer666 has joined #asahi
09:12crabbedhaloablut has joined #asahi
09:16i509vcb has quit [Quit: Connection closed for inactivity]
09:32holiday has joined #asahi
09:44Nefsen402 has quit [Remote host closed the connection]
09:44Nefsen402 has joined #asahi
09:52Wubbzy04 has joined #asahi
10:00Wubbzy04 has quit [Ping timeout: 480 seconds]
10:10pjakobsson has quit [Remote host closed the connection]
10:19janek has joined #asahi
10:36holiday has quit [Quit: WeeChat 4.1.2]
11:33kallsyms has quit [Ping timeout: 480 seconds]
11:35kallsyms has joined #asahi
11:42jeisom has joined #asahi
12:00rvalue has quit [Ping timeout: 480 seconds]
12:05rvalue has joined #asahi
12:45rvalue has quit [Ping timeout: 480 seconds]
12:46anon has joined #asahi
12:47anon has quit []
12:48rvalue has joined #asahi
12:52Moprius has joined #asahi
12:56Brainium has joined #asahi
13:06Moprius has quit [Quit: bye]
13:08brucekapp has joined #asahi
13:12brucekapp has quit []
13:55Wubbzy04 has joined #asahi
14:03Wubbzy04 has quit [Ping timeout: 480 seconds]
14:06janek has quit [Remote host closed the connection]
14:22rvalue- has joined #asahi
14:26rvalue has quit [Ping timeout: 480 seconds]
15:05darkapex has quit [Remote host closed the connection]
15:05darkapex has joined #asahi
15:24Brainium has quit [Ping timeout: 480 seconds]
15:28lanodan has joined #asahi
15:29ydalton has joined #asahi
15:30Wubbzy04 has joined #asahi
15:30ydaltonhm, i always had this question, what if you blacklisted the asahi kernel driver from loading, but the dcp driver would still be loaded. what would happen?
15:31svensoftware rending
15:33ydaltoneverything? but i imagine you'd still be able to change backlight settings and the like
15:33ydaltonand the notch as well
15:33j`eyyes, those are part of dcp
15:34ydalton has quit [Remote host closed the connection]
15:43bluetailcan you run asahilinux in a virtual machine on a x86 pc?
15:43bluetailmacOS already does, if you enter the "secret" passphrase ...
15:43ydalton has joined #asahi
15:44svenuh, what would be the point of that?
15:44ydaltondoesn't running asahi linux in a VM not make sense at all?
15:44ydaltonoh yeah i tried the blacklist thing myself, yeah there was indeed software rendering, but thanks to dcp, i didn't get screen tearing or anything like that
15:45j`eybluetail: you could run a arm64 linux distro, but there's no reason to try asahi, since its only reason is to work on apple silicon hw directly
15:45ydaltonit's not like running the default arch linux arm where it uses simpledrm and you do have screentearing
15:49j`eyyou can add 'nomodeset' on the kernel command line if you want to try that out!
15:52bluetailj`ey run a vm, do gpu passthrough and see if the screens misbehave the same way they did on my m1 mac, or maybe my m1 mac is just defective... In any case, I still believe apple products talk proprietary to displays, and no displays other than the apple displays understand fully.
15:53j`eybluetail: it wont be using the same drivers or anything
15:54bluetailoh. so its futile... thx
15:54j`eyother people are using random displays, without issues
16:02chadmed has quit [Read error: Connection reset by peer]
16:02chadmed has joined #asahi
16:04kidplayer666 has quit [Quit: Connection closed for inactivity]
16:06bluetailj`ey apple locking down threads and macrumors having a felt hundred pages with display related issues is not exactly no issues... but yes, there are people with no issues, correct. There are also people who have apple displays that have issues. But I claim something I have no evidence for, that apple is intransparent about the parts and the
16:06bluetailcommunications to displays in general [...]
16:07j`eysure, maybe there's some extra stuff for apple displays, but clearly they stick to standard stuff for other displays
16:10bluetailj`ey I have had lots of 'green line' artifacting in motion, as well as a moire effect, and I cannot make evidence as I lack the optics to do so. It could be even that apple is completely strictly following the specification. However what seems clear to me, that on the non-apple machines, the image is different, no matter what OS, and that I am used
16:10bluetailto it and can't get used to the small difference on what the display interprets on macOS
16:11j`eyand by 'on macOS' you also include asahi, right?
16:11bluetailno, I mean the hardware
16:11bluetailasahi behaves almost completely equally
16:11j`eyright, that's what I meant
16:11bluetailthe difference is that on macOS the issues comes up randomly
16:11bluetailon asahi it seems always present
16:12bluetailI only can make guesses, and I am probably totally wrong about what is the actual cause of it
16:13j`eyhave you been able to show anyone differences irl?
16:14bluetailI have shown it to one person, but they were barely noticing any difference
16:14bluetailI think the most likely outcome is that they'll say its in my head
16:14bluetailto which I went to the optometrist, which didnt find any issue with my sight
16:18bluetailj`ey ... I know of one user who might in the future be able to measure any differences...
16:18bluetailBut I don't name them, cause I don't want to exert any pressure
16:19bluetailfurthermore, I am absolutely certain this issue might express itself differently on different displays
16:20bluetailI have three displays at home where I can see it
16:21bluetailThey have in common: High-Refresh Rate, TN Panel. Brands: LG, BenQ
16:21bluetailThe moire effect lessens with higher refresh rate, which is confusing to me
16:22bluetailIt appears to me as staring through bares all the time, when I move my head a bit from left to right
16:23bluetailI tried alternative power sources, such as a UPS, but no diff
16:25j`eynext thing would be to try another m1. but unless there's an issue that someone can repro and work out if dcp is doing something "wrong"..
16:28bluetailyea, if it is just a defective m1, claims would just waste anybody elses time...
16:30ydaltonj`ey: i have tried nomodeset and it's exactly the same outcome as installing arch linux asahi by default
16:30ydalton*with the default drivers
16:33j`eyalthough on fedora I think thats get you the EFI FB, not simpledrm, but all the same really
16:33mate_czagany has joined #asahi
16:44ydaltonwoops, almost pasted a ton of text instead of the pastebin
16:47ydaltonbut this is just a normal boot
16:47j`eyyeah, efi is prefered for now for some reason
16:48j`eythere's a patch on the mailing list, but tbh it doesnt matter much sine DCP will take over
16:48ydaltoni don't see any entries related to efifb tho
16:48kidplayer666 has joined #asahi
16:49ydaltonj`ey: also i see the work of your patch, where it prints the kernel resource range properly :D
16:50j`eyoh hey, that's in 6.6, nice!
16:52ydaltonhow long would you expect patches to be merged in the kernel?
16:52j`eyI just forgot around what time I had sent that, maybe it was going into 6.7
16:53ydaltoni think it was october something
16:53ydaltoncuz i submitted a very similar patch at that same time
16:54ydaltonkernel noobie :D
16:56j`eyoh only 5 days after me
16:58ydaltoni got the Reviewed-by but nothing came of it i think
17:00j`eyyou could ping it with an email
17:02ydaltoni would say patches that add code or fix a real bug are treated with more priority
17:02ydaltonand this one is neither so
17:03j`eyits also a small fix and nearly2months, so i think it's fine
17:04ydaltonwould i wait til 6.7?
17:06j`eyI think you can email now
17:08ydaltonalright, i think i will do so in the weekend
17:09ydaltonthanks for your advice
17:12ChaiTRex has quit [Remote host closed the connection]
17:15ChaiTRex has joined #asahi
17:51PaulFertserydalton: what's the status on patchwork for your patch?
18:01jeisom has quit [Ping timeout: 480 seconds]
18:11Wubbzy04 has quit [Ping timeout: 480 seconds]
18:21Wubbzy04 has joined #asahi
18:22maria has quit [Ping timeout: 480 seconds]
18:23maria has joined #asahi
18:24c10l has quit [Remote host closed the connection]
18:24c10l has joined #asahi
18:25ydalton has quit [Remote host closed the connection]
18:37Wubbzy04 has quit [Ping timeout: 480 seconds]
18:41nicolas17 has joined #asahi
18:48Moprius has joined #asahi
18:48Wubbzy04 has joined #asahi
18:54Brainium has joined #asahi
19:01ydalton has joined #asahi
19:01ydaltonPaulFertser: it's marked "new, archived", and that's about it
19:03ydalton has quit [Remote host closed the connection]
19:06Chai-T-Rex has joined #asahi
19:07ChaiTRex has quit [Ping timeout: 480 seconds]
19:12jeisom has joined #asahi
19:14svenwhich subsystem is this? Not all of them actually use patchwork
19:14svenand either way, after >2 months it’s fine to resend or reply to the thread
19:15millefy has quit [Ping timeout: 480 seconds]
19:22ert has joined #asahi
19:27i509vcb has joined #asahi
19:35V has quit [Ping timeout: 480 seconds]
19:36V has joined #asahi
19:40nicolas17we're still missing the bootrom version of T6034 (the fat M3 Max)
20:05maximbaz has quit [Quit: bye]
20:06maximbaz has joined #asahi
20:06mate_czagany has quit [Ping timeout: 480 seconds]
20:18billak has joined #asahi
20:21billak has quit [Remote host closed the connection]
20:34Wubbzy04 has quit [Ping timeout: 480 seconds]
20:40grgy has quit [Remote host closed the connection]
20:43Wubbzy04 has joined #asahi
20:45grgy has joined #asahi
20:53Wubbzy04 has quit [Ping timeout: 480 seconds]
21:01Wubbzy04 has joined #asahi
21:11john-cabaj1 has joined #asahi
21:15jeisom has quit [Quit: Leaving]
21:17john-cabaj has quit [Ping timeout: 480 seconds]
21:17john-cabaj1 is now known as john-cabaj
21:18Wubbzy04 has quit [Ping timeout: 480 seconds]
21:36Wubbzy04 has joined #asahi
22:15mort_so this probably isn't asahi's fault, but it invites comparison with macOS, which makes it clear that: Linux's bluetooth stack is seemingly a little bit broken in pretty much every single layer in the stack
22:20psykose6.6 broke even my bluetooth on every single device i tested, in that the first time connecting to a device crashes everything and it only works after restarting some stuff in the kernel :D
22:21mort_awesome!
22:22mort_for me it's just ambiently broken; way too aggressive with forcing reconnects, misses the first 0.1 second of audio, and best of all, I have to pair my earbuds again every time they've been connected to another device, connecting doesn't work
22:24Wubbzy04 has quit [Ping timeout: 480 seconds]
22:25psykosethe latter is fun, same here :D
22:26psykosethe middle one i think is a sink-sleeping thing
22:26psykoseif you disable sinks pausing(?) in wireplumber or wherever it was there is no initial delay
22:26psykosei guess it's by design
22:27mort_I don't care about why it happens, it's just so inelegant and certainly shouldn't be default behavior and iOS, macOS, Android and Windows all manage to not miss the first bit of audio
22:28mort_but the first and last issues are by far the largest ones
22:28mort_I just we had someone who cared about bluetooth working on bluetooth
22:33armort_: my experience comes from x86 non-apple laptops, but my experience is pretty much reverse - that the stack on linux works best
22:33mort_x86 linux stuff has always had weird bluetooth issues for me
22:34mort_some seemingly intended, like I don't think the incredibly aggressive "oh you connected your phone to your earbuds? Let me yank them back" behavior is a driver bug
22:38army issues with non-linux bt stacks mostly boil down to "linux lets me choose the codec, and doesn't arbitrarily limit the choice of codecs depending on bt hardware vendor"
22:39mort_Linux just limits choice of codecs to the 1 shitty sounding royalty free one
22:39ari have ldac, sbc, aac, and apt-x available.
22:39mort_yea? Linux bluetooth stacks generally don't support apt.x
22:40arnow, some distros (cough cough fedora cough) choose not to ship support for various features because of patents or whatever
22:41arbut that's, well, very much a fedora problem, and not limited to just bluetooth codecs
22:41mort_I haven't seen a distro ship apt-x support out of the box, when I've cared enough I've had to download and compile and install some pulseaudio fork with apt-x support
22:42psykoselibfreeaptx is a thing and every distro i've used has it with pipewire and that's available
22:43mort_I guess I haven't looked at this after the move to pipewire
22:43psykosethough i'm not sure what 'having an option' means? aren't they inherently limited to if the bluetooth device actually supports it
22:43psykoseif the headphones only have a decoder for one thing you can't actually pick anything else
22:44mort_what's the deal with libfreeaptx? I thought the problem with apt-x was the patents, not that there aren't FOSS encoder/decoder implementations
22:44psykoseyou're probably right
22:44psykosemost distros just don't care and shipped it anyway
22:45psykosereminds me of fedora disabling all the video decoders by default in mesa
22:45j`eyand ffmpeg
22:45Wubbzy04 has joined #asahi
22:45mort_it's beyond messed up that we're in a world where basic math can be patented, that governments just say "no you're not allowed to use this math now, Qualcomm owns this math"
22:48mort_anyway I could forgive the codec issue, it's outside of the FOSS world's control, but all the other basic functionality issues are huge problems and it doesn't seem like anyone cares
22:49mort_this is not an attack against Asahi, as I said I haven't used a Linux device with functional Bluetoth outside of Android
22:51aralso, funnily enough, i've seen the "headphones stealing" issue on my partner's devices, with ubuntu, windows, and android, but only if they use their headphones, and not borrow mine because they can't find their own
22:51mort_this "nobody seems to care" thing extends out into the broader Bluetooth ecosystem and standards bodies too, like why do we still not have ok bidirectional audio? Can it *really* be unreasonable amounts of data to send one 128kbps audio stream in ech direction where one is stereo
22:52arso i'm inclined to belive this does - at least to some extent - depend on the headphones
22:52mort_cars are notorious for stealing bluetooth devices in my experience
22:53mort_tho maybe more in the "client device forces the host to connect" way than "host forces the client device to connect" way
22:55arin any case, bluetooth remains to be a "fun" protocol.
22:55Wubbzy04 has quit [Ping timeout: 480 seconds]
22:56ari'm often amazed anyone manages to implement it in any somewhat working and compatible capacity, if not always securely
22:56mort_I'm amazed that the standards body hasn't just said "ok mp3 is decent and patents have expired, you now have to support 128-320kbps mp3"
22:57mort_guessing influence from the companies which want patent royalties for things like apt-x
23:01psykosethe decoder side has to be able to do it in hardware too, i wonder how hard hwdec mp3 is (i know the other modern codecs were designed around making it easy in hardware or whatever)
23:02mort_eh throw a $10 mcu in there and it'll sw decode mp3
23:02zerdox has joined #asahi
23:02arthere's also the issue of battery life
23:05mort_I guess there may be good reasons to not use mp3 if it actually is hard to hardware decode efficiently
23:20Wubbzy04 has joined #asahi
23:29Wubbzy04 has quit [Ping timeout: 480 seconds]
23:33crabbedhaloablut has quit []
23:41Wubbzy04 has joined #asahi
23:52Wubbzy04 has quit [Ping timeout: 480 seconds]
23:57linuxgemini8 has quit []
…