ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
dcow has joined #asahi-dev
dcow has quit [Ping timeout: 480 seconds]
dcow has joined #asahi-dev
dcow has quit [Ping timeout: 480 seconds]
eiln has quit [Ping timeout: 480 seconds]
dcow has joined #asahi-dev
dcow has quit [Ping timeout: 480 seconds]
amarioguy has quit [Remote host closed the connection]
<janneg>
eiln: calibration upload works with the 13.5 isp firmware so this seems to be a 12.4 incompatibility
dcow has joined #asahi-dev
<janneg>
the 720p sensor is even with calibration data very noisy. could that be caused by a wrong config?
<leio>
janneg: thanks, I'll test it out when I get around to m1n1 updates overall, hopefully weekend
<kaazoo>
HI, in case anybody here uses ZFS: developers added support for BTI (Branch Target Identification) which is set via CONFIG_ARM64_BTI: https://github.com/openzfs/zfs/pull/15339
<leio>
on that topic, I'd be curious what packages overall need BTI disabling, besides chromium, to include these in ::gentoo out of the box
dcow has quit [Ping timeout: 480 seconds]
dcow has joined #asahi-dev
dcow has quit [Ping timeout: 480 seconds]
Yannik_Sc has quit [Ping timeout: 480 seconds]
<chadmed>
nothing i use regularly so far
<chadmed>
the fix for chromium is simple: stop using it
<leio>
I saw it done in webkitgtk fedora package too iirc, but I have other issues with it
dcow has joined #asahi-dev
Yannik_Sc has joined #asahi-dev
tenkuu has quit [Ping timeout: 480 seconds]
dcow has quit [Ping timeout: 480 seconds]
leitao has joined #asahi-dev
leitao has quit []
<janneg>
I doubt you've configured toolchain/portage configured to use BTI in the first place contrary to what fedora does
<chadmed>
leio took my make.conf which does explicitly enable -mbranch-protection=standard
leitao has joined #asahi-dev
Yannik_Sc has quit [Ping timeout: 480 seconds]
<leio>
chadmed: note that strip-flags used by brittle packages used to filter that out, but since yesterday it doesn't
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dcow has joined #asahi-dev
eiln has joined #asahi-dev
<eiln>
sounds like m2 SET_FILE_LOAD abi changed between 12.4 & 13.5? maybe that's where iova became u32 -> u64? if so we'll need the dcp os version checks
<eiln>
janneg: if it's "noisy" as in grainy it's very likely a temporal/motion filter issue (constants are off, graph order isn't right). lina should have an m2 fork of the tracer, which I do not see in any branch
<eiln>
chadmed: agreed
dcow has quit [Ping timeout: 480 seconds]
<leio>
someone needs to tell slack to add huddle support when used with firefox.
<psykose>
apparently it's only disabled on firefox+linux
<leio>
right, time to user agent spoof then :)
<leio>
(which is bad in way, as they'll think they have no users on firefox+linux or something); anyhow, getting off-topic
leitao has joined #asahi-dev
<cy8aer>
I just played around with the camera and want to present my results. first of all: The device works. ffplay/mpv /dev/video0 works for my desktop user. The problems I have now: Firefox says the device does not have the right resolution when I open a jitsi session. And cheese only works if run as root. Permissions of the camera device is the same like the permissions of a standard logitech camera: crw-rw----+ 1 root video, the desktop user belongs to...
<cy8aer>
... the video group. Are there any hints or is there something still missing in the kernel?
<cy8aer>
mbp14/m1pro
<lina>
eiln: Good thing I added the version to the m1n1 side ^^
<lina>
Should be easy to fix then!
<lina>
And that makes sense since 12.4 didn't support any machines where high IOVAs are used
bgb has quit [Quit: WeeChat 4.0.5]
<lina>
cy8aer: We support a lot of resolutions on those machines, including vertical ones... maybe Firefox/jitsi is unhappy with that?
<lina>
Can you try some webcam test sites?
<cy8aer>
lina ok, I'll do some webcam test sites...
<lina>
Depending on what Firefox is doing exactly, we might be able to change the logic in the driver to prefer some resolutions, or hide the weird vertical ones behind a module argument if they cause too much trouble
<mps>
cy8aer: guvcview have few resolutions to test
<mps>
I tested some last night
<lina>
If too much stuff is broken with extra resolutions we can just limit the 1080p cameras to 1920x1080p only for now, that's a simple device tree change.
<lina>
Also I didn't technically test any of this on m1pro/max, I just assumed the resolutions are the same as on m2pro/max since they use the same sensor... but it could be wrong.
<lina>
1080p should definitely be correct though
<cy8aer>
I now tried de.webcamtests.com and that works fine Resolution 1920x1080 FHD. There the browser does not make problems. I will now play around with guvcview
systwi has joined #asahi-dev
dcow has joined #asahi-dev
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has joined #asahi-dev
dcow has quit [Ping timeout: 480 seconds]
chadmed has quit [Remote host closed the connection]
chadmed has joined #asahi-dev
<cy8aer>
Ok, guvcview works with every tested resolution. But with jitsi I do not know what there is happening. I tried it with chromium and there the video is shown in diagonal stripes. Probably they want 720p
<cy8aer>
(found that somewhere in the page source)
<cy8aer>
1280x720 is not offered in guvcview
<cy8aer>
Ok, I got jitsi running, but: I am hosting my own jitsi server. And by default there is defined: prefered 720p, min 240p, max 720p! I set max resolution to 1080p and it worked. This may be a solution for me, but because max is 720p by default there should be 720p offered somehow.
Yannik_Sc has joined #asahi-dev
dcow has joined #asahi-dev
Yannik_Sc has quit [Remote host closed the connection]
Yannik_Sc has joined #asahi-dev
dcow has quit [Ping timeout: 480 seconds]
<janneg>
eiln: yes, very grainy
<janneg>
lina: can you push the m2 tracer to a branch? I have a partial port with fixed mailbox/doorbell offsets but that wasn't enough
<janneg>
do we know if the imac uses the same sensor as the m1 pro/max macbooks? it has a 1080p sensor
Yannik_Sc has quit [Ping timeout: 480 seconds]
dcow has joined #asahi-dev
dcow has quit [Ping timeout: 480 seconds]
<eiln>
janneg: I'd be really surprised if it wasn't. do any of us have an imac to test? I've never even seen one in the wild
<janneg>
marcan has or has access to one and I can get access to one as well. I can't remember seeing an user with an imac. the telemetry might tell us how many users with imacs we have
dcow has joined #asahi-dev
bgb has joined #asahi-dev
dcow has quit [Ping timeout: 480 seconds]
Yannik_Sc has joined #asahi-dev
<eiln>
didn't the imac have some weirdo audio codec? on second thought it might be a different sensor
<chadmed>
eiln: both
<chadmed>
i think we have a driver for the codec now though
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]