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
jacobk has joined #linux-amlogic
naoki has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
camus has quit [Ping timeout: 260 seconds]
camus has joined #linux-amlogic
camus has quit [Quit: camus]
camus has joined #linux-amlogic
hexdump0815 has quit [Ping timeout: 258 seconds]
hexdump0815 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
jacobk has quit [Ping timeout: 260 seconds]
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 272 seconds]
jacobk has joined #linux-amlogic
chewitt has joined #linux-amlogic
<narmstrong> I’m not surprised, it’s a trend in the industry, it’s cool
ldevulder has joined #linux-amlogic
Daanct12 has joined #linux-amlogic
<f_> sighs
<f_> >Licensee [...] shall not, directly or indirectly, reverse engineer, decompile or disassemble
<f_> any portion of the Object Code (or attempt to do so).
<f_> Clean-room reverse-engineering it is then?
mripard has joined #linux-amlogic
Daanct12 has quit [Quit: WeeChat 4.0.5]
Daanct12 has joined #linux-amlogic
psydroid has joined #linux-amlogic
<f_> narmstrong: seems like X4 AO CPU firmware isn't proprietary?
<narmstrong> Yep but it’s not the scp cpu, it’s an additional core to run rtos stuff like voice detection
<narmstrong> In the datasheet it’s said there’s one on the G12 SoCs but I never found anything about it
<f_> damn confusing
<narmstrong> It’s probably broken
<f_> I wish I never read that amlogic SLA for sc2
<f_> It specifically says that you're not allowed to RE their proprietary blobs...
<f_> SC2 boot makes no sense anyway
<f_> BL2X??????
<f_> BL2E??????????????????
<f_> I'll keep by g12 and older, thanks.
<f_> s/by/my/
<f_> hopefully they ruminate on the idea once they discover a weirdo reverse-engineering their blobs (which they won't...yet)
<f_> (won't discover I mean..please keep this secret lol)
<f_> But I guess we could try to "bypass" that restriction by doing clean-room reverse-engineering?
<f_> I hate having to do clean-room RE
psydroid has quit [Quit: Leaving]
psydroid has joined #linux-amlogic
<f_> gxl hacking time.
ldevulder has quit [Quit: Leaving]
<f_> One thing that bugs me out..what in the world is BL40?
<narmstrong> ???
<narmstrong> why do they invent such things ?
<f_> Am asking myself the same question
<phh> narmstrong: X4 AO CPU does handle stuff that used to be in Cortex-M, like CEC, BLE, RTC wakeup reasons
<f_> hm
<narmstrong> sure
<f_> Where's the SCP firmwate then?
<f_> *firmware
<f_> bl40
<narmstrong> rofl
ldevulder has joined #linux-amlogic
* f_ suddently rolls on the floor
<f_> Amlogic world is funny sometimes.
<phh> I have a documentation that says BL40: "SECPU firmware"
<phh> glhf with that
<f_> hmm
<phh> oh wait, it always says that SECPU: Secure CPU
<f_> Seeing how amlogic calls SCP, 'Secure Co-Processor'
<f_> so it might be the SCP firmware or something else
<f_> phh: which docs BTW?
<phh> f_: not public ones. I maybe shouldn't mention that here
<f_> datasheet I guess.
<f_> But sure.
<f_> I still wonder why Amlogic keeps hiding important documentation..
<phh> yeah, I often wish I would just work on rockchip devices
<f_> which purpose does a device serve when you don't even know how to use it?
<phh> well you can use it using software provided by amlogic...
<f_> Software that's of course proprietary...
<f_> bundled with a hacked up old U-Boot and linux
<phh> with a lot of proprietary blobs in userspace
<f_> Indeed.
<f_> message-id not found.
<narmstrong> f_: now do the spl counterpart and we're done
<narmstrong> it will arrive in a few seconds
<f_> Ah there we go.
<f_> Awesome
<f_> would have been nice to cc me too
<narmstrong> oops sorry
<f_> It's no problem
<f_> >Personal: cannot create messages outside the Drafts mailbox
<f_> Thanks ProtonMail..
<f_> let's see if I mess up the In-Reply-To header
<f_> Am tempted to rebase my tree once this gets merged
<f_> narmstrong: not very familiar with kernel review
* f_ looks up kernel review
<narmstrong> the final goal is to be able to test u-boot and/or linux on some boards that are not flashed with a bootloader, so I'll be able to use the same setup to test u-boot and linux, great success \o/
<f_> with U-Boot SPL \o/
<narmstrong> i'll need to add a secondary boot binary to the "abcd" tool so when the dfu appears after u-boot, it can load and continue
<f_> What's abcd?
<narmstrong> and yes I'll be able to ci test the spl with dfu
<f_> one very stupid question..when can someone use Acked-by or Reviewed-by?
<narmstrong> it's a fork of cdba tool we use for qcom devices but with pyamlboot https://github.com/starnux/abcd
<narmstrong> both are equal
<narmstrong> acked-by would signify it's ready to go for the maintainer if you're a reviewer of the platform
<narmstrong> in your case it would mean both, perhaps it could mean "i review and acknowledge it"
<f_> but I'm not a reviewer of the platform
<mkorpershoek> everyone can review, not only maintainers
<narmstrong> yep it's open
<f_> So I could add a Reviewed-by tag and it would be fine?
<narmstrong> yes
<mkorpershoek> yep, if you indeed did your best reviewing it :)
<f_> yeah that was what wasn't clear to me
<f_> It says Acked-by isn't formal
<f_> so I guess if I understood correctly Acked-by means 'LGTM' and Reviewed-by means 'did my best reviewing it and didn't find issues'
<mkorpershoek> I think so. I honestly don't use/understand Acked-by so much
<narmstrong> yep, both can be considered as reviewed-by, but acked-by with an unformal LGTM message
<narmstrong> some people attached a great difference to acked-by, I don't
<f_> Did my email arrive?
<f_> Nice to see in-reply-to got messed up ONCE AGAIN
jacobk has quit [Ping timeout: 240 seconds]
<f_> At this point is protonmail removing that header?
<narmstrong> I got it, weird, anyway lore is smart enough to link it to the original patchset
<f_> hmm seems like aerc didn't send it...
<f_> Should probably add a Tested-by there too
<f_> (after testing
<f_> )
naoki has quit [Quit: naoki]
Daanct12 has quit [Quit: WeeChat 4.1.0]
jacobk has joined #linux-amlogic
<narmstrong> sure
jacobk has quit [Ping timeout: 260 seconds]
ldevulder has quit [Quit: Leaving]
mripard has quit [Ping timeout: 240 seconds]
buzzmarshall has joined #linux-amlogic
jacobk has joined #linux-amlogic
f_[xmpp] has joined #linux-amlogic
<f_> >if you don't know how to config, then don't edit it
<f_> bl33/board/amlogic/g12b_w400_v1/firmware/timing.c
<f_> am looking at that file quickly..
<f_> too bad there aren't dumps of register like on older SoCs..these dumps made reverse-engineering much easier :)
<f_> (a little easier..)
<f_> hmm seeing how there are scripts to build e.g. bl31 I wonder if manufacturers have access to BL2 code..
jacobk has quit [Ping timeout: 260 seconds]
<f_> Seeing how amlogic is innovating I bet there will be a bl50 and bl60, as well as bl70, bl80, bl90, and finally bl100.
* f_ suddently starts rolling on the floor...
<narmstrong> blinfinite !
jacobk has joined #linux-amlogic
<phh> well, there is first a funnier one, BL4
<phh> (yes in addition to BL40)
<phh> BL4 is Secure CPU's bootrom
kenny has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
psydroid has quit [Quit: On my way to get myself one of those extremely juicy Threadrippers]
<f_> BL5, BL6, BL7, BL8, BL9, BL10, BL65535!
<f_> Innovative Amlogic.
Danct12 has left #linux-amlogic [A-lined: This user has been AViVA-lined!]
Danct12 has joined #linux-amlogic