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