17:52 <si1v3r> Any word on broken peachpit boots since april 1st?

17:53 <daniels> si1v3r: hmm, not sure why peach-pit isn't tracked in kernelci, but peachpi at least boots just fine, and i'm pretty sure javier had pit working ok too

17:54 <daniels> si1v3r: at least on linux-next - which tree are you using?

17:54 <si1v3r> My last attempt was mainline rc7

17:55 <si1v3r> Just wondering if the fixes to the wifi regulator issue (I believe) landed.

17:55 <daniels> ah okay, not quite sure what 'since' means in that context then - try linux-next

17:55 <daniels> some fixes didn't make it in time for 4.0

17:55 <si1v3r> Ok, so I'll be testing 4.1 rcs then

17:56 <daniels> i'd recommend just trying linux-next if you want something that works now

17:56 <si1v3r> linuxnext-20150405 was I think tagged as rc4 and that worked for me.

17:56 <daniels> as peach-pi is tracked in kernelci.org, it should be quite stable in that regressions instantly get noticed

17:56 <daniels> http://kernelci.org/boot/exynos5800-peach-pi/

17:56 <si1v3r> I've got the lil one, not the big one.

17:58 <si1v3r> Anyway, I was just wondering. I lost my source for the last working kernel I made (rc4) due to overenthusiastic partition kerpoofing so now I'm waiting for the next working version to continue playing with it.

17:58 <daniels> right, but pi and pit are really very similar

17:58 <si1v3r> yes they are

17:59 <daniels> javier also uses a pit, and i'm pretty sure that was working fine with -next, at least when he went on holiday on fri

17:59 <si1v3r> ok, I'll try another build tonight then.

21:18 <amitk> /quit