00:16 <clover[m]> what is that

01:12 <derzahl> steev: is there a repo of either individual or bundled together c630 patches that could just be applied to the vanilla kernel?

01:13 <steev> derzahl: you can always clone mine, and then apply them?

01:13 <steev> that is what my repo is?

01:14 <steev> clover[m]: it's something important to getting the gpu working (this is on the c630, where it was working and somehow has broken)

01:19 <steev> if you mean just the patches.... no? i mean, no offense but it's kinda dumb

01:19 <steev> why maintain a directory of patches instead of maintaining a git repo

01:19 <steev> or even better, maintain a git repo of patches... made from a git repo

01:24 <clover[m]> <steev> "clover: it's something important..." <- that's aggravating

01:25 <derzahl> sorry, my gitfu isnt stellar

01:25 <derzahl> i know how to take textfiles and apply them with the 'patch' command

01:26 <steev> git am ~= patch

01:26 <steev> as long as it's git formatted

01:26 <steev> added bonus that you get history, and more importantly, keep attribution

01:28 <derzahl> IIRC there seems to be multiple people making commits to your repo

01:28 <steev> no

01:28 <steev> those are the original authors

01:29 <steev> that's kinda the point. if there's a bug in a patch, you go to the author, not the committer

01:29 <steev> but if you really just want a directory full of patches

01:30 <derzahl> not sure if they are done with pull requests but i know I can those and add .patch to the url and get a text download

01:30 <derzahl> oh gotcha

01:31 <steev> if you have done git clone github:steev/linux.git -b linux-5.19.y; inside that linux directory, run git format-patch -o patches d654f7e29909ce602942a1cd927d56d5aa397ed8..HEAD

01:31 <steev> that will spit out the 206 or so patches that are applied

01:31 <derzahl> oh cool

01:31 <steev> i'm still not sure why you'd choose to do that over downloading each file individually, but i'd highly *highly* recommend learning git

01:32 <derzahl> whats the magic command to rip them all off and nail them on to a new kernel?

01:32 <steev> "Rob Clark authored and 0x011011110 committed 16 days ago" - that's saying rob wrote the patch, i just committed it to my repo

01:32 <steev> uhh

01:33 <steev> assuming you're using git

01:33 <steev> git am /path/to/patches/*.patch

01:33 <steev> and then fix them up as they break

01:34 <steev> in terms of what i do, well, the stable kernel is my origin, so i just git pull --rebase, which pulls in the latest 5.19 and then applies my patches on top of it

01:34 <steev> it also means patches automatically get dropped when they're committed to the repo, so again, i don't have to track them manually

01:35 <derzahl> oh, but you dont have a /path/to/*patch files if you do it the proper way through git right?

01:35 <derzahl> oh yeh

01:35 <derzahl> thats what i meant

01:36 <steev> so assuming you want to do what i did... well you'd take that folder of patches "we" just generated via git format-patch, and you'd git clone <upstreamkernelurl> -b linux-5.19.y; then go into the directory, and git am /path/to/patches/*.patch; and then you'd just git pull --rebase whenever they put out a new 5.19 kernel

01:37 <steev> and yes i just noticed that i've not pushed anything since 5.19.1

01:37 <steev> that's because i'm trying to dump the some-battery stuff and move to bamse's real driver

01:38 <steev> actually, i'm trying to make a c630 specific one, sc8180x specific one, and sc8280xp specific one

01:38 <derzahl> ok, so you are still working with a bunh of .patch files then.

01:38 <derzahl> i misunderstood

01:39 <derzahl> i just noticed the battery driver and enabled it but then the compile failed

01:40 <derzahl> im still on 5.17

01:40 <steev> you're gonna need to backport some stuff to make it work on 5.17

01:42 <derzahl> id just compile 5.19 with gcc before that

01:43 <derzahl> probably

01:43 <derzahl> i finally got 5.17 to compile with lto AND zfs and it all worked

02:53 <steev> unfortunately, if you want the battery/dp driver, you need the drm stuff to be backported as well

02:53 <steev> you might be able to go in and modify it to only be the battery, but i haven't bothered

20:51 <steev> looks like the thermal keeps things at ~80C

20:51 <steev> compiling and occasionally it hits 82-83C but definitely isn't going up to 90 anymore