IRC log for #maemo-ssu on 20131011

00:43.10*** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1)
00:46.24*** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au)
00:57.55*** join/#maemo-ssu kolp_ (~quassel@212.255.19.123)
01:07.37*** join/#maemo-ssu kolp (~quassel@212.255.19.123)
01:25.44*** join/#maemo-ssu kolp_ (~quassel@212.255.30.162)
01:30.44*** join/#maemo-ssu wmarone (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
01:41.22*** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-21.residential.rdsnet.ro)
02:41.11*** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn)
02:44.26*** join/#maemo-ssu g3kk3r (torrkull@lehtori.cc.tut.fi)
02:44.26*** join/#maemo-ssu ototo (ototo@ec2-54-225-101-41.compute-1.amazonaws.com)
02:44.42*** join/#maemo-ssu ototo (ototo@linaro/ototo)
02:45.35*** join/#maemo-ssu tg (~x@91.143.83.125)
02:45.48*** join/#maemo-ssu tg (~x@unaffiliated/tg)
02:55.13*** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode)
02:55.13*** join/#maemo-ssu amizraa (~amizraa@gateway/tor-sasl/amizraa)
02:56.53*** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode)
03:00.14*** join/#maemo-ssu discopig (~discopig@unaffiliated/discopig)
04:02.47*** join/#maemo-ssu Milhouse (~Milhouse@Maemo/community/contributor/Milhouse)
04:11.26*** join/#maemo-ssu aap (~drew@cpe-174-101-232-161.cinci.res.rr.com)
04:32.24*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
04:52.10*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
05:08.35*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
05:48.33*** join/#maemo-ssu Pali (~Pali@Maemo/community/contributor/Pali)
06:01.14*** join/#maemo-ssu luf (~luf@ip-89-103-184-55.net.upcbroadband.cz)
06:52.52freemangordonFatPhil: if you manage to boot fremantle with 3.12 on you devel device and wonder what to start doing with it, you may want to look why after a reboot from 2.6.28 to 3.12 a couple of devices connected to i2c fail to start :)
06:54.17*** join/#maemo-ssu Pali (~Pali@Maemo/community/contributor/Pali)
06:54.56freemangordonFatPhil: and yes, my tree is a clone of Pali's, but Pali's lag a little because of his faulty laptop
06:56.11FatPhilfreemangordon: good to know. I cloned yours, with linux as a --reference, I'll try to pull daily. How often to you merge?
06:56.49freemangordonit is pali who pulls upstream, iiuc on a release
06:56.52Palino merge
06:57.08PaliI only rebasing patches on rc/release versions
06:57.53Paliso I always see patches which are not in upstream...
06:58.18freemangordonPali: are there lots of them?
06:58.30Paliyes
06:58.30freemangordon(excluding drivers)
06:58.51PaliI think all are drivers or board code
06:59.07freemangordonwell, not that bad then
06:59.09Palionly small of them patching something other
06:59.17freemangordongood
07:00.07freemangordonsailus: ping
07:03.33*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
07:10.57Palifreemangordon: did you already looked at DT?
07:11.23freemangordonPali: no, I am waiting for something to come from upstream
07:11.33freemangordonin 3.13 there should be
07:11.47Paliok
07:11.55Palithen we will wait for 3.13
07:12.17freemangordonI'll send a couple of mails about broken omapfb later on
07:12.57Paliso now only need to fix snd (with jack detection), omapfb and camera, right?
07:13.06freemangordonyep
07:13.08freemangordonand gpios
07:13.21Paligood
07:13.29Paliand what about power management?
07:13.29freemangordonooh, and LEDs
07:13.42Paliah leds, I will look at them
07:13.49freemangordonPali: I think we should have everything working first
07:14.16freemangordontouchscreen is not disabled, so it is hard to say what is the state of PM
07:14.36freemangordonhmm, maybe I should look at that issu
07:14.40freemangordon*issue
07:14.46Palitouchscreen is not disabled when lock screen?
07:14.50freemangordonyes
07:14.56Palimaybe problem with slide gpio and mce
07:15.08Palior maybe missing some touchscreen sysfs entry
07:15.11freemangordonno, display is powered off
07:15.23freemangordonbut TS still active
07:15.39freemangordon:nod: (missing sysfs entry)
07:16.58freemangordoni'll look at it
07:18.24FatPhilPali: if you rebase, then you're not fast-forwardable. You're not a stable tree upon which to base anything else.
07:18.44FatPhilhttp://changelog.complete.org/archives/586-rebase-considered-harmful
07:19.06FatPhilSee the first bit in bold
07:19.39FatPhilIt's great for solo work, but not when you're sharing your tree
07:20.21PaliFatPhil: for each kernel version I have separate patch set
07:20.52Paliand rather I will use quilt for n900 patches, but it is not easy for use
07:21.19FatPhilquilt was invented when git didn't exist. there's no logical reason to use it now git exists.
07:21.27Palifor each kernel version I have separe branch
07:21.52FatPhilOK, at least that helps keep things sane
07:21.56PaliI need to see all patches which are not in upstream
07:22.20Paliand I also need to generate formated patches for sending to upsteam
07:22.43Paliwhich means I must rebase patches on top of some new kernel version
07:23.06Palifast forward and merge will totally broke it
07:23.13*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
07:23.28Paliand then there will be big mess about patches...
07:24.12Paliwhen I rebasing patches on top of new kernel version, I doing some patch simplification or merged more patches to one if that make sense
07:24.21Paliso I have clean patches...
07:24.43Paliand I never doing push --force, so repository is never broken
07:24.58Paliyou always can do pull fast forward
07:25.16Palibut sometimes you need to switch to new branch
07:25.35freemangordonhmm: "/sys/devices/platform/omap2_mcspi.1/spi1.0/disable_ts"
07:27.07FatPhilwhose touchscreen driver are you running?
07:27.14freemangordonupstream
07:27.14FatPhildoes it have a threaded irq?
07:27.18freemangordonNFC
07:27.23FatPhilOK, aaro's not mine
07:27.30freemangordonbut it should have, as it is forced
07:27.40freemangordon(threaded irq)
07:28.20FatPhilthere were no threaded irqs in .28, when I was maintaining tsc2005.c
07:28.56freemangordonin 3.12 all are threaded, unless you specify a flag in request_irq, iiuc
07:29.29FatPhilDmitry Torokhov's done some big cleanups to that code too, it's changed quite a lot
07:30.35jonwilbtw did we end up solving the problem of that one driver where the kernel guys refused to accept changes because "its Nokia's Driver and only Nokia can change it"?
07:31.06freemangordonjonwil: there is no problem, Pali wanted to simplify the things
07:31.11jonwilok
07:31.15freemangordoniirc
07:31.42Palijonwil: it is still a problem
07:31.48jonwilok
07:31.51Paliin usb subsystem
07:32.18FatPhiljonwil: that was a patch from Pali that Felipe rejected as it created potential breakage for legacy userspace
07:32.22FatPhilIIRC
07:32.35jonwilok
07:32.43Palithere was no userspace breakage
07:32.51freemangordon:nod:
07:32.57Palibut I will send that patch for comments again
07:33.04Palion top of 3.12-rc1
07:33.11FatPhilDidn't it change the userspace API?
07:33.16Paliin 3.10 was g_nokia totally broken
07:33.25Palino, it did not changed any api
07:33.35Paliit added new optional support
07:33.44Paliwhich can be at runtime enabled/disabled
07:34.05Palifreemangordon: is g_nokia working in 3.12?
07:34.14Paliis pc suite mode working?
07:34.21Paliis mass storage working?
07:34.30freemangordong_nokia is broken, at least in bootmenu
07:34.30Palican you test it?
07:34.35freemangordonok, I will
07:34.39Paliok
07:36.34freemangordonPali: would bq start charging if device booted with charger attached?
07:36.50freemangordonbq driver that is
07:37.09FatPhilah, this thread... http://lkml.org/lkml/2013/1/22/375
07:38.09Palifreemangordon: should
07:44.05freemangordonwell, well, the path for TS is different
07:44.20freemangordonBUT - there is no "disable" sysfs entry iiuc
07:44.58Palifreemangordon: so only sysfs entry is missing?
07:45.10freemangordonPali: and path differs too
07:45.35freemangordon"/sys/devices/platform/omap2_mcspi.1/spi_master/spi1/spi1.0" is in 3.12
07:45.53Paliyou should use /sys/class
07:45.59freemangordon"/sys/devices/platform/omap2_mcspi.1/spi1.0/" is what mce looks for
07:46.09freemangordonPali: me? :P
07:46.24Palican you check if you have it in /sys/class/ too?
07:46.59freemangordon"/sys/class/spi_master/spi1"
07:47.16freemangordonthat is linked to "/sys/devices/platform/omap2_mcspi.1/spi_master/spi1"
07:48.31Palisome other class name (like input/touchscreen/....)?
07:49.10FatPhilcommit 5cb81d19bae47adcb073a5e5a3bc40dd252f239e
07:49.40FatPhilhopefully revert to solve "so only sysfs entry is missing?"
07:49.44FatPhilpure guess
07:50.52Palion kp52 I have /sys/class/spi_master/spi1/device/spi1.0
07:51.53freemangordonnot in 3.12
07:52.16Paliand what is on 3.12?
07:52.44freemangordonPali: ^^^
07:53.05freemangordon"/sys/class/spi_master/spi1"
07:53.22freemangordonlinked to "/sys/devices/platform/omap2_mcspi.1/spi_master/spi1"
07:53.42Palikp52: /sys/class/spi_master/spi1/device/spi1.0/disable_ts
07:54.08Paliin 3.12 there is? /sys/class/spi_master/spi1/disable_ts
07:54.25freemangordonno, see the commit posted by FatPhil
07:54.32Palilink?
07:54.35freemangordon"Input: tsc2005 - remove 'disable' sysfs attribute"
07:55.01PaliI do not have git tree on n900 :D
07:55.15freemangordonthis is the title ^^^
07:55.39freemangordonlets see if we can use some "power" sysfs entry
07:55.41FatPhilhttp://www.spinics.net/lists/linux-input/msg14575.html
07:55.52FatPhilPali: ^^^ = that patch
07:55.58Paliok
07:56.43FatPhilWho was interested in the AES h/w acceleration
07:58.41Paliif we can offload aes from cpu to other dedicated hw, then it can be really usefull
07:58.52Palie.g. for luks
07:59.10freemangordonPali: FatPhil: any clue how to power down(disable) a device using sysfs entry?
07:59.42FatPhilPali: http://privatepaste.com/97443f891d
07:59.51Paliwrite something to power/level
08:00.04Paliand if level does not exits, then there is no way
08:00.23FatPhilfreemangordon: I liked the old sysfs way, but I have a 2.6.28 brain
08:00.49freemangordonPali: what needs to be done so "level" to appear?
08:00.55freemangordonFatPhil: same here :D
08:00.58FatPhilI'm not sure why Dmitry removed the functionality from tsc2005 before adding a generic replacement
08:01.57PaliFatPhil: about that secure code: it is not possible to enable it from non secure side via smc calls?
08:02.21Palilike IBE bit for thumb errata
08:03.06Palifreemangordon: report bug to maintainer for reverting old sysfs entry for compatibility mode (or to implemented new support)
08:03.36FatPhilMaybe someone could ask him why he broke userspace ;-)
08:03.48Paliright
08:06.16*** join/#maemo-ssu freemangordon_ (~freemango@46.249.74.23)
08:07.22FatPhilA very cheesy way of "disabling" the ts is to just close the device node, of course
08:07.44FatPhilwho's the client that relies on ts_disable?
08:08.03freemangordon_FatPhil: mce :D
08:09.29freemangordon_FatPhil: (power outage here) is there a way to open that firewall by using SMC?
08:10.47freemangordonFatPhil: also, what exactly do you mean by saying "firewall"? all I know is some co-processor registers
08:11.13Paliomap firewall from that pastebin
08:11.39freemangordonwhat IS "omap firewall", I've never seens such a term in ARM docs
08:12.53FatPhilfreemangordon: have you even seen the secure mode docs ;-)
08:13.21freemangordonno, but co-pro regs are well documented in public docs
08:14.53FatPhilMy understanding, and I've never ever looked at secure mode, is that the firewall is just a name for rejecting certain requests. If it's not configured in secure mode to enable those calls, you can't call them.
08:15.40freemangordonwhich is exactly what some regs in system control coprocessor do
08:16.38freemangordonthough mshield is missing from the public docs afaik
08:17.48jonwilso much omap bits not made public and only revealed under NDA
08:19.09FatPhil90% of the kernel developers didn't have access to that bit of the TI docs
08:19.36FatPhilEven the TI onsite support dude didn't have access to the TrustZone docs, it was that secretive
08:20.24Palithere is some docs about arm trustzone
08:20.29Palion arm website
08:20.39Palionly need to register
08:21.37jonwilProbably not the secret bits
08:21.57freemangordonHW AES shouldn;t be that secret
08:22.18jonwilThat Jazelle stuff for Java speedup is also totally secret :(
08:22.29freemangordonyeah :(
08:22.55jonwilI think the Java thing was a deal with Sun to make sure that only Sun approved JVMs could use the hardware acceleration
08:24.07FatPhilnow deprecated, thank ${DEITY}
08:24.39Palithere is thumb-ee ISA for jit compilers
08:26.39jonwilSurprised no-one didn't just reverse engineer Jazzelle
08:26.52jonwilWouldn't be the first time someone reverse engineered undocumented instruction sets :P
08:27.07Palibecause of java?
08:27.20Paliwhy somebody want to have java on mobile???
08:27.20freemangordonjonwil: nothing to RE afaik. jazelle is something like FP on 8088 iiuc
08:27.52freemangordonyou either have HW support, or you get an interrup/fault/whatever
08:27.57*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
08:28.00Palirather to have native code as some hw support for java jvm
08:28.37freemangordonjonwil: iiuc, you have some java bytecode instructions supported in HW
08:32.28jonwilJazzelle came about back when J2ME was king and the CPUs in phones were less powerful than they are today
08:32.59jonwilso it made sense to support it
08:33.51jonwilhttp://en.wikipedia.org/wiki/Jazelle indicates that using it isn't as simple as it sounds
08:34.28freemangordonhmm, no "level" here https://gitorious.org/linux-n900/freemangordons-linux-n900/source/777f4ace4c58799575391833db48050ceefe6fd6:Documentation/ABI/testing/sysfs-devices-power
08:45.04*** join/#maemo-ssu kolp (~quassel@212.255.30.162)
08:58.56FatPhilfreemangordon: Doh - I'm being thick, the very next patch (backwards in time) shows what the correct power interface is - open/close! commit 0b950d3d7ce4c1e870b8efc4ae0faaf0ef53532c
08:59.15freemangordonFatPhil: yep, saw that
08:59.19*** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net)
08:59.42freemangordonbut I don;t know who opens it
09:00.03FatPhilX?
09:00.12freemangordoncould be
09:00.19freemangordonbut doesn't help much :D
09:00.23FatPhillsof should say
09:02.05freemangordonNokia-N900:/dev/input# lsof ts
09:02.07freemangordonCOMMAND    PID USER   FD   TYPE DEVICE SIZE NODE NAME
09:02.09freemangordonXorg      1581 root   11u   CHR  13,67      6903 event3
09:02.11freemangordonhald-addo 1664 root    6r   CHR  13,67      6903 event3
09:02.13freemangordonmce       1948 root   10r   CHR  13,67      6903 event3
09:02.28freemangordonopen/close won't help
09:02.33FatPhilyup
09:02.43FatPhilDmitry needs mailing
09:02.50freemangordoncould you do it?
09:03.02FatPhilsure thing
09:03.16freemangordoncopy me and Pali please
09:06.44FatPhilThat's a possibility. As long as it doesn't immediately get dismissed as just being those troublemakers again...
09:07.20freemangordonFatPhil: hmm?
09:07.26freemangordonwho are the troublemakers?
09:07.28freemangordon:D
09:08.44freemangordonooh, those die hard n900 guys who want the kernel to work on a real HW. I see...
09:09.19freemangordonFatPhil: BTW I don;t see what else could be used
09:09.25FatPhilWell, people who swear at Felipe Balbi might be considered troublemakers, for example
09:09.45freemangordondon;t copy Pali then  ;)
09:10.45freemangordonFatPhil: any idea what else could be used instead of disable sysfs entry?
09:11.56FatPhilI think revert the patch is the best option
09:12.11FatPhilIt's lunchtime here though. I'll write the mail with a full belly
09:12.28freemangordonsounds sane
09:18.12FatPhilI got as far as:
09:18.13FatPhilBack in http://www.spinics.net/lists/linux-input/msg14575.html [PATCH 17/17] Input: tsc2005 - remove 'disable' sysfs attribute
09:18.16FatPhilyou broke Nokia n900 userspace.
09:18.43FatPhilBut decided that was not the polite approach
09:18.45freemangordonyeah, you'd better have something for lunch :)
09:21.26FatPhilneed food! but before I get food, I need socks!!! (moved back to tallinn last weekend, everything's chaos here)
09:31.46*** join/#maemo-ssu luf (~luf@80.188.29.62)
09:35.31*** join/#maemo-ssu Pali (~Pali@Maemo/community/contributor/Pali)
10:35.09*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-lpulgqyodfgttjnn)
11:31.54*** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode)
11:34.15*** join/#maemo-ssu xmlich02 (~imlich@2001:67c:1220:80c:88:1f9:781:6ae1)
11:45.16*** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net)
11:56.31PaliFatPhil, freemangordon: when you sent those mails to lkml (without cc), please at least send links here
12:03.44FatPhilPali: will do
12:04.02FatPhilHAs anyone ever seen the UI "shrunk"?
12:04.16FatPhilFulol functional, just only taking up 2/3rds of the screen
12:04.24FatPhils/fulol/fully
12:04.53merlin1991FatPhil: yep
12:04.56merlin1991reboot and it's gone
12:05.00merlin1991we don't know the exact cause
12:05.28merlin1991btw to use it, the touchscreen still is used as if the ui were "fullscreen" :D
12:21.19FatPhilyup, worked that out!
12:21.33FatPhilThe weird thing is that the swipe-to-unlock is the right size!
12:31.40kolpFatPhil: For me it happend when I locked the device right after the wallpaper showed at boot time. When I then unlock a little later the scrren is 2/3rds like you see
12:39.25Palifreemangordon: is there public documentation about omap3 smc calls?
12:39.49Palito check if omap hw rand driver is ok?
12:53.08*** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode)
14:05.01*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
14:19.01FatPhiloi, silly bot, what was the URL I told you to pass on to Pali...
14:19.53jonwilwouldn't that be in the chanlog? :P
14:21.12FatPhilYeah, but I want the bot to feel useless, lest it gets a sense of superiority to humans
14:22.20Paliirc memoserv is for offline messages .-)
14:26.43FatPhilYRC, many thanks!
14:29.53FatPhiljonwil: have you decompiled nolo?
14:30.20jonwilnope, I wouldn't know where to begin as its a binary blob rather than an ELF executable
14:30.30jonwiland obviously I cant decompile it since its ARM and not x86
14:30.37Paliyou can embed binary blob into elf :-)
14:30.42jonwilbut no I haven't disassembled it
14:30.52jonwilwhy the interest in nolo?
14:31.05Palijust compile empty file to elf object file
14:31.18Paliand then objcopy nolo into that elf object
14:31.48Paliand then objdump -D for disassembling working fine
14:32.00jonwilits not about loading the binary into IDA its about knowing where in the address space the different parts of the blob need to sit, its about knowing whats instructions and whats data etc
14:32.10jonwilalso I have no reason to care much about nolo
14:32.42jonwilIts not going to be usable on Neo900 in any case
14:32.57jonwilsince nolo is tied to the specific OMAP SoC in N900
14:39.29jonwilso again I say, why the interest in NoLo?
14:43.59freemangordonjonwil: I suspect because of AES
14:44.20*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-egshnetmqbbdgdnq)
14:44.41freemangordonhmm, but why nolo?
14:45.15freemangordonPali: there is something mentioned in public 3430 TRM, lemme check what it is
14:45.43Palifreemangordon: ok
14:45.58Palisome doc for omap3 rom rng can be usefull
14:46.55jonwilPersonally I would be less inclined to trust hardware cryptography given all the recent NSA stuff (and given that Texas Instruments is a big USA company that would probably bend over backwards if the NSA wanted them to add backdoors to their parts)
14:47.37jonwiland I know a few security researchers and crypto geeks who would agree with the idea of being suspicious of hardware crypto and RNGs and stuff in mass-market hardware
14:48.18Paliseed from hw rng for /dev/urandom should be safe
14:48.21jonwilat least with a software implementation in, say, openssl, its possible to audit that implementation
14:48.23Paliand good
14:48.36freemangordonPali: all is about L2 and AUX CTL,
14:49.03freemangordonSWPU223M, p.3382
14:49.15Paliok
14:50.36PaliI did not find anything on internet about omap3 rng (expect info in maemo kernel)
14:51.42Palianybody has doc about smc/secure part?
14:55.29jonwilTI seems to want to keep all that stuff secret
14:55.34jonwilincluding security features
14:55.37jonwilhardware RNG/crypto
14:55.39jonwiletc etc
14:55.59freemangordonjonwil: most probably they are missing in GP devices
14:56.25jonwilI doubt anyone who has that doc will be willing to share public (it likely has a lot of "confidential TI information" warnings at the top of irt)
14:56.36Paliyes, gp devices does not have them
14:57.12Palibut why is api big secret? if you want to use it - it must be in kernel and that is open source...
14:57.36freemangordonPali: how is HWRNG called? through SMC?
14:58.06jonwilIs Linux the only OS that can run on the TI OMAP?
14:58.08jonwilI doubt it
14:58.24jonwilalso, having kernel source and having full docs are 2 different things
14:58.56jonwilespecially if kernel source is written in a way to hide as much info as possible
14:59.20jonwile.g. not giving names to hardware registers (or giving useless names)
15:00.14freemangordonPali: hmm, what we need is smc calls for n900
15:01.23freemangordononly 3 functions are in trm, with their numbers not matching what is in n900
15:01.26Palifreemangordon: yes hwrng is used by calling smc
15:01.51freemangordonPali: the only think we can use is 2.6.28 kernel
15:01.54freemangordon*thing
15:02.10Palifreemangordon: hwrng driver is already in lkml
15:02.18freemangordonI know
15:02.21PaliI sent it for upstream
15:02.48freemangordonI know that too. the point is that our only source of info re ROM on n900 is 2.6.28
15:03.12Palibut I do not understand why there is rng driver for omap2 and omap4 which using normal memory access
15:03.22Palibut nothing for omap3
15:03.23freemangordonPali: where?
15:03.25freemangordonupstream>
15:03.35Paliyes in upstream
15:03.37freemangordons/>/?/
15:03.49Palibut for omap3 is only via smc...
15:04.16freemangordonPali: did you try upstream on n900?
15:04.27Paliand aes/sha/md5 driver using also direct mem access, but secure side needs to be configured
15:05.03freemangordonPali: hmm, wait. I bet there is an smc call to use crypto module
15:05.04Palifor me it looks like that smc code is used when secure side is not configured for direct mem access
15:05.10freemangordon:nod:
15:05.18Palino crypto module using direct mem access
15:05.19freemangordonthat is why my bet
15:05.22Palino smc calls
15:05.29freemangordonhow do you kno0w that?
15:05.48Paliyes I already looked at crypto module source code
15:06.02freemangordonPali: that's not relevant
15:06.08Paliit is in upstream kernel
15:06.29freemangordonPali: isn't it the same for HWRNG? ;)
15:06.45freemangordonupstream uses memory, we SMC
15:07.02freemangordontoldya, I bet it is the same for crypto
15:07.14PaliI do not understand why: hwrng for omap2 and omap4 (both different code), crypto modules (sha, aes, md5) using direct mem read/write
15:07.27Paliand our omap3 hwrng calling smc
15:07.55freemangordonwhat other device but n900 uses HWRNG from the kernel?
15:07.56Paliand there is no omap3 hwrng in upstream
15:08.16Palido not know
15:08.23freemangordonN9?
15:08.32freemangordonwhat about it? merlin1991 ^^^
15:08.55Palido not know, need to look into harmattan kernel
15:09.02freemangordonPali: hmm, I guess we can find the info from harm kernel
15:09.30freemangordonI'll join #harmattan and ask
15:09.36Paliok
15:09.47Paliif that channel is not dead
15:09.58freemangordonfeel free to join :)
15:10.04freemangordonit is not dead
15:11.07Palifreemangordon: look: http://www.droid-developers.org/wiki/Trust_Zone
15:16.05freemangordonPali: I see nothing of interes here, do I miss something?
15:21.43freemangordonPali: where is HWRNG driver in KP?
15:22.27Paliin drivers/char/hwrng
15:34.18*** join/#maemo-ssu jonwil_ (~jonwil@27-33-137-199.static.tpgi.com.au)
15:50.37*** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-21.residential.rdsnet.ro)
15:55.30FatPhiljonwil: was yesterday's dose of cosmetics acceptible?
16:05.16*** join/#maemo-ssu NIN101 (~NIN@p5DD2891B.dip0.t-ipconnect.de)
16:10.40*** join/#maemo-ssu trx (ns-team@devbin/founder/trx)
16:12.29*** join/#maemo-ssu trx (ns-team@212.200.198.223)
16:12.29*** join/#maemo-ssu trx (ns-team@devbin/founder/trx)
16:35.35FatPhilfairly subtle passive-aggressive mail composed, ready for sending
16:36.16FatPhil"given that you've shat on our heads, any advice on how we should comb our hair?"
16:36.35freemangordon:D
16:44.22freemangordonPali: NOLO calls PPA with some other functions, like 37, 29, 21, 20, 19 15
16:47.00freemangordonome of them have traces like "Initializing secure storage" (20) "Initializing RPC" (21)
16:47.10merlin1991FatPhil: did that go to some mailing list, ... can I read it?
16:48.17Palisecure storage??
16:48.29freemangordonNFC what that is
16:48.42PaliDRM?
16:48.52merlin1991it is a 2337 haxx0r proof memory location ofc ;)
16:48.52Palibut maemo has no DRM support...
16:49.05freemangordon18 is "Importing PAPUB keys"
16:49.29PaliPAPUB key is some part of x-loader signing chain maybe...
16:49.38Palior maybe R&D certificate
16:49.54freemangordoncould be
16:50.42freemangordonthe point is that we don;t know all PPA functions. and there is a hope there is some function in PPA, which allows us to enable crypto
16:51.57FatPhilmerlin1991: *that* didn't go to any mailing list - I was just playing things for laughs ;-)
16:52.32Palifreemangordon: in notebook hdd I have that xloader with crypto enabled functions
16:52.46Palixloader is for hw rev 2101 only
16:52.59Paliand nolo secondary too
16:53.23Palican you do some diff against pr1.3 xloader & nolo?
16:54.21freemangordonPali: there is xloader (some 15k binary) for every rev
16:54.34freemangordonunpack fiasko
16:54.38freemangordonyou'll see
16:54.41Palibut not xloader with crypto functions enabled
16:54.54freemangordonI don;t have it
16:54.57Palithat xloader was part of that email sent to maemo ml
16:55.00freemangordonlink?
16:55.06Paliuploaded to megaupload
16:55.13Paliso link is dead now
16:55.24freemangordonjacekowski?
16:55.24Palibut I should have copy in notebook hdd
16:55.48merlin1991Pali: do you have some backup of the notebook hdd somewhere?
16:55.54Palihttp://maemo.org/community/maemo-developers/n900_aes_and_sha1-md5_hw_acceleration_drivers/
16:56.09merlin1991I'm starting to feel like a lot of important (for us) stuff resides there
16:56.22Palimerlin1991: hdd is near me :-) but I do not have any reader of notebook hdd
16:56.41merlin1991shouldn't it be regular sata? (if it is not that old)
16:56.54PaliI do not have any machine here...
16:57.30PaliI will never give hdd with notebook to some warranty service provider
16:57.40PaliI do not trust any company...
16:57.59merlin1991feels like sending his old notebook to Pali, only problem I don't think it is sata yet :D
16:58.14Palifreemangordon: look at link ^^^
16:58.55freemangordon"Invalid or Deleted File." :(
16:58.56PaliI got email from HP that I will receive email about case :D
16:59.30freemangordonPali: don;t tell me you sent your laptop without have your HDD backed up
17:00.07Palifreemangordon: read ^^ I sent it without HDD
17:00.23*** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1)
17:09.15freemangordonPali: oh, ok :)
17:15.59FatPhilfreemangordon: merlin1991: Pali: http://lkml.org/lkml/2013/10/11/533
17:16.07FatPhil^^^ tsc2005 mail
17:29.03freemangordongood
18:01.06*** join/#maemo-ssu BCMM (~user@unaffiliated/bcmm)
18:11.09*** join/#maemo-ssu Woody14619 (~Woody@2620:4:4000:11:d1af:c755:bd0e:2352)
18:11.09*** join/#maemo-ssu Woody14619 (~Woody@Maemo/community/contributor/Woody14619)
18:13.06*** join/#maemo-ssu BCMM (~user@unaffiliated/bcmm)
19:24.31*** join/#maemo-ssu BCMM (~user@unaffiliated/bcmm)
19:29.24*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
20:07.06*** join/#maemo-ssu _rd (~rd@p57B483CF.dip0.t-ipconnect.de)
20:15.52*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
20:15.54*** join/#maemo-ssu dos11 (~dos@unaffiliated/dos1)
20:28.01*** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode)
20:41.24*** join/#maemo-ssu Martix (~martix@4.177.broadband3.iol.cz)
20:45.36*** join/#maemo-ssu Martix (~martix@4.177.broadband3.iol.cz)
20:51.40*** join/#maemo-ssu Martix (~martix@4.177.broadband3.iol.cz)
21:07.30*** join/#maemo-ssu xes (~xes@unaffiliated/xes)
21:16.08*** join/#maemo-ssu _rd (~rd@p57B483CF.dip0.t-ipconnect.de)
21:22.26*** join/#maemo-ssu _rd (~rd@p57B483CF.dip0.t-ipconnect.de)
21:34.02*** join/#maemo-ssu _rd (~rd@p57B483CF.dip0.t-ipconnect.de)
21:44.39*** join/#maemo-ssu rd_ (~rd@p57B483CF.dip0.t-ipconnect.de)
21:51.19*** join/#maemo-ssu WielkiTost (~dos@unaffiliated/dos1)
22:14.54*** join/#maemo-ssu freemangordon (~freemango@46.249.74.23)
22:24.45*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
22:55.05*** join/#maemo-ssu joshgillies (~josh@ppp108-14.static.internode.on.net)
23:52.27*** join/#maemo-ssu wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)

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