IRC log for #openmoko-cdevel on 20180905

00:23.28*** join/#openmoko-cdevel apt (ibot@208.53.50.136)
00:23.28*** topic/#openmoko-cdevel is Please /join #openmoko | Openmoko Community Developers Channel - discussion on all firmware images, packages and software | SHR: http://shr-project.org | #hackable1 | #openmoko-debian | #qtmoko | #android-on-freerunner | CIA notifications in #freesmartphone.org | Logs: ~logs & http://logs.nslu2-linux.org/livelogs/openmoko-cdevel.txt
00:23.28*** mode/#openmoko-cdevel [+v apt] by ChanServ
01:10.55*** join/#openmoko-cdevel paulk-leonov (~paulk-leo@leonov.paulk.fr)
01:24.30*** join/#openmoko-cdevel PaulFertser (~paul@paulfertser.info)
01:54.14*** join/#openmoko-cdevel _Chris_ (~Chris@p5DE1A3A1.dip0.t-ipconnect.de)
01:57.45*** join/#openmoko-cdevel _Chris_ (~Chris@p5DE1A3A1.dip0.t-ipconnect.de)
02:58.13*** join/#openmoko-cdevel morphis (~morphis@p200300CCFBEF7000D6C5E6B5B8F349E9.dip0.t-ipconnect.de)
03:53.46pabs3https://puri.sm/posts/2018-09-librem5-hardware-roadmap-announcement/
03:53.51pabs3https://puri.sm/posts/librem5-2018-09-hardware-report/
04:10.55*** join/#openmoko-cdevel PaulFertser (~paul@paulfertser.info)
04:46.41*** join/#openmoko-cdevel pabs3 (~pabs3@unaffiliated/pabs3)
05:05.14pabs3so purism are putting the modem on the USB bus
05:06.08pabs3seems like a terrible idea to me, it could emulate a USB keyboard
05:48.38*** join/#openmoko-cdevel Q-Master^Work (~q-master@217.175.38.170)
05:53.11*** join/#openmoko-cdevel ao2 (~ao2@host196-141-dynamic.10-87-r.retail.telecomitalia.it)
07:01.00*** join/#openmoko-cdevel cheapie9 (~cheapie@156.212.207.168)
07:01.02*** mode/#openmoko-cdevel [+q *!*@*156.212.207.168] by Donnager
07:02.06*** mode/#openmoko-cdevel [-q *!*@*156.212.207.168] by Donnager
09:34.00*** join/#openmoko-cdevel pespin_ (~Sharwin_F@93.176.183.48)
09:47.00*** join/#openmoko-cdevel patinux (~patinux@unaffiliated/patinux)
10:22.17*** join/#openmoko-cdevel morphis (~morphis@p200300CCFBEF7000D6C5E6B5B8F349E9.dip0.t-ipconnect.de)
10:51.25DocScrutinizer05pabs3: it's the only feasible way. And you of course need a dedicated USB interface3 for the modem, and you do NOT allow any HID on that particular USB bus
10:52.49DocScrutinizer05>>it could emulate a USB keyboard<< sure, but your system is free to ignore usch USB keyboard on that bus
10:52.58DocScrutinizer05such*
10:56.11DocScrutinizer05pabs3: refer Neo900, we already sorted *all* this
10:57.25DocScrutinizer05ideally you'd want modem on HSI interface, but... no modem module offers HSI afaik
11:06.55DocScrutinizer05there are quite a few problems you're facing with using USB interface for modem, like power consumption of the mere USB PHY, then USB suspend+resume or alternatively the time it needs to ENUM on "power up" aka "plug in". Last not least the actually not THAT fast 480Mbit/s max bandwidth.of USB2. But pripheral forging a keyboard and system idiotically and ignorantly accepting and using that as a legit input device for sure isn't
11:06.57DocScrutinizer05one of them problems. Also see how a kbd is input / ingress but for sure a very poor output / egress channel for any sort of attack
11:09.55DocScrutinizer05pabs3: makes sense?
11:17.28DocScrutinizer05but Purism is really awesome, they know about how to do one thing absolutely outstandingly right: 'sell' common knowledge and trivialities as their own remarkable new ideas and breakthrough in phone design
11:20.16DocScrutinizer05the whole paragraph about modem in https://puri.sm/posts/librem5-2018-09-hardware-report/ could be copied from early musings in Neo900 of a 5 years ago, just all the bragging and alluding of this being their own revelation is genuinely by Purism
11:21.37DocScrutinizer05funny how they forgot to mention you hardly can find any modem module that offers any other interface than USB and UART/serial
11:22.50DocScrutinizer05and I wonder which modem module they will finally pick. Modules with voicecall support get increasingly rare and hard to find
11:29.28DocScrutinizer05and I *really* wonder when or if they ever will stop spreading lies about the librem5 being "the first non-android phone" etc pp
11:31.51DocScrutinizer05>>given that a RYF phone has never been attempted before<< LIE!
11:53.04DocScrutinizer05Openmolo GTA01/02 you could argue was pre-RYF and thus logically can't have attempted to to be a RYF compliant phone (though we nevertheless *did* talk with RMS about exactly those aspects and the only thing missing was the RYF spec itself). But Neo900 evidently chatted with Mr Stallman regarding RYF compliance and we found we can't reliably forbid modem firmware upgrade. And we don't want to. Other than that Neo900 always
11:53.05DocScrutinizer05followed the principles of RYF from very beginning
12:14.14*** join/#openmoko-cdevel larsc (~lars@eisbaer.ursus-maritimus.org)
13:08.15*** join/#openmoko-cdevel alexxy (~alexxy@gentoo/developer/alexxy)
13:29.04pabs3DocScrutinizer05: does Linux have the USB bus restriction stuff?
13:30.44pabs3I hope the Neo900 project gets to production at some point
14:39.43mickeylhmm... indeed they tend a bit to historic revisionism, which is a bit insulting. Then again, it's marketing. *shrug*
16:56.20*** join/#openmoko-cdevel rtp (rtp@lechat.rtp-net.org)
18:20.35*** join/#openmoko-cdevel patinux (~patinux@unaffiliated/patinux)
19:39.27*** join/#openmoko-cdevel ao2 (~ao2@host196-141-dynamic.10-87-r.retail.telecomitalia.it)
19:53.33DocScrutinizer05pabs3: no expert, but I *think* at least udev for example should allow very finegrained filtering regarding which bus and and sub-branch etc is allowed to trigger modprobe for which driver
19:58.42DocScrutinizer05pabs3: then, there's a "inter-IC-USB" hw interface which is embedded USB without PHY for connecting chips (would be ideal for this usecase, alas all modem modules come with PHY so you need a second PHY in your phone)
19:59.55DocScrutinizer05pabs3: and generally when you have a kernel driver for - say, modem - and you load that driver and the driver occupies the USB controller hardware, then no other driver can get loaded and use that same bus, no?
20:16.10DocScrutinizer05actually never understood how jernel module probing works in detail
20:16.17DocScrutinizer05kernel*
20:16.59DocScrutinizer05deep onto the rabbit hole of DT and whatnot, I guess
21:28.49*** join/#openmoko-cdevel morphis (~morphis@p200300CCFBED4D00DF56D4137EF36E69.dip0.t-ipconnect.de)
23:34.08*** join/#openmoko-cdevel jave (~jave@h-223-63.A149.priv.bahnhof.se)
23:36.13*** join/#openmoko-cdevel pespin__ (~Sharwin_F@93.176.183.48)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.