#
…

2022-02-04

00:01jmr2 has joined #asahi
00:02jmr2jeffmiw: are you starting from scratch, or from Corellium's ?
00:03yuyichao has quit [Ping timeout: 480 seconds]
00:25yuyichao has joined #asahi
01:14jmr2 has quit [Quit: Page closed]
01:19nirgo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
01:27chadmed has joined #asahi
02:40jbowen has quit [Ping timeout: 480 seconds]
02:54balrog has quit [Ping timeout: 480 seconds]
03:00bmrgz[m] has quit [Server closed connection]
03:01bmrgz[m] has joined #asahi
03:01balrog has joined #asahi
03:29lewurm has quit [Server closed connection]
03:29lewurm has joined #asahi
03:35jx0 has joined #asahi
03:49kov has quit [Quit: Coyote finally caught me]
03:51allegorie[m] has quit [Server closed connection]
03:51allegorie[m] has joined #asahi
03:52kov has joined #asahi
04:01TomHobson[m] has quit [Server closed connection]
04:01PhilippvK has joined #asahi
04:01TomHobson[m] has joined #asahi
04:02threerik[m] has quit [Server closed connection]
04:02threerik[m] has joined #asahi
04:04phiologe has quit [Ping timeout: 480 seconds]
04:14LorenzKofler[m] has quit [Server closed connection]
04:14LorenzKofler[m] has joined #asahi
04:21drwhax[m]1 has quit [Server closed connection]
04:21drwhax[m]1 has joined #asahi
04:32jbowen has joined #asahi
04:36hspak has quit []
04:37hspak has joined #asahi
04:38oi_wtf has quit [Server closed connection]
04:38oi_wtf has joined #asahi
04:38as400[m] has quit [Server closed connection]
04:38as400[m] has joined #asahi
04:40latko[m] has quit [Server closed connection]
04:40latko[m] has joined #asahi
04:41jbowen has quit [Ping timeout: 480 seconds]
04:41l3k[m] has quit [Server closed connection]
04:41l3k[m] has joined #asahi
04:42Sebhl[m] has quit [Server closed connection]
04:42Sebhl[m] has joined #asahi
04:46dsrt^ has joined #asahi
04:49_jannau_ has quit [Server closed connection]
04:49_jannau_ has joined #asahi
05:09RianSouzaSantos[m] has quit [Server closed connection]
05:09RianSouzaSantos[m] has joined #asahi
05:13jonnymac[m] has quit [Server closed connection]
05:13jonnymac[m] has joined #asahi
05:34st3g4n0[m] has quit [Server closed connection]
05:34st3g4n0[m] has joined #asahi
05:44Rhys[m] has quit [Server closed connection]
05:45Rhys[m] has joined #asahi
05:50jelly has quit [Server closed connection]
05:53mini has quit [Server closed connection]
05:54mini has joined #asahi
06:00jelly has joined #asahi
06:05SteffanKaragianis[m] has quit [Server closed connection]
06:05SteffanKaragianis[m] has joined #asahi
06:16Glanzmannjeffmiw: I look forward to it.
06:17Glanzmannmarcan[m]: Is the SMC stuff already ready for general testing?
06:19bradfier has quit [Server closed connection]
06:19bradfier has joined #asahi
06:20mattmurr[m] has quit [Server closed connection]
06:21mattmurr[m] has joined #asahi
06:23jeffmiwGlanzmann: I looked at what kettenis did for openbsd and Corellium, and then try to come up with something
06:25riker77 has quit [Server closed connection]
06:25riker77 has joined #asahi
06:30David[m]12345678 has quit [Server closed connection]
06:30David[m]12345678 has joined #asahi
06:32Glanzmannmarcan[m]: Do I see it correctly that the SMC driver currently does only provide the interfaces and now the consumers like wifi driver need to use it, to power on its power. Or the watchdog driver to turn off the power of the system?
06:32GlanzmannAnd I think theere was one guy writing a library so that we can use it to get the battery information?
06:32ogimgd[m] has quit [Server closed connection]
06:33ogimgd[m] has joined #asahi
06:33jbowen has joined #asahi
06:38chadmedGlanzmann: i think his question was more to do with why we need it on these machines, not what the SPMI actually _is_
06:38chadmedi.e. what specifically do we need to talk to over SPMI
06:41jbowen has quit [Ping timeout: 480 seconds]
06:42jx0 has quit [Quit: poof!]
07:08jeffmiw has quit [Ping timeout: 480 seconds]
07:17eroux has joined #asahi
07:39joske has joined #asahi
07:39joskemarcan: smc/work doesn't compile?
07:41joskeforgot a ; after EXPORT_SYMBOL on line 133
07:49joskemarcan: and after that fix, fails to link: https://pastebin.com/SrpC1DAC
07:51joskeexporting wrong symbol on line 69
07:51joskewith those 2 fixes it compiles
07:52hellsenberg has joined #asahi
07:54joske has quit [Quit: Leaving]
07:55hell__ has quit [Ping timeout: 480 seconds]
08:09marcanI think I never tested module mode :)
08:09marcansince I have modules disabled EXPORT_SYMBOL probably compiles out
08:10marcanGlanzmann: no
08:10marcanthe SMC driver is not currently hooked up to pcie
08:10marcanso that needs to happen before it's useful
08:14landscape15[m]@_oftc_joske:matrix.org: do you get that compiling ```Image modules dtbs```? Because for me seems to work without compiling modules
08:15kholtastrophe[m] has quit [Server closed connection]
08:15kholtastrophe[m] has joined #asahi
08:18Bicet[m] has quit [Server closed connection]
08:18Bicet[m] has joined #asahi
08:24alexstore06[m] has quit [Server closed connection]
08:24alexstore06[m] has joined #asahi
08:27wollymilkcap[m] has quit [Server closed connection]
08:27wollymilkcap[m] has joined #asahi
08:28BlazinWeed[m] has quit [Server closed connection]
08:28BlazinWeed[m] has joined #asahi
08:33jbowen has joined #asahi
08:33landscape15[m]Glanzmann: For debugging purpose, I would add to enable CONFIG_USB_ANNOUNCE_NEW_DEVICES in Asahi docs. When I have time I try the latest patches and inform you.
08:34sppdqd[m] has quit [Server closed connection]
08:35sppdqd[m] has joined #asahi
08:35josipknezovic[m] has quit [Server closed connection]
08:35josipknezovic[m] has joined #asahi
08:41jbowen has quit [Ping timeout: 480 seconds]
08:55Major_Biscuit has joined #asahi
09:29Glanzmannlandscape15[m]: Add whatever you think is useful. I just started the list because so often people (including me) forgot to set a config option and as a result something was not working.
09:38landscape15[m]ok thanks, I’ll do
09:42Glanzmannchadmed / DmitrySboychakov: IIRC jeffmiw has a userland programm to query different smc values, but maybe that was someone else.
09:43j`eyit was joske, but it's for macOS
09:54NotHere[m] has quit [Server closed connection]
09:54NotHere[m] has joined #asahi
09:54JamieMagee[m] has quit [Server closed connection]
09:54JamieMagee[m] has joined #asahi
09:54M32thSystem[m] has quit [Server closed connection]
09:55M32thSystem[m] has joined #asahi
09:55citruscitrus[m] has quit [Server closed connection]
09:55citruscitrus[m] has joined #asahi
09:56cangurbuz[m] has quit [Server closed connection]
09:56cangurbuz[m] has joined #asahi
09:56elosant[m] has quit [Server closed connection]
09:57elosant[m] has joined #asahi
09:57ytg has quit [Server closed connection]
09:57ytg has joined #asahi
09:58isitaboat[m] has quit [Server closed connection]
09:58isitaboat[m] has joined #asahi
09:59lemonsus[m] has quit [Server closed connection]
09:59lemonsus[m] has joined #asahi
10:03dsrt^ has quit [Remote host closed the connection]
10:03dsrt^ has joined #asahi
10:03rethematrix[m] has quit [Server closed connection]
10:03rethematrix[m] has joined #asahi
10:04long[m] has quit [Server closed connection]
10:04long[m] has joined #asahi
10:04matthewayers[m] has quit [Server closed connection]
10:04matthewayers[m] has joined #asahi
10:04Santiago[m]1 has quit [Server closed connection]
10:05Santiago[m]1 has joined #asahi
10:05yoodee[m] has quit [Server closed connection]
10:05yoodee[m] has joined #asahi
10:07GenieLotion[m] has quit [Server closed connection]
10:07GenieLotion[m] has joined #asahi
10:07ryanhrob[m] has quit [Server closed connection]
10:07ryanhrob[m] has joined #asahi
10:08roxiun[m] has quit [Server closed connection]
10:09roxiun[m] has joined #asahi
10:11dsrt^ has quit [Ping timeout: 480 seconds]
10:11dsrt^ has joined #asahi
10:16essentia[m] has quit [Server closed connection]
10:16essentia[m] has joined #asahi
10:17Glanzmannj`ey: Thank you, I see.
10:18fionera[m] has quit [Server closed connection]
10:18fionera[m] has joined #asahi
10:18nirusu[m] has quit [Server closed connection]
10:19nirusu[m] has joined #asahi
10:19dsrt^ has quit [Ping timeout: 480 seconds]
10:21ghantaz[m] has quit [Server closed connection]
10:21ghantaz[m] has joined #asahi
10:22why2[m] has quit [Server closed connection]
10:22why2[m] has joined #asahi
10:22sproede[m] has quit [Server closed connection]
10:22sproede[m] has joined #asahi
10:22angustrau[m] has quit [Server closed connection]
10:23angustrau[m] has joined #asahi
10:23dek[m] has quit [Server closed connection]
10:23dek[m] has joined #asahi
10:23haterade[m] has quit [Server closed connection]
10:23haterade[m] has joined #asahi
10:24nykma[m] has quit [Server closed connection]
10:24nykma[m] has joined #asahi
10:25Rhys[m] is now known as Rhys[m]1
10:25Rhys[m]1 is now known as Rhys[m]12
10:25cavoirom[m] has quit [Server closed connection]
10:25cavoirom[m] has joined #asahi
10:25Rhys[m]12 has quit [Quit: Reconnecting]
10:25Rhys[m]12 has joined #asahi
10:25gladiac has quit [Quit: Ping timeout (120 seconds)]
10:25gladiac has joined #asahi
10:33jbowen has joined #asahi
10:39mlq_ has quit [Server closed connection]
10:40mlq_ has joined #asahi
10:41jbowen has quit [Ping timeout: 480 seconds]
10:43chadmedSMC isnt connected over SPMI though is it?
10:46svenit's just yet another co-processor running rtkit
10:52yrlf has quit [Server closed connection]
10:52yrlf has joined #asahi
10:59Glanzmannj`ey: cat /sys/class/power_supply/macsmc-battery/capacity is this exposed by default when you enable smc or did you had to enable something?
11:00j`eyGlanzmann: I just wrote a little driver for it, dunno if I will keep working on it though
11:02Glanzmannj`ey: git-format-patch -1; and upload please, if you don't mind. :-)
11:03GlanzmannI'm looking forward to the patch that enables wifi. That gives untethered access to Jens Axboe. ;-)
11:03j`eyGlanzmann: maybe if i work on it a bit more, it was just a quick test for now
11:04GlanzmannAnd having Jens running Linux on m1 can't hurt.
11:04j`eynext stop: linus
11:05suricato has quit [Server closed connection]
11:06suricato has joined #asahi
11:09mpsSMC is merged?
11:10mpsor it is somewhere else?
11:10j`eyjust pushed to a branch, but there's no interation, so nothing to test
11:13mpsj`ey: which branch?
11:13j`eysmc/work
11:13mpsaha I see, thnaks
11:14mpss/thnaks/thanks/
11:25hellsenberg is now known as hell__
11:32JoshuaAs- has quit [Server closed connection]
11:32JoshuaAshton has joined #asahi
11:46coolshaurya has quit [Server closed connection]
11:46coolshaurya has joined #asahi
11:54joske has joined #asahi
11:54joskej`ey: I'm also interested in that 'little driver' ;-)
11:54joskeI built smc/work, but I didn't have that file, now I know why ;-)
11:56mpsjoske: are patches for keyboard needed on top of smc/work
11:57j`eysmc/work is just a few patches on top of the asahi branch, so if you had some of the spi and w/e patchs, theyre still needed
11:58kettenisin its current state smc/work doesn't really add anything useful for end-users
12:00joskemps: yes
12:00joskeaudio too
12:00joskeI noticed that audio took a while to initialize
12:00joskeand wifi didn't work
12:03j`eyjoske: wifi didnt work.. did you have it working before on asahi/asahi?
12:04joskerunning on wifi now ;)
12:04joskerunning the asahi branch with the input/audio and 4k patches
12:05joskethis is on an air
12:09nsklausjoske: you mentionned audio input, i thought it was only audio out until now, does audio in starts working too ?
12:09j`eyinput meaning keyboard
12:09chadmedhe means input as in keyboard
12:09nsklausah i see
12:11nsklausit's nice keyboard and trackpad got in, once more step toward a base system beta release of asahi
12:12jato has quit [Server closed connection]
12:12jato has joined #asahi
12:12chadmedkb and touchpad have been in linux-asahi for a little while now actually
12:12chadmedi believe some cleanup is required before its upstreamable though
12:13nsklauswe poor users didn't get to know about it until recently..
12:13* nsklauspoint finger at wiki task list and blog's progress reports lacking a bit behind
12:13j`eycomplaining wont make them happen quicker :P
12:14chadmedit was in the last blog post, written in early december
12:14chadmedand the wiki has had it listed as supported since at least i edited tasks and wrote Feature Support
12:14nsklausi admit i prefer git commits gets in before news articles commenting on them
12:15_jannau_it should have been inthe november blog post. My understanding of the task list that task are done when they are in the upstream kernel
12:15j`eyhopefully spi, input and wifi can be in for 5.18, that would be a decent amount of patches from linux/asahi
12:15nsklausi'm just a bit sad that once the job got done, there's no hurry to share the joy to the rest of the world
12:15_jannau_at least for linux kernel driver
12:16j`eynsklaus: but it's not at the point where it's easy to use, so not much point in sharing!
12:16j`eyonce it's in mainline is the best point to share
12:16nsklausbut i agree, the main thing is the job getting done, and that is what is being done, so that's good ..
12:17chadmednsklaus: https://github.com/AsahiLinux/docs/wiki/%22When-will-Asahi-Linux-be-done%3F%22 while i did write this mostly for my own leisure, it makes a cogent point
12:18Retr0id3 has joined #asahi
12:18Retr0id has quit [Remote host closed the connection]
12:18Retr0id3 is now known as Retr0id
12:18chadmedthe driver being committed to linux-asahi doesnt mean its ready for announcing to the world, or for wide user adoption. we've been testing it and it "works" but it spams dmesg about CRC errors from the trackpad. if it got announced for all to come in and use, we would be flooded with 10 quadrillion github issues about it i guarantee you
12:19nsklausyou understand this article you wrote out of noticing many users out there are asking for news and you feel it's a (minor form) of nuisance. instead of writing such article telling users not to ask, best would be to keep news up to date with commits and general progress then point users to those up to date news article
12:20nsklaus*articles
12:20nsklausif twitters post or wiki was up to date, all you would have to do is point everyone to the same link
12:21nsklausyou could even put the link in the channel topic and that would be the end of the story
12:21chadmedi think developer time is better spent developing than writing puff pieces for the amusement of impatient users who cant be bothered reading the wiki. features will be announced and added to Feature Support/Tasks when they are supported. that is your "regular updates"
12:21nsklausit's because developer write verbose articles
12:22nsklausit's nice, but most user just wish to see the tasklist items being checked, or now they are being worked on
12:22chadmed1) people have better things to do than log each and every commit on twitter, 2) the wiki is up to date because i spent most of the past week ensuring that, 3) there is a link to the wiki in the channel topic
12:22anon2022[m] has quit [Server closed connection]
12:22anon2022[m] has joined #asahi
12:22nsklauswhere is smc in the task list ?
12:22nsklaussee my point ?
12:23leah has quit [Server closed connection]
12:23chadmedyouve already been told things get checked off on the task list when they are upstreamed. the smc driver has not yet been upstreamed and its not even *useful* for *anything* yet
12:23leah has joined #asahi
12:23leah is now known as Guest1763
12:24nsklausyes, but that's just because that tasklist item is not reflecting one element of progress, it keeps track of what has been done and cleared, and not what is being worked on
12:24chadmedwould you expect, for example, a game developer to announce that a game is "done" or ready for consumption the minute their engine compiles? no, because an engine that compiles with nothing attached to it is not a game, and its utterly useless to gamers
12:24nsklausyou are correct of course
12:25matthewayers[m]nsklaus: The wiki also mentions that it isn’t the best idea to ask about this kind of stuff in IRC because it will likely lead to a headache.
12:25nsklausthat's why i said tasklist is missing keeping track of the 'in progress' stuffs
12:26matthewayers[m]Again, a lot of people are working on a lot of things and time is better spent working on the project itself instead of documenting every bug fix as it happens.
12:26chadmedimo keeping track of "in progress" stuff invites people to test stuff that isnt ready, which leads to them spamming bug reports for stuff developers already know about. especially when here, "in progress" could mean anything from "it works but a race condition on boot means that 30% of the time it wont start" to "well we know what writing 1s to 0xf00 does"
12:26nsklausi could take care of bugging devs to get a statement of what they are doing and keep tasklist up to date with it, if you wanted, that should keep it off your shoulders
12:27chadmedwell no see my point is the devs dont want to be bugged for statements. things are announced and released when theyre ready.
12:28chadmedagain, i updated the wiki specifically to avoid these sorts of conversations polluting IRC
12:28chadmedits pretty easy to parse, "dont ask us when things will be done, and here is why"
12:29nsklausthen it's normal ppl ask for news, if you think it's better to leave them in the dark with partial info, for example last progress report is from november, asahi twitter last post is from december, last youtube vid is from +2 weeks ago, etc .. after some time pass by with no fresh news people start to get hungry and wonder what's happening. seems logical and to be expected
12:30mpsnsklaus: heh, I read few addresses with i2c tools and saw some bits and bytes and that is some kind of progress but I wouldn't call it 'work in progress'
12:30j`eynsklaus: yeah but also be patient, 2 weeks isnt that long time in reality!
12:32nsklausi agree 2 weeks is not that long, and this project is generally doing good, i agree asking for patience in this context is quite ok. people just are getting interested and want linux on M1 for yesterday :)
12:32chadmedi think its important to understand that not telling people about every single successful register poke or gpio pull up is pretty good practice. users typically dont understand the significance of such efforts (and is why we have to write long winded articles explaining them) and assume that no work is being done on ${IMPORTANT_FEATURE}
12:33jbowen has joined #asahi
12:34nsklausthere could be a reasonable middle ground between teeling everyone when a register gets successfully poked at and a more general sense of what is being worked on with the project at current time
12:34chadmedlike what looks better to a user? going away for two/three/four weeks and coming back with firefox playing out of the builtin speakers? or bit banging a 1kHz beep to the speaker amp from m1n1?
12:37blasty has quit [Server closed connection]
12:37blasty has joined #asahi
12:37chadmedthe reasonable middle ground is what happens now. nifty/cool advancements are announced on twitter (e.g. marcan showing off plasma on the macbook pro) and the wiki is updated when those things are ready for people to test/use. its fine how it is. youre the only person who has complained this much
12:38nsklausmore high level general statement: as in: povik works on audio. so far audio out through jack works on all hardware, he's currently working on speaker out and audio in. work is in progress. update on this statement will be made as soon as there will be a relevant progress achieved. stay tunned.
12:39chadmedthat was already announced via the blog post.
12:40chadmedyou see what i mean? stuff like that is announced when its ready to be announced. just because you feel like it's actually ready _now_ does not make that so.
12:40nsklausyou see, a one or two line statement per feature being supported, a general, high level report, it would provide a good sense of what is happening. no need for a super verbose review that take days to be made, and wasting too much time
12:41nsklausyes i know that was announced
12:41flying_sausages has quit [Server closed connection]
12:41chadmed yeah so read Feature Support. every feature is literally one line in a table. cant get more succinct than that
12:41jbowen has quit [Ping timeout: 480 seconds]
12:42chadmedand it provides you a good sense of whats happening because features that are actually at a stage where theyre ready to be announced to the world are listed as supported in some capacity.
12:42nsklausi just used it as example to give an image of small, time efficient form of report, that let everyone knows what's going on, without wasting dev time too much
12:42flying_sausages has joined #asahi
12:43j`eythe short form is that feature support wiki, the long form is the blog post
12:44nsklausmarcan reviews blog article are a very nice to read, but they are a bit overkill and it's easy to understand doing them is a pain and wasting his time quite a bit and so since they are like that he's not happy about doing them
12:44nsklaushence they drag behind
12:44j`eyis that what he said? or just what you think?
12:44nsklausit's what i think of course
12:45j`eyanyway, you can want what you want, but you'll get what you get!
12:45nsklausmaybe he like doing them. i wouldn't. i'd prefer short 1 or 2 line per feature. quick 15mn to 30mn to do an overall report
12:45viljami[m] has quit [Server closed connection]
12:45viljami[m] has joined #asahi
12:46nsklausas a dev i'd view creating verbose, lengthy report as a pain
12:46chadmedok yeah so read the wiki. theres no point in anyone writing any "reports" when theres nothing to actually report
12:46chadmedthe fact that we can poke the smc is totally irrelevant to anyone who would actually read such a user-targeted "report"
12:47chadmedwhen the smc is actually useful in linux, i will update the wiki. its not though.
12:48chadmed"oh yeah every time you wanna check your battery you have to do run a bunch of commands as root, also it doesnt actually do half of the other stuff we need it to do yet!" is not worthy of a progress report. its silly.
12:48nsklausi have said what i wanted and provided suggestions to give more frequent, less verbose report. you'll do as you please of course. the decision was always yours (all the devs).
13:05nsklauspersonaly i'd go through every member of the team once a week, and ask for a general statement (high level, layman terms) of progress and i'd post just that somewhere online (wiki or blog or twitter whatever). that way news report would always be up to date.
13:16kaprests has quit [Server closed connection]
13:16kaprests has joined #asahi
13:29matthewayers[m]Sorry, but that’s a big ask for this kind of project. A lot of people do this for free and it’s taxing enough as it is. Check feature support or subscribe to the blog for updates, infrequent as they may be, because that’s the best way to figure out what’s going on without learning how the sausage is made.
14:03nsklausi was not saying that if a dev has nothing new to give as a weekly statement of progress they would get punished or anything ;)
14:04nsklaussome statements could be valid for weeks, even a month.. if longer then that would indicate the task could be breaked into smaller bits though, but that's up to the dev itself to decide if he knows what he's doing
14:07nsklausmaybe after 6months if statement never change, then probably time to wonder what's going on with that dev though but that would be about it. i bet most dev would have a little something to say once a week. noone require them to provide "earth shattering revolutionary breakthrough splitting the atom" statement of progress every week..
14:08sventhis is not a company, if you want weekly progress reports from me you better pay me damn well for it.
14:08nsklaussven you don't understand you're already providing those.
14:08svenyes, i do understand.
14:08nsklausi'm just talking about organizing them through a schedule
14:09sven<sven> this is not a company, if you want weekly progress reports from me you better pay me damn well for it.
14:10nsklausyou're already proving those, and you didn't ask for anything special, or didn't felt offended or such. if anything with my way of doing it, you'd be asked less often and would have to provide those less often
14:11svenno, the point is that i don't want to be asked about progress
14:11sveni'll share whatever whenever i see fit and I won't change that
14:11j`eycan we just move on, we understand your point, but it's unlikely to happen in the way you want, since it's happening in the way te people doin the work want
14:11nsklausyou'll be asked anyway
14:12nsklaussven: i mean, not by me of course, but by everyone gravitating around this project, users poping in the channel, or on twitter, etc ..
14:12svensee what j`ey said
14:12j`eysven: so youre saying we need to get your boss interested in asahi, so we can force you to give status updates >:D
14:12svenj`ey: :D
14:13nsklauspeople and logic ..
14:15matthewayers[m]I’ve taken 5 courses in the last year about logic in various contexts… math, computer science, linguistics, and digital circuits. I feel like I could give an attorney a run for his/her money given the right context
14:16j`eyif the context is boolean logic, sure :P
14:27mpslogic comes from logos and no one actually knows what *is* logos :)
14:33jbowen has joined #asahi
14:36yuyichao has quit [Ping timeout: 480 seconds]
14:38eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:42jbowen has quit [Ping timeout: 480 seconds]
14:47artemist has quit [Quit: artemist]
15:03nirgo has joined #asahi
15:07jbowen has joined #asahi
15:15artemist has joined #asahi
15:18joske has quit [Quit: Leaving]
15:29mpstrying to build smc/work and got this `drivers/platform/apple/smc_core.c:135:1: error: expected ';' before 'struct' 135 | struct apple_smc *apple_smc_probe(struct device *dev, const struct apple_smc_backend_ops *ops, void *cookie)`
15:32j`eymps: build it builtin or add a ; to the end of line 136 and make line 66 export the right symbol
15:32mpsah `EXPORT_SYMBOL(apple_smc_get_key_count)` missing ;
15:33M1bn3mar[m]hey every one :)
15:34mpsj`ey: line 66 is empty?
15:34j`eymps: sorry 72
15:35mpsj`ey: you mean line `EXPORT_SYMBOL(apple_smc_write);`?
15:35j`eyyeah, should be apple_smc_rw
15:36mpsj`ey: thanks
15:37M1bn3mar[m]hey, im new 2 this how could i compile asahi linux?
15:39mpsM1bn3mar[m]: git clone, add some patches and build, Glanzmann have some short guide which patches are needed, so not much complicated if you have experience with building kernels
15:40M1bn3mar[m]mps: ok, thanks
15:58M1bn3mar[m]mps: hey didn't find the video, i searched youtube & lbry
16:01mpsM1bn3mar[m]: I think Glanzmann have text file on some url but I don't have this url at hand now
16:02mpswill look later
16:03M1bn3mar[m]mps: ok, thank u, looking forward I'm really excited about this XD
16:03M1bn3mar[m]* looking forward 4 that I'm really
16:07mpsM1bn3mar[m]: https://tg.st/u/asahi.txt but not sure is that still correct
16:08M1bn3mar[m]mps: yes, thank u so much
16:09M1bn3mar[m]it even mention's an end user's guide, I
16:10M1bn3mar[m]* guide, I'm getting enthusiastic about this : )
16:10mpsj`ey: did you got internal keyboard working with smc/work branch
16:14j`eymps: yes it just worked, smc/work only added the smc drivers, the rest is identical to the normal asahi branch
16:15mpsj`ey: hmm which patch you used for keyboard?
16:15mpsj`ey: do you have url
16:16mpsI built smc/work but keyboard doesn't work so I missed patch for it
16:16mpsj`ey: thank you
16:20mpsj`ey: these two patches needs refactoring I think
16:20mpsdoes they apply cleanly for you
16:21j`eyI actually applied the second one manually since I tested it before jannau committed it
16:21j`eybut the first should at least apply cleanly?
16:22j`eyhopefully they can just be included in the next asahi update
16:22mpsagree, they should be added
16:23mpsalready refactored second now have to look at first, one hunk failed
16:24mps(but have to work now on $day_job)
16:27mpsj`ey: my bad, I applied them in reverse order, both are fine
16:27_jannau_I don't see how they can not apply cleanly. they are based on top of https://github.com/AsahiLinux/linux/commits/bits/090-spi-hid and modify only files which are created in that branch
16:28_jannau_ah, I see
16:28mps_jannau_: my bad
16:32mpsfine it works
16:32mpswhat is needed to read battery
16:33mpssome kernel .config drivers?
16:33j`eythose drivers arent there yet
16:35mpsI see this added GPIO_MACSMC
16:53LaurentiuCosma[m] has joined #asahi
16:56yuyichao has joined #asahi
16:58Gaspare has joined #asahi
17:54Major_Biscuit has quit [Ping timeout: 480 seconds]
18:07mpsI got this in dmesg output `macsmc-rtkit 23e050000.smc: error (____ptrval____): No SRAM region`
18:08mpsand `macsmc-rtkit: probe of 23e050000.smc failed with error 5`
18:08mpsdoes that means that some modules or options are not enabled in kernel config?
18:10kettenisprobably means your dtb is not up to date
18:10mpskettenis: so I have to build new m1n1+u-boot?
18:10kettenisas I tried to point out earlier today, there is nothing really on that branch yet for users to test
18:11mpskettenis: I don't expect it working 'out-of-the-box', just wanted to look at status
18:12ketteniscompare the smc node in the device tree you're using with what marcan has in that tree
18:24mpst8103.dtsi is different
18:24kettenisof course it is
18:25mpsand small change in t8103-jxxx.dtsi
18:27mpskettenis: do you plan to sync these
18:27kettenisI'm tracking the asahi branch
18:28mpsaha, ok
18:28kettenisso once the stuff marcan is working on shows up there, I'm going to adjust things
18:29mpsthanks for explaining
19:24m6wiq has joined #asahi
19:41malvo has quit [Ping timeout: 480 seconds]
21:30landscape15[m]I have a doubt. After installing a kernel module, do I need to compile the kernel with ```make modules``` or ```make modules_install```?
21:32mpslandscape15[m]: if you installed module you don't need to build it or I don't understand question
21:38landscape15[m]mps: I mean together with kernel Image compiling, ```make Image modules dtbs```
21:38mpslandscape15[m]: right, this is for build and after that make modules_install
21:40mpslandscape15[m]: here is my script which I run to build all in tarball https://tpaste.us/YEOe
21:40mpscould be of use
21:40mpsthis is how to add needed packages before building on alpine linux
21:42landscape15[m]ok thanks, then I made it right. So modules_install should be used only if I’m using external modules I guess
21:42psykoseit installs the things tagged with =m in kconfig
21:44landscape15[m]Does this mean also the Broadcom WiFi module?
21:44mpslandscape15[m]: no, make modules_install is to install modules in kernel thres
21:44mpss/thres/tree/
21:45mps`modules_install` is section in kernel Makefile
21:47landscape15[m]mps: yeah, in theory every compiled module should be installed by modules_install
21:47mpslandscape15[m]: and in practice
21:47landscape15[m]s/should/is/, s/be//
21:48landscape15[m]Also in practice :)
21:50landscape15[m]I was in doubt because I still couldn’t make USB working with my .config. Everything else seems to work fine.
21:50mpsif you build new module for already running kernel you need `modprobe $module_name` after make modules_install
21:51mpsand `depmod -a` before that probably
21:51landscape15[m]mps: yeah I used it to install my Ethernet dongle driver
22:05Gaspare has quit [Quit: Gaspare]
22:11Deewiant has joined #asahi
22:27null has quit [Server closed connection]
22:27null has joined #asahi
22:35j`ey has quit [Server closed connection]
22:35j`ey has joined #asahi
22:49malvo has joined #asahi
23:07Glanzmann has quit [Server closed connection]
23:44m6wiq has quit []
23:49mps has quit [Server closed connection]
23:49mps has joined #asahi
23:54yuyichao has quit [Ping timeout: 480 seconds]
…