<Pali>
"All am35xx GPs have the SHAM and AES modules except some very old ones."
<Pali>
which means that there are some TI GP devices with AES hw support
<DocScrutinizer05>
sounds about correct then, yes
<DocScrutinizer05>
if I hadn't already closed the relevant TRM pages in my reader, I'd look up the relevant bits in config registers and read them out from processor
<DocScrutinizer05>
well, I would if I had a working OS image on a uSD for BB-xM
<DocScrutinizer05>
when you think about it, it makes not much sense TI building _two_ different chips, one for GP and one for HS. If I were do build those OMAP3, I'd simply fuse to death the HS features for my GP series
<DocScrutinizer05>
prolly GP simply has a few according commands in ROMBOOT that disable and hide the HS stuff
<Pali>
do you know what is timer12?
<Pali>
timer@48304000
<DocScrutinizer05>
sorry no
<Pali>
reg = <0x48304000 0x400>;
<Pali>
it is disabled on omap3 hs devices
<DocScrutinizer05>
o.O
<Pali>
in DT file
<Pali>
also in hwmod
<DocScrutinizer05>
disabled on *HS*?
<DocScrutinizer05>
so it must cause a threat to the whole TrustZone thing
<DocScrutinizer05>
or cause malfunction when using it in HS mode
<DocScrutinizer05>
maybe something about profiling?
<Pali>
"On secure devices the 12th timer is reserved for secure usage and so cannot be used by the kernel, where as for a GP device it is available."
<wpwrak>
looks like a case of a complex system failing (or maybe not ?) in a messy and incomprehensible way
<DocScrutinizer05>
two things attract my suspicion: dhclient in there, and the completey out-of-sync timestamp 2015-02-18T09:15:01.951233+01:00
<bencoh>
I think you worry too much about a broken by design piece of software :)
<DocScrutinizer05>
I do since it's on my system - which is bad enough
<bencoh>
I'd tell you to move to devuan, but you wouldnt be able to ask for info on their channel :>
<DocScrutinizer05>
yeah
<wpwrak>
why, does the bouncer only let you in if you have a 50+ cm white beard ?
<DocScrutinizer05>
no, a sucker banned me
<DocScrutinizer05>
for qurstioning his ban of a complete IP subnet
vakkov has quit [Ping timeout: 264 seconds]
<DocScrutinizer05>
channel owner told me in query "we need to do sth about this whole topic" but that's been it
<DocScrutinizer05>
[BanList:#devuan] *!*@openmoko/engineers/joerg set by ChanServ on 2015-01-28 Wed 16:49
<DocScrutinizer05>
by *chanserv*, aka /akick
<DocScrutinizer05>
no sane chanop using akick
<DocScrutinizer05>
rationale why this guy did: "I want to establish bans that no other chanop can revert" - OMG
<DocScrutinizer05>
what for he needs other chanops (+o) then, anyway?
<kerio>
you don't understand veterans
<wpwrak>
we need that on a t-shirt :)
<DocScrutinizer05>
this is no veteran, this looks like a noob and allegedly is very young, according to chan owner
<DocScrutinizer05>
when you don't want somebody to do - or undo - bans on your channel, you don't accesslist +o him, neither +b. When you need somebody to do minor "chan moderator" tasks like changing topic (+t) or giving voice (+v) to other chan users, you set accesslist flags accordingly
<bencoh>
DocScrutinizer05: just ask chanowner to revert that
<DocScrutinizer05>
bencoh: I did, chan owner answered "we need to do sth about that. But later, busy now". Last I heard of him
<bencoh>
meh
<DocScrutinizer05>
(very young) his IRC account is 10 years old though
<bencoh>
haha
<DocScrutinizer05>
which seems doesn't help to grok how IRC chan admin works
<bencoh>
compared to a veteran vax admin maybe :>
<bencoh>
note my irc account is 7yo and I'm "only" 25yo as well, so ...
<bencoh>
s/irc/freenode/
<wpwrak>
if devuan doesn't want you, maybe try openbsd. i've heard they have pretty decent security. you'll have to set theo right on some things, but i'm sure he'll be appreciative of any constructive input.
<DocScrutinizer05>
anyway, I offered to forget about it and keep up support and contribution to #devuan and the project, if they feel like rethinking this mad ban. Chan owner said we will take care. He didn't
<bencoh>
wpwrak: is it friday yet ? :D
<wpwrak>
bencoh: almost :)
<DocScrutinizer05>
wpwrak: I'm not going to change OS just to get rid of poettering malware
<Wizzup>
wpwrak: or freebsd, which is more advanced than openbsd
<bencoh>
I wouldnt exactly say "more advanced" on every aspect
<DocScrutinizer05>
[2015-02-18 Wed 16:09:21] [Notice] -NickServ- Information on coagen (account coagen):
<DocScrutinizer05>
please help me out, too many names
<DocScrutinizer05>
I guess googling won't help
Kabouik has quit [Ping timeout: 250 seconds]
jake42_ has joined #neo900
sixwheeledbeast^ has joined #neo900
Kabouik has joined #neo900
jake42 has quit [Ping timeout: 245 seconds]
sixwheeledbeast has quit [Ping timeout: 245 seconds]
quatrox has joined #neo900
che11 has quit [Remote host closed the connection]
<Pali>
just to note: omap AES, SHA and MD5 HW support is enabled for all GP devices by linux kernel
<Pali>
no idea if this is bug or feature
<Pali>
just fact
<Pali>
and DISABLED for all HS devices (because it cause L3 firewall error and kernel crash -- on devices where bootloaders does not enable that HW support)
<Pali>
DocScrutinizer05: it is easy to check if bbmx board has support for AES. just load kernel driver omap-aes.ko
<Pali>
and check dmesg log for errors :D
xray256 has joined #neo900
xray256 has quit [Client Quit]
xray256 has joined #neo900
xray256 has quit [Quit: WeeChat 0.3.7]
paulk-collins has quit [Quit: Quitte]
vakkov has quit [Ping timeout: 250 seconds]
<Pali>
systemd-fsckd
<Pali>
this is not a joke
<Pali>
another stuff in systemd
<DocScrutinizer51>
Pali: coherent. when mounting then also fsck
<Pali>
yes fsck+mount should be one action
<Pali>
but why systemd-fsckd as separate?
<DocScrutinizer51>
no idea
<DocScrutinizer51>
I just hate it redhat hijacks linux
<DocScrutinizer51>
whitehat grayhat blackhat redhat. now it starts making sense
<kerio>
illuminati confirmed
<DocScrutinizer51>
what's next? steelhat? asshat?
<DocScrutinizer51>
skinhat
vakkov has joined #neo900
<kerio>
systemd-linux
<DocScrutinizer51>
System D
<DocScrutinizer51>
forget linux
<DocScrutinizer51>
D like demolition
<kerio>
or like dong
<kerio>
( ͡° ͜ʖ ͡°)
<DocScrutinizer51>
long dong silver?
<DocScrutinizer51>
...was a hoax
<DocScrutinizer51>
maybe somebody should tell poettering
<bencoh>
23:57 < Pali> systemd-fsckd
<bencoh>
wtf
<bencoh>
and ... how comes I *always* learn about it from Pali ? :D
<Pali>
systemd-fscks is invention from canonical, not red hat
<bencoh>
:/
<Pali>
>>> [00:35:11] <DocScrutinizer51> maybe somebody should tell poettering <<< no, maybe canonical people do not tell this plan to poettering..
<Pali>
:D
<bencoh>
or ... poettering fanboys are hiding in Canonical and lurking in the dark
<bencoh>
cant be too sure these days
<DocScrutinizer05>
I thought when he knows it was a hoax, he suffers less inferiority complex so doesn't need to compensate with monstrous systemd
<DocScrutinizer05>
kerio: btw kudos for this fontset
<kerio>
which fontset
<DocScrutinizer05>
͜ʖ ͡° etc
<DocScrutinizer05>
whatevr it is
<kerio>
k
<DocScrutinizer05>
incredible kerning
<DocScrutinizer05>
and it renders on opensuse konversation and on maemo xchat ;-)