ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<Dylanger>
Anyone know if the EC can reflash the SPI/Depthcharge/Coreboot?
<Dylanger>
I'd like to compile Depthcharge myself and bypass the whole "Dev Mode Enabled" screen
<Dylanger>
I've configured the EC to drop it's guards
<Dylanger>
Guessing this is the definition for the internal SPI
<Dylanger>
`[ 3.755542] spi-nor spi12.0: gd25lq64c (8192 Kbytes)` kernel sees it
<Dylanger>
amstan: I should prob set it up like this
<Dylanger>
Incase I do mess up
<Dylanger>
Cheers
<Dylanger>
Have you managed to compile depthcharge?
<Dylanger>
Lol wish me luck
<Dylanger>
I'll dump the SPI Flash first
<Dylanger>
So I can always just recover
<Dylanger>
I want to headshot the developer nag
<Dylanger>
And I've always wanted to fully control the BL on a device
<Dylanger>
Wouldn't mind changing the PON sequence
<Dylanger>
Guessing that'd be EC
<Dylanger>
Actual EC
<Dylanger>
PON Button -- EC yeah?
<Dylanger>
God I love that Google do that ❤️
<Dylanger>
Homestar
<Dylanger>
Good luck ever finding source for x86 based ECs
<robclark>
amstan: are you not identified w/ NickServ.. I kinda assume Dylanger isn't talking to themselves but I only see one half of the conversation ;-)
<Dylanger>
lol, yeah you need to identify every few weeks
<Dylanger>
Kinda annoying
* robclark
has seen other funny one-sided conversions with matrix users :-P
amstan has left #aarch64-laptops [#aarch64-laptops]
<Dylanger>
Nickserve needs to identify you iirc
amstan has joined #aarch64-laptops
<robclark>
amstan: ok, I see you now: `→ amstan joined (~amstanhyp@2001:470:1af1:101::70f6`
amstan has quit [Quit: Reconnecting]
amstan has joined #aarch64-laptops
<amstan>
yay?
<amstan>
robclark: ok, this channel's setup a little weird i would say
<amstan>
i've been in here for weeks did not even realize i can't talk to anyone
<robclark>
I'd blame that on someone else, but it is probably my fault
<amstan>
i mean, yes i guess i could have seen nickserv yelling at me, but that's like 3 nickservs i have in my list i have to worry about now, lol
<amstan>
i would prefer if it was +r (so you can't even join the channel), would have been way more obvious
<Dylanger>
If you haven't identified with NickServ, everyone on Matrix could hear you, but no one in IRC would be able to, it'll randomly force you to redo it every few weeks
<amstan>
i never had a nickserv account on oftc it turns out
<amstan>
so i guess that explains why nobody here would reply to me except Dylanger , lol
<amstan>
Dylanger: so yeah, if i were you and wanted to customize things a lot: I would leave the ap firmware alone (gbb flag will get your white screen pretty short)
<amstan>
ec firmware is easy to compile and play with in isolation since it's only one git tree, so it should be easy there to modify things
<amstan>
for custom ecs you have to either disable software sync or roll your ec version into the ap firmware
<Dylanger>
Okay, I'll need to get up a whole cros environment
<amstan>
that probably qualifies as "sc7180-qc_blobs", and if it's on github i'm sure there's already a cros_sdk thing that grabs it for you
<amstan>
but i'm saying there might be repos in my list that you don't even have access to
<amstan>
gone are the days of rk3288 where everything there was open source, lol
<amstan>
meanwhile libreboot only has a release for that one chromebook, rk3288, that's already fully open source
<Dylanger>
I kinda wanna just try change a string, and flash it
<Dylanger>
See if it freaks out
<amstan>
it won't
<amstan>
well....
<amstan>
you can change everything in RO, in RW, RO might care (but idk if that happens before or after it realizes it's in dev mode and doesn't care anymore)
<amstan>
I doubt there's CRCs or any other crypto verification in RO
<Dylanger>
amstan: Let's see
<amstan>
anyway, as i said earlier, AP firmware is too much of a PITA to modify it, especially since gbb flags do what i mostly care about to boot the thing, after it boots i couldn't care less about how it looks
<amstan>
ec firmware on the other hand is a different world
iivanov__ has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
pg12_ has quit [Ping timeout: 480 seconds]
gwolf has quit [Ping timeout: 480 seconds]
gwolf has joined #aarch64-laptops
pg12 has joined #aarch64-laptops
broonie has quit [Read error: Connection reset by peer]
broonie has joined #aarch64-laptops
broonie has quit [Remote host closed the connection]
broonie has joined #aarch64-laptops
robher has joined #aarch64-laptops
macc24_ has joined #aarch64-laptops
calebccff_ has joined #aarch64-laptops
pg12_ has joined #aarch64-laptops
macc24 has quit [charon.oftc.net helix.oftc.net]
pg12 has quit [charon.oftc.net helix.oftc.net]
amstan has quit [charon.oftc.net helix.oftc.net]
martijnbraam has quit [charon.oftc.net helix.oftc.net]
calebccff has quit [charon.oftc.net helix.oftc.net]