cc___ has quit [Ping timeout: 248 seconds]
harut has quit [Ping timeout: 246 seconds]
qwazix has joined #neo900
hexamod has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hexamod has joined #neo900
preview has quit [Ping timeout: 240 seconds]
hexamod has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
xmn has quit [Quit: Leaving.]
Kabouik- has quit [Ping timeout: 248 seconds]
chomwitt has quit [Ping timeout: 246 seconds]
ArturShaik has joined #neo900
knttl has quit [Ping timeout: 240 seconds]
knttl has joined #neo900
hexamod has joined #neo900
hexamod has quit [Client Quit]
hexamod has joined #neo900
infobot has quit [Ping timeout: 240 seconds]
hexamod has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
_whitelogger has joined #neo900
pigeons_ is now known as pigeons
harut has joined #neo900
ravelo has joined #neo900
preview has joined #neo900
hexamod has joined #neo900
hexamod has quit [Client Quit]
ecloud_wfh is now known as ecloud
ravelo has quit [Quit: Connection closed for inactivity]
Kabouik has joined #neo900
jonsger has joined #neo900
ArturSha1 has joined #neo900
luke-jr has quit [Ping timeout: 248 seconds]
lukedashjr has joined #neo900
ArturShaik has quit [Ping timeout: 240 seconds]
lukedashjr is now known as luke-jr
lukedashjr has joined #neo900
luke-jr has quit [Ping timeout: 248 seconds]
lukedashjr is now known as luke-jr
chomwitt has joined #neo900
ossguy has joined #neo900
cc___ has joined #neo900
xmn has joined #neo900
__Chris has joined #neo900
Chris_ has quit [Ping timeout: 248 seconds]
jonsger has quit [Ping timeout: 246 seconds]
ravelo has joined #neo900
louis_ has joined #neo900
infobot has joined #neo900
silviof1 is now known as silviof
threebar has joined #neo900
Pali has joined #neo900
louis_ has quit [Ping timeout: 248 seconds]
louis_ has joined #neo900
pagurus has joined #neo900
Kabouik has quit [Ping timeout: 248 seconds]
pagurus` has quit [Ping timeout: 240 seconds]
<Joerg-Neo900> [2017-11-10 Fri 05:51:33] <pabs3> "An update on the Android problem" https://lwn.net/SubscriberLink/738225/28d2098ce220b2ee/ [2017-11-10 Fri 16:53:41] <DocScrutinizer05> wow, and HAHA yeah! >>Greg Kroah-Hartman started by saying that he has been working for some time with the system-on-chip (SoC) vendors to try to resolve this problem, which he blames primarily on Qualcomm for having decided not to work upstream. Qualcomm has since concluded
<Joerg-Neo900> that this decision was a mistake and is determined to fix it, but the process of doing so will take years. The other SoC vendors are also committed to closing the gap between the kernels they provide and the mainline but, again, getting there will take a while.<<
<Joerg-Neo900> btw the approach of SoC manufs providing kernels instead of proper datasheets for community to develop true FOSS kernels based on that info, that's so radically wrong I fail to appreciate it in my rants
louis_ has quit [Ping timeout: 248 seconds]
louis_ has joined #neo900
ArturSha1 has quit [Ping timeout: 240 seconds]
hexamod has joined #neo900
Kabouik- has joined #neo900
hexamod has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hexamod has joined #neo900
rofl_ has joined #neo900
jcarpenter2 has quit [Ping timeout: 260 seconds]
hexamod has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hexamod has joined #neo900
hexamod has quit [Client Quit]
* enyc meows
<Joerg-Neo900> the problem starts earlier: with tivoization (locked bootloaders, forbidding reflashing with unsigned software images) and hardware manufs not providing proper datasheets/schematics. When you got a complex circuit for e.g. battery management (let's assume it been made from a Silego GP5 mixed signal matrix 'FPGA' and a few analog components like regulators, current limiters, thermosensors and so on) then it doesn't matter if the manufacturer
<Joerg-Neo900> provides the software needed to make that stuff work in form of a userland closed blob or a customized kernel driver or even upstreams their drivers to mainline kernel. Nobody will really be able to do anything about that "gibberish" even when plan C sourcecode, since the datasheets and schematics for the hardware are missing so a FOSS sw developer could understand *what* to do about the code and *how* it's actually supposed to work. Pretty
<Joerg-Neo900> much exactly same for GPUs where the drivers are worth nothing even in FOSS sourcecode when you don't have decent docs about how the internal gear in the GPU actually works. Same for cameras and you-name-it
xmn has quit [Ping timeout: 248 seconds]
<Joerg-Neo900> in the article linked above - and the comments there - some folks insinuate that such lockdown like tivoization was a regulatory requirement for phones. That's BS, it's not. Only the modem's radiostack is really subject to FCC et al approval
<Joerg-Neo900> it's a pity that guys like Kroah-Hartman and Torvalds seemingly fail to understand this
<Joerg-Neo900> sn0wmonster: hint: this ^^^ is pretty much related to the "security" topic
sicelo has joined #neo900
<Joerg-Neo900> btw the Librem5 is following exactly same broken approach of providing their "own firmware" which despite they explicitly claim willingness to upstream stuff to mainline, is worth nothing since they obviously cannot (or don't want to) provide the schematics and datasheets for their hardware
<Joerg-Neo900> ok, a FOSS driver makes it easier to RE the hardware, but it's only gradually different in its brokenness, while the correct approach would be to provide schematics and datasheets first and only on next lower priority provide some software reference implementation demonstrating how to use the hardware *in a limited selection of operation modes* (no sw implementation ever can cover *all* operation modes of hardware, only the datasheets +
<Joerg-Neo900> schematics can do this)
silviof has quit [Changing host]
silviof has joined #neo900
<atk> Joerg-Neo900: do you think it's possible to get the binary graphics blobs for the n900 working on the mainline?
<atk> Joerg-Neo900: also, I remember you were once giving out a link to some instructions for "what to do when you get a used n900"
<Joerg-Neo900> atk: yes, I think TI's "gfx blob" stuff as they provide it on their website should compile on mainline kernel, maybe after a few patches
<atk> cool
<Joerg-Neo900> a link to "what to do with a used N900" was possibly a link to #maemo chanlog - I don't think there's a concise comprehensive web page covering that
<Joerg-Neo900> you may try
<Joerg-Neo900> ~jrtools
<infobot> i guess jrtools is http://wiki.maemo.org/User:Joerg_rw/tools
<Joerg-Neo900> not exactly geared to the topic, but might help
<atk> re graphics: any link you could give me to that? *tries googling "TI gfx blob for n900"*
<Joerg-Neo900> mompls
<atk> I'll have a look
<Joerg-Neo900> "TI SGX toolkit" or somesuch
<atk> yes, I found that too
<atk> the wiki page claimed that no registration was required
<atk> and what a load of bullshit that was
<atk> wait no, it's on a js alert, I clicked the wrong button
<atk> it really is no registration required!
<atk> although it looks like this is an installer.... I guess I'll have to binwalk it so that I can avoid "installing" things over my pristine filesystem
harut has quit [Ping timeout: 250 seconds]
louis_ has quit [Read error: Connection reset by peer]
<Joerg-Neo900> actually I think somebody "leaked" the complete PowerVR software sourcecode, just the FOSS community rejects to use leaked copyrighted code
harut has joined #neo900
<Joerg-Neo900> atk: about "what to do when you get a used n900" please ask in #maemo, there are a few nice folks willing to help
<atk> cool
<Joerg-Neo900> for a start:
<Joerg-Neo900> ~lazyflashing
<atk> Joerg-Neo900: what do you think of postmarketOS?
<atk> (I'm considering helping them get the hwaccel working for the n900 so I can eventually maybe help port the rest of the n900 stuff onto a more recent kernel and set of libraries
<atk> they have hildon UI working but it's slow because of the lack of hwaccel
<Joerg-Neo900> I didn't look into postmarketOS, so I can't really comment on it
<atk> I see
<Joerg-Neo900> a quite unfortunate side effect of Neo900 UG - I hardly have any spare time and energy for following other aspects of mobile phones or anything
<atk> how's the prototype going anyway?
<Joerg-Neo900> metacollin had a family obligation last 5 weeks, so not much progress.
<Joerg-Neo900> he'll prolly be back next few days
<Joerg-Neo900> that's the downside of tiny projects like this one: so many "single points of failure", basically every single person is such
<Joerg-Neo900> in a larger project you wouldn't even notice when one engineer catches the flu or otherwise isn't available for a few weeks
<atk> I've caught the plague myself
<atk> or something
rofl_ is now known as jcarpenter2
hexamod has joined #neo900
ossguy has quit [Quit: leaving]
hexamod has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hexamod has joined #neo900
hexamod has quit [Client Quit]
hexamod has joined #neo900
hexamod has quit [Client Quit]
hexamod has joined #neo900
hexamod has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hexamod has joined #neo900
hexamod has quit [Client Quit]
Kabouik_ has joined #neo900
Kabouik- has quit [Ping timeout: 240 seconds]