narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
djrscally has quit [Ping timeout: 244 seconds]
vagrantc has quit [Quit: leaving]
hexdump0815 has quit [Ping timeout: 272 seconds]
hexdump0815 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
djrscally has joined #linux-amlogic
<f_> hexdump0815: maybe. Would be great if it's the case, A311D has pretty good support in mainline :)
ldevulder has joined #linux-amlogic
ldevulder has quit [Ping timeout: 245 seconds]
ldevulder has joined #linux-amlogic
jacobk has quit [Ping timeout: 260 seconds]
jacobk has joined #linux-amlogic
chewitt has joined #linux-amlogic
<f_> oooh.. Now that was completely unexpected
<f_> I think I might have an idea regarding on what foss firmware Amlogic's bl30 is based on
<f_> but not 100% sure
<f_> I noticed some stuff it outputs to UART look similar to what cros_ec would output? Somehow Amlogic could've retrofitted it for their SCP?
<f_> Only way to make sure is to feed it to ghidra and diff/compare :)
<f_> If that is true it might make reversing it easier as then all I/we/you/etc need to do is reverse-engineer amlogic's changes, and no need to care about the rest :D
<f_> Being able to boot with no proprietary boot firmware running on the AP is a nice achievement, but I'd argue being able to boot with no proprietary boot firmware *at all* would be much more awesome
<f_> If no one gets to reversing BL30 before me, I could try.. but I said I was going to reverse g12b BL2 before, so SCP fw reversing will be later for me
<f_> that said running stuff on the SCP ought to be pretty straightforward. I think even on secureboot-enabled devices the SCP firmware doesn't actually do encryption/signing checks and such
<f_> at least it did not complain at all when I loaded an old s805y bl30 from some random u-boot repo along with an old lepotato bl301
<f_> on the secureboot-enabled Mi TV Stick
<f_> So I'm fairly confident no checks are being ran on bl30 by the SCP
<f_> which kinda makes sense.. BL2 and BL1 are the ones doing all the rest of the checks, and in theory that would not allow you from running your own firmware at all.. unless there was a vuln in one of these two
<f_> chewitt: noticed it yeah, did not read it though
<f_> Hmm.. some of these specs are similar to some amlogic SoC I've seen before
<f_> interesting
<chewitt> It looks overall similar to the SM1 boards; except for AV1 support, so I suspect it's closer to S4 .. the article says the same
<chewitt> I think V901D just proves their marketing team uses /dev/random for naming input :D
<f_> I'm sure V is the first letter of "car" in some other language so not completely /dev/random :D
<f_> but what in the world is up with 902/905/912/805/812 numbers
<chewitt> they lost the plot with those a long time ago
<f_> Okay, amlogic bl30 might be based upon cros_ec-v1.1.0
naoki has quit [Quit: naoki]
psydroid2 has joined #linux-amlogic
ldevulder has quit [Ping timeout: 252 seconds]
ldevulder has joined #linux-amlogic
<f_> I could not resist
<f_> I opened bl30 in ghidra to take a look
<f_> version v1.1
<chewitt> another piece of the jigsaw :)
<f_> :D
<f_> if anyone wants to stare at it feel free!
jacobk has quit [Ping timeout: 248 seconds]
chewitt has quit [Quit: Zzz..]
buzzmarshall has joined #linux-amlogic
buzzmarshall has quit [Ping timeout: 276 seconds]
ldevulder has quit [Ping timeout: 268 seconds]
jacobk has joined #linux-amlogic
vagrantc has joined #linux-amlogic
<f_> regarding the HDMI boot dongle, it looks like a vendor can choose to disable it completely apparently.
<f_> They can choose to also disable USB boot entirely. Though that is kind of separate
<f_> Separate as in, if the HDMI boot dongle detection is enabled and USB is disabled, and a hdmi boot dongle is plugged in, it will go to USB mode
<f_> But under no other circumstances will it reach that mode
<f_> you can {dis,en]able it by blowing efuses. I'll push some docs about those in a bit
buzzm has joined #linux-amlogic
jacobk has quit [Ping timeout: 276 seconds]
ldevulder has joined #linux-amlogic
<f_> And yep, secureboot does not imply AES encryption
<f_> at least not in the bootROM's POV.
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-amlogic
<f_> > Obfuscate UART logs
<f_> :D :D :D
<f_> *security by obscurity intensifies*
<f_> Luckily only a few zte devices have that enabled
<narmstrong> f_: oh it may explain those task thing they also use in bl301
<narmstrong> what a weird base to use
ldevulder has quit [Ping timeout: 244 seconds]
montjoie has quit [Ping timeout: 244 seconds]
montjoie has joined #linux-amlogic
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 248 seconds]
djrscally has quit [Quit: Konversation terminated!]
djrscally has joined #linux-amlogic
jacobk has joined #linux-amlogic
<f_> narmstrong: yeah, but cros_ec has cortex-m support so there's that ;p
<f_> it probably would've been better to just use Arm-Software/SCP-Firmware
<f_> Anyway, that was just out of curiosity while I randomly saw a chromebook's EC logs and thought to myself, "hey that looks familiar!"
<f_> s/while/when/
jacobk has quit [Ping timeout: 260 seconds]
djrscally has quit [Quit: Konversation terminated!]
djrscally has joined #linux-amlogic
naoki has joined #linux-amlogic
psydroid2 has quit [Quit: KVIrc 5.2.6 Quasar http://www.kvirc.net/]
djrscally has quit [Quit: Konversation terminated!]
djrscally has joined #linux-amlogic
djrscally has quit [Client Quit]
vagrantc has quit [Quit: leaving]