<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>Am 21.01.2016 um 14:39 schrieb Radek Polak <<a href="mailto:psonek2@seznam.cz">psonek2@seznam.cz</a>>:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 9pt; font-style: normal; font-variant: normal; font-weight: 400; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: 'DejaVu Sans Mono';"><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">On Thursday 21 of January 2016 13:05:27 Andreas Kemnade wrote:</div><p style="white-space: pre-wrap; margin: 0px; text-indent: 0px;"> </p><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> I must admit that I have never used qtmoko kernels because of that initramfs</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> because I do not want to /dev/mmcblk0p1 to be touched by anything</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> automatically. Just because power might end at a bad moment and there might</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> be no bootable kernel.</div><p style="white-space: pre-wrap; margin: 0px; text-indent: 0px;"> </p><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">Well i dont think it's the case. The gta04-init mounts only the partition that you tell it to mount (e.g. via config file, or touch screen) and boots into it. Just the mount command is done from userspace and can be very nicely customized compared to "stupid" root kernel option.</div><p style="white-space: pre-wrap; margin: 0px; text-indent: 0px;"> </p><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">Btw there was talk about "daemon" but daemon is IMO not needed at all, just single check during init that GPS is powered off.</div></div></blockquote><div><br></div><div><div>Yes, there is a difference to a daemon: a daemon runs forever and this runs only once.</div><div>Unless someone is wrongly handling the gpio. I.e. a process that did crash.</div></div></div><div><br></div><div><blockquote type="cite"><div style="font-size: 9pt; font-style: normal; font-variant: normal; font-weight: 400; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: 'DejaVu Sans Mono';"><p style="white-space: pre-wrap; margin: 0px; text-indent: 0px;"> </p><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> Well the problem is solved in some way. It is just about getting the</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> solutions accepted. That takes energy and if successful not only solves</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> GTA04 stuff but also other solutions. But that is the general problem of</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> upstreaming. You have your working solution and then put extra energy into</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> it which does often not give anything as reward (in short term).</div><p style="white-space: pre-wrap; margin: 0px; text-indent: 0px;"> </p><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">Yup understand. But i could understand if the upstreaming is rejected. Growing general kernel code because of 100 users while there is simple userspace solution...</div></div></blockquote><div><br></div>Well, there is a simple user space solution for a lot of garbage in the kernel...</div><div><br></div><div>But this is the solution: we need to grow number of users :)</div><div><br></div><div><blockquote type="cite"><div style="font-size: 9pt; font-style: normal; font-variant: normal; font-weight: 400; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: 'DejaVu Sans Mono';"><p style="white-space: pre-wrap; margin: 0px; text-indent: 0px;"> </p><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> > The real problem is e.g. that my Nokia N900 eats 3mA in suspend and</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> > lasts 6day, while GTA04 eats 25mA and needs recharging every day. I</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> > personally dont care if turning GPS on/off is 10 lines of code in</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> > userspace</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> > or 40 lines of code in kernel.</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> </div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> Well, I prefer working, standard interfaces. If the general rule is that</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> kernel is powering down things which are not used, than I want that.</div><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">> Another solution I could life if rfkill can at least do everything.</div><p style="white-space: pre-wrap; margin: 0px; text-indent: 0px;"> </p><div style="white-space: pre-wrap; margin: 0px; text-indent: 0px;">Agree that toggling rfkill during init should be easily doable for any userspace. </div></div></blockquote><div><br></div>Yes, but again: we have a working solution that is better. So it is waste of time to</div><div>think about yet another.</div><div><br></div><div>BTW: if I remember correctly, some RFKILL solution was also rejected by</div><div>kernel maintainers, because RFKILL means RF kill but not "turn device on/off".</div><div><br></div><div>The result is that same that you don#t get data... But it shows how nit-picking it</div><div>might be to get things into the kernel. Especially if they don't like that you come</div><div>and disturb their circles...</div><div><br></div><div>BR,</div><div>Nikolaus</div><div><br></div></body></html>