| 03:24.45 | *** join/#maemo-ssu DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 08:45.19 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 08:49.03 | *** join/#maemo-ssu RedM (~redw@89-76-164-87.dynamic.chello.pl) |
| 09:17.12 | *** join/#maemo-ssu freemangordon (~ivo@46.249.74.23) |
| 09:52.44 | *** join/#maemo-ssu futpib (~futpib@37.113.239.183) |
| 10:44.11 | *** join/#maemo-ssu RedW (~redw@89-76-164-87.dynamic.chello.pl) |
| 11:15.21 | *** join/#maemo-ssu trx (ns-team@cable-188-2-98-144.dynamic.sbb.rs) |
| 11:15.21 | *** join/#maemo-ssu trx (ns-team@devbin/founder/trx) |
| 11:26.42 | *** join/#maemo-ssu corvinux (~hashcore@unaffiliated/hashcore) |
| 11:27.42 | *** join/#maemo-ssu hashcore (~hashcore@internet-188-196-229-244.narocnik.mobitel.si) |
| 11:28.48 | *** join/#maemo-ssu corvinux (~hashcore@internet-188-196-229-244.narocnik.mobitel.si) |
| 11:29.36 | *** join/#maemo-ssu hashcore (~hashcore@internet-188-196-229-244.narocnik.mobitel.si) |
| 11:30.04 | *** join/#maemo-ssu corvinux (~hashcore@internet-188-196-229-244.narocnik.mobitel.si) |
| 11:31.05 | *** join/#maemo-ssu corvinux (~hashcore@unaffiliated/corvinux) |
| 11:31.54 | *** join/#maemo-ssu corvinux (~hashcore@internet-188-196-229-244.narocnik.mobitel.si) |
| 11:33.16 | *** join/#maemo-ssu corvinux (~hashcore@unaffiliated/corvinux) |
| 11:38.34 | freemangordon | sailus: ping |
| 12:45.47 | *** join/#maemo-ssu corvinux (~hashcore@unaffiliated/corvinux) |
| 14:07.26 | *** join/#maemo-ssu RedM (~redw@89-76-164-87.dynamic.chello.pl) |
| 14:19.54 | Pali | freemangordon: looks like modest on my n900 does not set \Answered flag when sending reply to some message... |
| 14:20.07 | Pali | it is bug only for my setup, or do you have it too? |
| 14:21.17 | Sicelo | always thought mutt only can do that |
| 14:23.53 | Pali | Sicelo: I'm using KMail (1) and it set \Answered flag always... |
| 14:24.05 | Pali | mutt too |
| 14:24.10 | Pali | trojita too |
| 14:24.33 | Pali | and modest looks like did not do it for last emails which I checked |
| 14:25.53 | Sicelo | yes, it doesn't. (tbh i don't use it much, but i don't recall that flag being set) |
| 14:47.34 | DocScrutinizer05 | which flag? where gets it stored, and how? |
| 14:48.35 | DocScrutinizer05 | I guess kmail stores it locally (or - in my case - particularly in akonadi abomination) |
| 14:49.14 | DocScrutinizer05 | or is there a header tag that gets added to the mail text? |
| 14:50.14 | DocScrutinizer05 | KMail (1)? |
| 14:50.18 | DocScrutinizer05 | man kmail |
| 14:50.19 | DocScrutinizer05 | No manual entry for kmail |
| 14:50.19 | Pali | DocScrutinizer05: KMail 1 stores IMAP flags in local copy of email header |
| 14:50.33 | Pali | I mean KMail in version 1 (=non akonadi version) |
| 14:51.03 | Sicelo | it's saved on server .. |
| 14:51.04 | Sicelo | In-Reply-To: <CAPmnw_Xq5J30UTfNbEJ8hES=PByuT+5WZyGKYR4oMVtw9Hw_KA@mail.gmail.com> |
| 14:51.05 | Pali | and when synchonizing folders, it propagates flags from local email headers to imap flags |
| 14:51.08 | DocScrutinizer05 | aah, k. that's why I said "in my case" - I know you got an awesome akonadi-neutered version |
| 14:51.22 | Pali | Sicelo: no, that is in-reply-to header in email message |
| 14:51.33 | Pali | I mean IMAP flags which are not part of message |
| 14:51.50 | Sicelo | i can't find them :( |
| 14:51.59 | Pali | what? |
| 14:52.15 | DocScrutinizer05 | I try to avoid IMAP where I can |
| 14:52.23 | DocScrutinizer05 | so I can't comment |
| 14:52.29 | Sicelo | prefering POP? |
| 14:52.33 | Pali | Sicelo: what you cannot find? |
| 14:53.08 | DocScrutinizer05 | Sicelo: yep, but we had that "discussion" several times. I got my sound reasons, from my very uncommon usage pattern |
| 14:53.15 | Sicelo | Pali: where the flag ends up getting stored. |
| 14:53.25 | Pali | on IMAP server |
| 14:53.29 | Sicelo | DocScrutinizer05: okay. interesting |
| 14:53.35 | Pali | IMAP is state protocol |
| 14:53.49 | Pali | it identifies message by IMAP UID |
| 14:54.03 | Pali | and for each UID is can store list of flags |
| 14:54.13 | DocScrutinizer05 | Sicelo: it boils down to me neither wanting mail stored on an arbitrary exposed server I don't control, nor do I want sync of clients |
| 14:54.35 | DocScrutinizer05 | only local data is good data ;-) |
| 14:54.56 | Sicelo | :) |
| 14:55.57 | Pali | normal flags are: \Seen \Answered \Flagged \Deleted |
| 14:56.10 | Pali | and if you have "good" imap server, you can use any flag :-) |
| 14:56.22 | Pali | \Seen is used for marking message "as read" |
| 14:58.14 | Sicelo | and \Flagged? |
| 14:58.41 | Pali | imap rfc say that \Flagged is used for marking message as "important" |
| 14:58.50 | Pali | all those flags can be set by imap client |
| 14:58.54 | Pali | or unset |
| 14:59.07 | Sicelo | nice. will test that one on mutt |
| 14:59.19 | Pali | in mutt it is key F :-) |
| 14:59.56 | Pali | if you mark in mutt message as flagged it propagate this state to imap server as \Flagged |
| 15:00.07 | Sicelo | just did it. puts an exclam. nice :) |
| 15:00.41 | Pali | yes |
| 15:00.58 | Pali | gmail imap server translate this flag as "Star" |
| 15:18.03 | freemangordon | Pali: no idea what this "answered" thing is |
| 15:18.26 | Pali | imap flag, like \Seen |
| 15:25.49 | freemangordon | Pali: any idea how to switch to front cam in camera-ui2? |
| 15:26.13 | Pali | well, I knew that... |
| 15:26.57 | freemangordon | found it b/B |
| 15:30.08 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 15:33.35 | *** join/#maemo-ssu DocScrutinizer05 (~saturn@ppp-88-217-19-209.dynamic.mnet-online.de) |
| 15:33.38 | *** join/#maemo-ssu DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 15:33.47 | Pali | yes, b/B key |
| 16:03.42 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-34-183.net.upcbroadband.cz) |
| 16:32.09 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-34-183.net.upcbroadband.cz) |
| 16:59.21 | *** join/#maemo-ssu Sicelo009N (~sicelo@unaffiliated/sicelo) |
| 18:16.32 | *** join/#maemo-ssu corvinux (~hashcore@internet-188-197-41-95.narocnik.mobitel.si) |
| 18:16.32 | *** join/#maemo-ssu corvinux (~hashcore@unaffiliated/corvinux) |
| 18:22.06 | *** join/#maemo-ssu RedW (~redw@89-76-164-87.dynamic.chello.pl) |
| 18:52.30 | *** join/#maemo-ssu anYc (anyc@home.hadiko.uni-karlsruhe.de) |
| 18:53.16 | *** part/#maemo-ssu anYc (anyc@home.hadiko.uni-karlsruhe.de) |
| 19:05.19 | *** join/#maemo-ssu RedW (~redw@89-76-164-87.dynamic.chello.pl) |
| 20:02.59 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-92-160.residential.rdsnet.ro) |
| 20:39.11 | *** join/#maemo-ssu DrCode (~DrCode@5.28.134.3) |
| 21:01.36 | sailus | freemangordon: Pong. |
| 21:48.37 | freemangordon | sailus: hi! I am trying to make cameras working on n900, linux 4.6-rc1. No matter what I do, all I can get is a green image, the same as with 3.x kernels. So, is CSIb supported in ISP driver and what needs to be done to implement that support if not? |
| 21:50.03 | freemangordon | I am using Pali's linux-n900 tree, there are a couple of fixes from you (and sre) to make N9/50 cameras working |
| 21:50.42 | freemangordon | In dmesg log everything seems ok, there are no errors, etc |
| 21:52.49 | freemangordon | sailus: One thing I saw missing, is enabling the CSI1 receiver in SCM CONTROL_CSIRXFE register, but even after I added the needed code, still no success |
| 22:30.53 | DocScrutinizer05 | silly question: you got proper initialization for the camera(s)? |
| 22:33.10 | DocScrutinizer05 | SMIA95_AF_camera module_APL_090511.doc ET8EK8 |
| 22:34.25 | DocScrutinizer05 | http://wstaw.org/m/2016/04/11/plasma-desktopUk2219.png |
| 22:45.27 | DocScrutinizer05 | http://wstaw.org/m/2016/04/11/plasma-desktopqJ2219.png http://wstaw.org/m/2016/04/11/plasma-desktophw2219.png http://wstaw.org/m/2016/04/11/plasma-desktopIL2219.png |
| 22:46.24 | DocScrutinizer05 | https://www.google.de/search?q=SMIA95_AF_camera+module_APL_090511.doc |
| 22:49.14 | DocScrutinizer05 | http://mg.pov.lt/maemo-irclog/%23maemo.2013-03-02.log.html#t2013-03-02T08:21:15 |
| 23:58.51 | sailus | freemangordon: I think the CCP2 receiver should be ok. No-one has verified the changes though. And AFAIR there's no DT support (in the mainline kernel). |
| 23:59.36 | sailus | I remember there were issues with clocks on 3430, I have to say I don't know whether the issue was resolved since. :-I |
