<wpwrak>
not sure. now that much information has been leaked, we may see some changes. but i don't really know what's going on inside those circles.
<wpwrak>
of course, as an equipment maker, we would also be at risk of bumping into patent issues if we use a "liberated" driver
b1101 has joined #neo900
b1101 has quit [Changing host]
b1101 has joined #neo900
Kabouik has quit [Read error: Connection reset by peer]
<nadrimajstor>
wpwrak: Don't get me wrong - I want neo900 no matter what hw specs are... But it is bugging me for a long time as I see this issue as a deadweight.
b1101 has quit [Quit: b1101]
b1101 has joined #neo900
b1101 has quit [Client Quit]
<wpwrak>
i guess nobody likes that gfx core :)
<nadrimajstor>
wpwrak: If neo900 project would like to have some exposure outside of Europe, FSF's "blessing" is a nice-to-have.
<wpwrak>
i wouldn't worry too much about what the FSF says about it. we know that it's not possible to make a device with these characteristics that would meet FSF's requirements. that's a completely different sort of environment.
<nadrimajstor>
wpwrak: Even the imgtec dislikes this core as they are openly hostile towards FLOSS. :D
<jake42>
tl;dr: FSF "wishes" are impossible to comply
<wpwrak>
nadrimajstor: yeah, i kinda wish that all of imagination's worst nightmares come true, and hordes of competitor and other patent trolls find stuff in the leaked documents they can sue them over. it would prove their point (and thus send the wrong signal to industry), but it still would feel like oh so sweet revenge ;-)
<nadrimajstor>
jake42: The debian guy from the Librem 15 team did mention that FSF is considering/debating with them to have exceptions.
<wpwrak>
i guess the fact that even fairly bare laptop needs an exception says something about how FSF's requirements connect to reality :)
<wpwrak>
but i understand why they are what they are - the FSF is concerned about ways to undermine the GPL, not about actually making hardware
b1101 has joined #neo900
b1101 has quit [Remote host closed the connection]
<SylvieLorxu>
It makes sense for the FSF to be strict
<SylvieLorxu>
I mean, if they allow proprietary baseband, why not allow proprietary WiFi and if they allow proprietary WiFi, why not allow proprietary kernel firmware, and if they...
<SylvieLorxu>
I like following the FSF to see where we want to be, and the FSFE to see where most progress is being made
<jake42>
the allow proprietary firmware, but it can not be updateable
b1101 has joined #neo900
<jake42>
s/the/they/
<SylvieLorxu>
Yeah, okay
<jake42>
which doesn't make any sense
<jake42>
(to use)
<SylvieLorxu>
Heh, agreed :P
<nadrimajstor>
SylvieLorxu: I see your point... But there are signs that RHS is trying to be more pragmatic and look at what can and what can not be realistically achieved at the moment.
<nadrimajstor>
SylvieLorxu: And it is a great achievement in itself. :D
<jake42>
unfortunatly RMS will never be able to carry a (turned on) mobilephone with him, as it can track him per design
kolp has quit [Remote host closed the connection]
<jake42>
regardless if it has a free baseband or not
<Oksana>
Heh... Wrap it in tin foil, and it will be untrackable.
<Oksana>
Or just use the "kill-modem" switch.
<jake42>
Oksana: right, but then again you could just take the battery out
<Oksana>
If you still want to use it as PDA-map-camera, "kill-modem" switch is more practical.
<jake42>
then you should get a PDA :-)
<jake42>
though they got quite rare I think
<jake42>
Oksana: you can get neo900 without modem :-)
<Oksana>
Phone booths are getting rare, these days, because of mobile phones ;-) And, they cannot get incoming calls, or incoming SMSs.
<Oksana>
Nay, I will just use the Neo900's built-in "kill-modem" switch.
<jake42>
RMS has a pager :-)
<jake42>
Oksana: ofc if you want to be able to connect to the mobilenetwork everynow and then
<jake42>
no modem is not an option
<jake42>
designing a mobilenetwork which cannot track you would be interesting
b1101 has quit [Quit: b1101]
<wpwrak>
easy but you have to start with a clean slate. then you begin to define suitable physics .. ;-)
* nadrimajstor
Pyra looks cool.
<Oksana>
Pyra probably has modem separated-isolated from main-CPU, too. Need more information about that, though. And I am fairly sure that Pyra is closer to laptop than to handheld.
b1101 has joined #neo900
<DocScrutinizer05>
there's virtually no way to design a transmitter that cannot get located
<DocScrutinizer05>
((pyra)) particularly our cousin project has no phone usecase in its design guidelines
<DocScrutinizer05>
it's neither designed for weeks of idle standby, nor for playback of ringtones on inbound calls
xes has joined #neo900
<DocScrutinizer05>
and it definitely has no external display for signalling any state when clamshell closed, nor an earpiece to use it as a normal phone
<DocScrutinizer05>
it's even unclear if the modem has complete audio connected
<DocScrutinizer05>
pyra's modem been included for data connectivity. Everything beyond is an "afterthought"
<DocScrutinizer05>
((<jake42> RMS has a pager :-) )) for RMS we will design a way he can integrate his pager into Neo900 to instantly pop up dialer with the number to call back, so RMS only needs to hit the "green button" and the modem will log in to network and cal the number signalled by pager ;-)
<DocScrutinizer05>
that should keep him happy
<DocScrutinizer05>
but hey, he will hate Neo900 since he can update the modem firmware :-/
<DocScrutinizer05>
sorry, RMS. No special pager integration for you then.
<DocScrutinizer05>
((pager)) we already discussed several aspects of this. Alas we cannot add a worldwide pager function into Neo900. But you can add the pager according to the standard you need, to the hackerbus of Neo900
<Oksana>
Maybe, it does not need additional hardware? Radio bands used for pagers include: 900 MHz band, 400 MHz band, the VHF band, and the FM commercial broadcast band (88-108 MHz). Don't know about others, but FM-receiver could be tame-able?
xes has quit [Ping timeout: 258 seconds]
sparetire_ has quit [Quit: sparetire_]
<DocScrutinizer05>
yes, for some near-FM pagers it could work, though this would keep CPU budy and cut through your battery in no time
<DocScrutinizer05>
we had a pager signal here in Germany on iirc 86.5MHz, used to decode this using a slightly tuned standard FM radio and a ZX-81
<DocScrutinizer05>
from the latter you can tell it been quite a while ago when I did that. dunno if it still exists, I guess not
<DocScrutinizer05>
>>Its distinctive design brought its designer, Rick Dickinson, a Design Council award.<< and rightly so, the ZX81 was awesome ingenious schematics
b1101 has quit [Quit: b1101]
<DocScrutinizer05>
prolly inspired wpwrak for his VGA output in Ben NN
<DocScrutinizer05>
;-)
<wpwrak>
naw, zx81 had an asic. that's cheating :)
<DocScrutinizer05>
hahaha
<DocScrutinizer05>
yeah, and that dang asic had a transistor buffer for video output that usually broke eventually. You could fix it though by adding an external transistor to the weak but still "visible" signal from the asic's video-out pin ;-)
<DocScrutinizer05>
ooh, I forgot to hit "thanks" on reinob's nice blessing of Neo900 and me
<DocScrutinizer05>
sixwheeledbeast: ta for the link!
<DocScrutinizer05>
just >>(OK, a fourth row on the keyboard would be even better)<< o.O better than a 1GB RAM, a 3730-CPU@1GHz, and a awesome modem solution and truckload of sensors?
<DocScrutinizer05>
aah maybe my poor english again. "even better" with than without
<DocScrutinizer05>
yeah, I as well wish we could have a fourth row
<DocScrutinizer05>
wpwrak: you knew the detail about ZX81 having asic, or you just checked?
<wpwrak>
i looked it up some time (months ? years ?) ago :)
<DocScrutinizer05>
:-)
b1101 has joined #neo900
b1101 has quit [Remote host closed the connection]
<DocScrutinizer05>
it's a awe-inspiring design
<wpwrak>
one key feature was a shift register for one screen line. that's actually something i sort of did on ubb-vga, too. that is, in the mmc-powered version. the first one used just bit-banging.
<DocScrutinizer05>
shift register for a whole line? nah, I don't think so. Shift register for one char's line, iirc
<DocScrutinizer05>
if the whole line was from a hw shiftreg, the CPU would have been free to perform semi-decent even in slow mode
<DocScrutinizer05>
but slow mode ate some 95% of CPU for video output
b1101 has joined #neo900
<wpwrak>
i think it was a whole line. but i'm not sure. ubb-vga does a whole line at a time. i'm sure about that :)
<DocScrutinizer05>
I think it transferred the "video buffer" symbol codes in real time to the asic, and they got serialized to 8 dots * 8 (or 10?) lines there
b1101 has quit [Quit: b1101]
<wpwrak>
naw, that would be mean storing a whole line of characters
<DocScrutinizer05>
maybe the car ROM was even discrete and CPU shoveled the raw pixel data from ROM into that 8bit sh-reg
<DocScrutinizer05>
s/car/char/
<wpwrak>
yup. the cpu sent one char cell line at a time. no character rom in the ULA. this of course makes me wonder why we didn't have high-res graphics on the critter.
<DocScrutinizer05>
because the ROM sent the char cell line to the ASIC
<DocScrutinizer05>
but yeah, you probably *could* override the char ROM output by simply providing the pixel data on CPU data bus, this basically trying to write to the char ROM address instead of reading from it
<DocScrutinizer05>
(R7 .. R14)
<DocScrutinizer05>
the kbd scanning still completely eludes me
<DocScrutinizer05>
particularly A13 which is connected to kbd matrix and A13 of CPU oly
<DocScrutinizer05>
only*
louisdk has quit [Remote host closed the connection]
<DocScrutinizer05>
meh, no overriding of the pixel data by CPU, it's doing a refresh
<DocScrutinizer05>
>>Some of this process is fixed in hardware (the ULA, resistors separating ROM/RAM from ULA/Z80 data lines), some of it is ROM code. In practice, ZX81 display generation turned out to be remarkably flexible, and various high-resolution schemes were produced. Some using ROM data (= pseudo Hi-Res), some using pixel data stored in RAM (= true Hi-Res, this works with internal RAM, or 16K RAM pack with a small hardware mod). Sir Clive missed
<DocScrutinizer05>
this Hi-Res capability by just a few logic gates... :-(<<
<DocScrutinizer05>
hehe
rblanco has quit [Ping timeout: 264 seconds]
<DocScrutinizer05>
((kbd)) meh, they omitted the kbd0 .. kbd4 wires in schematics
<wpwrak>
(quake) "crazy shit" just got redefined ;-)
<DocScrutinizer05>
lol
<DocScrutinizer05>
I'm almost happy that a LCD DSO is absolutely unsuited to do this, actually I think the Rigol not even has intensity/Z modulation in X/Y mode
<bencoh>
I'm pretty sure you'd have tried otherwise :p
<DocScrutinizer05>
I actually planned a computer display based on exactly this principle, though with discrete vectorizer. Back in 1977
<bencoh>
:)
lexik has joined #neo900
<DocScrutinizer05>
I went to the extreme of even trying to get parametric bsplines as shapes
<DocScrutinizer05>
and a planned for a character ROM
<DocScrutinizer05>
obviously not pixel based but composing chars from geometric shapes
<DocScrutinizer05>
luckily this project never grew further than theoretical planning
<DocScrutinizer05>
the cost would have beaten a highres raster display even with the RAM prices back when
rblanco has joined #neo900
<DocScrutinizer05>
and then... who would want to *use* such a display? Picasso?
lexik has quit [Read error: Connection timed out]
<DocScrutinizer05>
;-)
lexik has joined #neo900
<bencoh>
DocScrutinizer05: vector-based arcade games :p
<bencoh>
(asteroid was one of them iirc)
<DocScrutinizer05>
right, it would've been simple to define "sprites" of all sorts, and project them to and angle and distance
<DocScrutinizer05>
any*
<DocScrutinizer05>
any yes, asteriod original arcade version been vector gfx. I wonder if that inspired me or my idea was prior to that
<DocScrutinizer05>
and* dang
<bencoh>
Release date(s) Arcade
<bencoh>
NA November 1979
<DocScrutinizer05>
eeeew, it returns out of the graceful fog of oblivion. All those programmable amplifiers, oscillators and even hardwired sine/cosine tables and stuff. Incredible
<DocScrutinizer05>
grateful
<DocScrutinizer05>
the sort of phantasies a geek dreams at day with 17
<kerio>
didn't asteroids also have a way to shut down the line tho
<kerio>
so you didn't have to rely on drawing really quickly to make it show a very small line
<DocScrutinizer05>
sure, that's caled Z or intensity
<DocScrutinizer05>
and I don't know of a kathode ray tube that doesn't have it
<DocScrutinizer05>
basically all analog scopes come with a Z/trigger input
SylvieLorxu has joined #neo900
unknown__ has joined #neo900
<kerio>
don't you need three channels tho
justbrowsing has quit [Quit: Page closed]
<DocScrutinizer05>
X/Y/Z, yes
<kerio>
but audio is stereo
<kerio>
:(
<DocScrutinizer05>
very cheap analog 1-channel scopes come with trigger/Y jack
<DocScrutinizer05>
ooops s/Y/X/ - they also have no sensitivity adjustment for X input then
<DocScrutinizer05>
the Rigol has 4 input jacks / channels but afaik no Z/intensity
<DocScrutinizer05>
and thanks to it being a DSO, it not even dims "fast" lines
<wpwrak>
hmm, i wonder if it couldn't do this. after all, it does have intensity grading
<DocScrutinizer05>
sure it *could* do, but I think it doesn't in X/Y mode
<DocScrutinizer05>
for DSOs X/Y is sort of an afterthought
<DocScrutinizer05>
and extremely not natural to their internal operation mode
<DocScrutinizer05>
I think early DSOs were incapable of X/Y at all, thanks to the organization/entanglement of storage and display buffer
<DocScrutinizer05>
it's quite natural to have storage address == X and storage value == Y
<DocScrutinizer05>
for a single channel DSO you might not have a true video buffer at all
<DocScrutinizer05>
which instantly results in those scopes not displaying more than one dot per column
<DocScrutinizer05>
anyway nowadays X/Y mode is kinda obsolete for multichannel DSOs with tons of smart math. You calculate stuff like phase differences with the push of a button, not by using your calculator and trigonometric functions
<kerio>
lol
<DocScrutinizer05>
stuff like a nice little quatropole component tester drops off the table at far end though
rblanco has quit [Quit: leaving]
<DocScrutinizer05>
that's btw why I "investigated" pattern triggers, since I need to trigger on the sharp edge of the wobbling sawtooth signal rather than using the signal directly for X input
<DocScrutinizer05>
the planned test setup been wobbling a sqaurewave oscillator and record the frequency response of the PT331C
<DocScrutinizer05>
obviously you would want to trigger on first rising edge of the wobbled squarewave after sharp edge of wobbling sawtooth signal
<DocScrutinizer05>
ideally you would sync the wobbling signal to the square wave though
<DocScrutinizer05>
in the wave generator
NIN101 has quit [Remote host closed the connection]
NIN101 has joined #neo900
NIN101_ has joined #neo900
NIN101 has quit [Read error: Connection reset by peer]
<DocScrutinizer05>
MSO-S version would have had its merits
<DocScrutinizer05>
but not that many merits to pay more than twice the price
<Openbot>
I love those chineese critters exessive value for money :p
Openbot has quit [Ping timeout: 258 seconds]
Openbot has joined #neo900
<DocScrutinizer05>
freemangordon: ^^^ you'll *love* this
<DocScrutinizer05>
>>The I/O target automatically updates the SHA-1 hash every time we made changes in the 1bl code space, enabling us to do cute things like interactively patch and disassemble code within the emulated ROM space.<< \o/
Openbot has quit [Read error: Connection reset by peer]
<DocScrutinizer05>
WOW! sorry for long paste, but... >>Because of the difficulty in trying to locate critical blocks, and because JTAG is multiplexed with critical functions on the target device, an unconventional approach was taken to attach a debugger: xobs emulates the ARM core, and uses his fernly shell to reflect virtual loads and stores to the live target. This allows us to attach a remote debugger to the emulated core, bypassing the need for JTAG
<DocScrutinizer05>
and allowing us to use cross-platform tools such as IDA on x86 for the reversing UI.<<
<DocScrutinizer05>
Bunnie is *awesome*
APic has joined #neo900
<kerio>
who's bunnie
<kerio>
is it fluffy and white
Kabouik has quit [Remote host closed the connection]
Kabouik has joined #neo900
<DocScrutinizer05>
maybe, who knows
<DocScrutinizer05>
do you really think true EE even notice such negligence as physical appearance?
<bencoh>
this article is awesome
<DocScrutinizer05>
yes!!
<DocScrutinizer05>
even when you skip the complete middle part
<DocScrutinizer05>
I'm really envy about Bunnie's writing skills
<bencoh>
"automated fuzzing of unknown hardware blocks" :))
<DocScrutinizer05>
and also about his energy to cope with insurmountable workloads
<DocScrutinizer05>
hehe
<DocScrutinizer05>
yeah
<DocScrutinizer05>
awesome, no?
<DocScrutinizer05>
also his franken-qemu which really is beyond me at first read
<bencoh>
dont spoil, I'm about to read that part :p
<DocScrutinizer05>
incredible groundbreaking stuff done en passant, just for tooling
<DocScrutinizer05>
err instrumentation, maybe
<DocScrutinizer05>
freemangordon will love to see IDA integrated into qemu integrated into remote GDB of sorts
<DocScrutinizer05>
"beachhead" hehe
<DocScrutinizer05>
when this was a beachhead, they should call the project D-Day
<bencoh>
what I dont understand is how the "fernly shell interface" works
<bencoh>
is that plain serial ?
<DocScrutinizer05>
nfc
<DocScrutinizer05>
oooh, no, the hw interface is via their dual ported ROMulator
<DocScrutinizer05>
basically mmap()
<DocScrutinizer05>
aiui
<kerio>
DocScrutinizer05: btw i'm sure you'll be happy to know that the next cssu-t will offer a new kernel and thumby packages :3
<DocScrutinizer05>
*shrug*
<DocScrutinizer05>
I'm glad the guys finally made it
<DocScrutinizer05>
I hope they really did
<kerio>
the cssu kernel is going to be silly
<DocScrutinizer05>
extremely risky migration
<kerio>
it's got *some* improvements
<kerio>
but not stuff like usb host mode
<DocScrutinizer05>
no complaints about that from my side. It's a sane decision
<DocScrutinizer05>
o.O
<DocScrutinizer05>
lag: 2s
<DocScrutinizer05>
~ping
<infobot>
~pong
Kabouik has quit [Remote host closed the connection]
Kabouik has joined #neo900
lexik has quit [Ping timeout: 256 seconds]
lexik has joined #neo900
Openbot has joined #neo900
<Openbot>
~Ping
<infobot>
~pong
<Openbot>
~Ping
<infobot>
~pong
<Openbot>
3 sec lag now omg any one ele experincing or shoud i shoot a mail to my isp ?
<DocScrutinizer05>
could you please see last ~8 lines backscroll? And a tad less offensive bashing than "Are you drunk?" in /query would help your karma a lot
<Openbot>
Or is this those freenode ddos scripties you guys talk about ?
<DocScrutinizer05>
:-(
<Openbot>
I read log then i said its lag :p btw thats not bashing lol
<DocScrutinizer05>
querying the chanop with "are you drunk? what did you do?" when encountering a lag on irc for sure is bashing and evil insult
<Openbot>
Ok what is tl;dr and iot
<kerio>
the fuck
<Openbot>
Ok ok i didnt mean that way its chrismas and new year eve here sorry :(
<DocScrutinizer05>
ooh, the time of love, peace, and kind insults - I see
<Openbot>
Kerio sexy
<DocScrutinizer05>
I got a recommended read for you, Openbot:
<infobot>
somebody said netiquette was a set of guidelines that makes the people on the Internet live together in peace and harmony, well, at least in theory, or at http://www.fau.edu/netiquette/netiquette.html, or found at ftp://ftp.ripe.net/rfc/rfc1855.txt
<Openbot>
Btw in the link what the op is doing i didnt get that ? And that chip $3 ?
<Openbot>
Ok better i read em first ;
<Openbot>
Bitter to digest a couple of lines :p
<Openbot>
Humm
<DocScrutinizer05>
~wtf tl;dr
<infobot>
usage: wtf <foo>.
<DocScrutinizer05>
~tl;dr
<DocScrutinizer05>
tzzz
<DocScrutinizer05>
~wtf iot
<infobot>
Gee... I don't know what iot means...
<DocScrutinizer05>
~wiki tl;dr
<Openbot>
Well didnt get that :(
<infobot>
At http://en.wikipedia.org/wiki/Tl;dr (URL), Wikipedia explains: "{{wiktionary|TL;DR}} {{For|the Wikipedia essay|WP:Too long; didn't read}} 'TL;DR', an acronym for "'Too long; didn't read'", is Internet slang used in reply to a lengthy online message. It is also used at the beginning of a summary of such a message. The phrase dates back to at least 2004,{{cite web| title= tl;dr |url= http://boards.theforce.net/threads/tl-dr.15047069/ | |date=Feb 26, ...
<Openbot>
Ok
<Openbot>
So what that guy is doing with that mtk chip ?
<DocScrutinizer05>
reverse engineering it to the bones :-)
<DocScrutinizer05>
it's basically a powerful yet cheap chip, but comes without any proper datasheets/docs how to use it. So Bunnie dissected it into molecules, virtually, to learn how to use it
Openbot has left #neo900 [#neo900]
<kerio>
can we use it in the neo900
<DocScrutinizer05>
no, not really
<kerio>
:(
<kerio>
can i get a neo900 with an i7
<DocScrutinizer05>
next week
<DocScrutinizer05>
the relevance of bunnie's blogpost for Neo900 is more in the general analysis of IP situation in Asia vs western world
<DocScrutinizer05>
thus focus on intro and end of the post, it has the more general not-so-technical stuff
<DocScrutinizer05>
which would make a separate great blogpost of its own
<freemangordon>
DocScrutinizer05: IDA already has integration with gdb (incl remote)
<fling>
DocScrutinizer05: how to disassemble gta02 case? :P
* fling
can't get to the mobo…=
paulk-collins has quit [Ping timeout: 256 seconds]
<DocScrutinizer05>
disassemble GTA02? Duh, that's simple: unscrew the two Torx near lanyard hole, then simply pry open
<fling>
DocScrutinizer05: unscrewed but it is not opening…
<DocScrutinizer05>
IIRC I used the trick to *carefully* push in aux button a bit with my fingernail, then pull up on case plastic and slide in fingernail into the gap
<fling>
I will try this method ;>
<DocScrutinizer05>
BEWARE to push aux too hard!
<DocScrutinizer05>
it will break when you push in too hard
<DocScrutinizer05>
actually you can force your fingernail between upper lid and case shell at the corner where aux button window ends
<DocScrutinizer05>
no need to "pull"
<DocScrutinizer05>
just make sure the force is sideways towards the gap beween lid and case, not downwards to push in the aux button
<DocScrutinizer05>
then slide the fingernail along the complete circumference of case and the latches snap open
<wpwrak>
a credit card or such is great for opening GTA01/02
<DocScrutinizer05>
I guess a credit card is already too thick
<wpwrak>
or - even better - a guitar pick, if you happen to have one
<DocScrutinizer05>
guitar pick aka plektrum
<wpwrak>
DocScrutinizer05: i used CCs all the time :)
<DocScrutinizer05>
hey, you beat me on it
<DocScrutinizer05>
I used fingernails all the time
<DocScrutinizer05>
I wonder if the procedure "unscrew the screws 1.5 turns, then push them in hard intil lid pops off" could work as well
<DocScrutinizer05>
but yeah, sorry, it's not as simple as I thought to recall it was
<dos1>
yeah, I struggled with opening my gta02 the first time
<wpwrak>
the screw trick sounds evil ;-)
<DocScrutinizer05>
when you pry it open from aux button, start sliding towards the long side, not towards the round side
<dos1>
it felt like it would break if I pulled a bit harder, but if I didn't it wasn't opening
<wpwrak>
dos1: break the gta01/02 case ? in your dreams ;-)
<DocScrutinizer05>
I guess GTA02 cass cannot break. It doesn't know how to do that
<DocScrutinizer05>
;-)
<DocScrutinizer05>
case*
<dos1>
yeah, that was just it. "felt" :)
<DocScrutinizer05>
yay, touched a GTA02 first time for at least one year :-D
<DocScrutinizer05>
funny enough first try works just fine, like I described, and with all the description I seem to have forgotten how to do it
<DocScrutinizer05>
;-)
<DocScrutinizer05>
ok, now when I stopped thinking about what I'm doing, it works again. Eeeeasy
<DocScrutinizer05>
fingernail of right hand middle finger, holding device with left hand (left thumb near aux). Sliding fingernail "towards me"
<DocScrutinizer05>
matter of 0.3s
<DocScrutinizer05>
then it gets tough, particularly with new case that never got opened yet
<DocScrutinizer05>
when you think your fingernail got completely stuck between lid and case, it will snap open on the next 1mm
<DocScrutinizer05>
that's happening when you're about at middle of long side
<DocScrutinizer05>
X-P killing nepomuk freed up ~50% of my RAM. Of course it got restarted instantly but it noticed that mail is 100% indexed, and I suspended it. Hope that keeps it from eating my RAM again
xes has quit [Ping timeout: 240 seconds]
xes has joined #neo900
xes has quit [Read error: Connection reset by peer]
MonkeyofDoom has quit [Remote host closed the connection]
trx has quit []
<SylvieLorxu>
nepomuk? KDE dropped that in favor of Baloo on 4.13.4 or so
mvaenskae has quit [Ping timeout: 244 seconds]
<kerio>
what the fuck is "baloo" supposed to be
<kerio>
is this The Jungle Book
<Pali>
DocScrutinizer05: :D:D:D nepomuk kde shit? :D
<DocScrutinizer05>
yoh
<Pali>
DocScrutinizer05: you can disable nepomuk in systemsettings
NIN101_ has quit []
<DocScrutinizer05>
I know, but then it fscks up kmail
<Pali>
downgrade to my kmail version :-)
<Pali>
ehm... it is upgrade
<DocScrutinizer05>
I would if I could install a RPM
NIN101 has joined #neo900
<DocScrutinizer05>
building KDE stuff is a nightmare
<DocScrutinizer05>
SylvieLorxu: Platform Version 4.11.5
<Pali>
it is better then building gnome stuff...
<DocScrutinizer05>
gonna update to new distro version soon
<DocScrutinizer05>
kerio: (jungle book) worse, this is KDE
<SylvieLorxu>
Building KDE stuff is a nightmare?
<SylvieLorxu>
# emerge kde-meta
<DocScrutinizer05>
yes
<SylvieLorxu>
:D
<DocScrutinizer05>
lol
<DocScrutinizer05>
maybe on a debian system, or gentoo or whatever
<kerio>
apt-get build-dep kde
<DocScrutinizer05>
I once built an own kmail version, took me ~20h until it "worked", and the result been that kmail been *completely* useless since it didn't know about contacts and thus email addresses and generally wasn't integrated into KDE anymore
Pali has quit [Remote host closed the connection]
<kerio>
LOL
<kerio>
maybe you should give up with this "software" thing doc
<kerio>
focus on electrons and ways to move them
nox- has joined #neo900
trx has joined #neo900
trx has quit [Changing host]
trx has joined #neo900
<DocScrutinizer05>
wut? if you love building frankenstein KDE apps, go ahead show me you can do it
<DocScrutinizer05>
pack it in a nice rpm or even just provide the binary, and I'll consider what you said
<DocScrutinizer05>
given the thing *works*
<DocScrutinizer05>
I'm absolutely sure it's a matter of 10 minutes for you to patch kmail in a way so it doesn't rely on akonadi anymore, but still can access contacts (which happen to be stored in... akonadi)
<DocScrutinizer05>
oooh, and while you're at it, you probably can tame akonadi so it doesn't start polling my mail accounts after boot even when no mail client at all is running
<kerio>
but doc
<kerio>
how will you get push notifications on your compatible handheld device otherwise?
<DocScrutinizer05>
when you've done all this, the minor problem of searching fulltext in mails is only a negligence
<nox->
anyone know which version the maemo bugilla is at?
<kerio>
i'd point you in the direction of grep, but i bet mails aren't stored as text
<DocScrutinizer05>
I'd point you in the general direction of maemo
<DocScrutinizer05>
maybe contatc council, or worst case directly techstaff
arcean has quit [Quit: Application terminated!]
<SylvieLorxu>
>Vulnerability researches
<SylvieLorxu>
>Critical vulnerability report
<SylvieLorxu>
>Posted on public location
<kerio>
hahah he actually created admin@mozilla.org
<nox->
yeah...
<freemangordon>
I'll look at that tomorrow
<nox->
ok
gottosortoutanic has joined #neo900
gottosortoutanic is now known as astr
<Oksana>
Good morning. Off-topic: Have you heard of stylus based on dart? A bit too thick for N[eo]900 case, though, I expect. Especially considering that N900's stylus is not-round.
<Oksana>
There are plenty of capacitive "pens" on the market, but they tend to be really bulky. Thicker that 1mm-thin stylus.
paulk-collins has quit [Quit: Quitte]
kolp has quit [Remote host closed the connection]
lexik has quit [Ping timeout: 245 seconds]
<Oksana>
The problem is, with resistive you prefer to have precision, and thus stylus needs to be thin. With capacitive, for stylus to be noticed, it needs to be either thick (most) or made of really capacitive material (metal scratches the screen, remember).