AnthonyMalczanek has quit [Ping timeout: 244 seconds]
freemangordon has quit [Ping timeout: 245 seconds]
freemangordon has joined #neo900
qwazix has joined #neo900
dal2 has quit [Ping timeout: 250 seconds]
antiatom has joined #neo900
_whitelogger_ has quit [Ping timeout: 252 seconds]
_whitelogger_ has joined #neo900
ZetaR has quit [Quit: Leaving.]
paulk-collins has joined #neo900
paulk-collins has quit [Excess Flood]
paulk-collins has joined #neo900
paulk-collins has quit [Ping timeout: 256 seconds]
jonsger has joined #neo900
cybiko123 has joined #neo900
cybiko123 has quit [Changing host]
cybiko123 has joined #neo900
enyc has joined #neo900
<enyc>
DocScrutinizer51: getting any success with 'action needed:' emails previously discussed ??
<edwin>
DocScrutinizer05: seen something in channel log about issues with Paypal. If I got the payment confirmation email from neo900.org does that mean everything is OK with Paypal?
qwazix_ has joined #neo900
paulk-collins has joined #neo900
jonsger has quit [Ping timeout: 246 seconds]
paulk-collins_ has joined #neo900
qwazix_ has quit [Quit: Ex-Chat]
paulk-collins has quit [Ping timeout: 246 seconds]
lobito has quit [Ping timeout: 248 seconds]
lobito has joined #neo900
<DocScrutinizer05>
enyc: still pending
<DocScrutinizer05>
edwin: don't worry, everything OK for you
<edwin>
k
<DocScrutinizer05>
edwin: you actually should also have received a mail from shop
<DocScrutinizer05>
unless you missed to do a preorder
<edwin>
I got a [Neo900] payment accepted on 06/23/2015
<DocScrutinizer05>
see? :-)
<edwin>
:)
paulk-collins_ has quit [Ping timeout: 255 seconds]
paulk-collins_ has joined #neo900
paulk-collins_ has quit [Ping timeout: 255 seconds]
<enyc>
DocScrutinizer05: oh ok hopeing teh project not lost impetus...
<DocScrutinizer05>
sort of heat throttle
<enyc>
hrrm, finishing things always difficult
<enyc>
how many board-spins away etc.?
<DocScrutinizer05>
enyc: we hope for 2
<enyc>
DocScrutinizer05: how well are you able to test the board given non-completed ported-OSes etc ??
<DocScrutinizer05>
alas recently Nikolaus is busy with dragonbox pyra so we have a delay of 6 weeks
<DocScrutinizer05>
enyc: 100%
<DocScrutinizer05>
actually ported OS is not really helpful for testing the hw
<DocScrutinizer05>
not much at least
<enyc>
hrrm i mean you can work out your own contrived test cases?
<enyc>
but I ould think in some ways that only a ''real usage'' wil find *some* edge-cases ??
<DocScrutinizer05>
testing is done subsystem by subsystem, function by function
<enyc>
sure but what about weird coherency and lockup bugs that only happen when all used in certain combinations at once?
<DocScrutinizer05>
those need to get avoided in design phase, and that's usually pretty easy
<enyc>
and I suppose (much) of that mess is already sorted in the GTA04 board test already?
<DocScrutinizer05>
yes, that too
<enyc>
now more about ''attaching neo900 ancillaries''
<enyc>
are the n900 / gta02 displays sufficiently similar driver interfaces, just different resolutions/layout ?
<DocScrutinizer05>
no
<DocScrutinizer05>
we'll need and use the N900 display driver
* enyc
looks up taht neo900 hardware diagram whatnot
<enyc>
does that bit work now tested/integrated ?
<DocScrutinizer05>
sorry?
<enyc>
does the n900 display driver on the neo900 board spin work so far?
<DocScrutinizer05>
it's planned to interface BB-xM display interface to proto-v2
<enyc>
sounds like an important hurdle to get sorted =)
<DocScrutinizer05>
no hurdle at all
<enyc>
random older hardware question: do you happen to know anybody with old intel-440BX-chipset dual cpu motherboard (i.e. 2*slot 1 or 2*skt-370) spare?
<DocScrutinizer05>
no probelms expected with that one
<DocScrutinizer05>
(440bx) sorry, nope
<DocScrutinizer05>
(display) the display is tested with omap3 platform and evidently works, see N900
<enyc>
so now waiting for nikolaus ? i think some wiould be happer with a semi-organized page of 'known tasks and issues to resolve for completion'... end is in sight etc =)
<enyc>
i think that may look good towards those to put down-payments etc
ZetaR has joined #neo900
dal has joined #neo900
dal is now known as dal2
<enyc>
odd list to resources page or similar, even if continuously updated page
<DocScrutinizer05>
yes, such a page would make sense
<enyc>
probably help you to sort out the dependencies too while Nokolaous busy? ;-)
<enyc>
I've been maknig losts on my own messes in middled of sorting out , been taking an 'opportunistically resolving' approach to increase Throughput over Latency generally =)
<enyc>
DocScrutinizer05: if yo ushow me adraft list I'd be really interested to comment/question from pov of somebody ntot fallowing in high det'ail, which may help to show to many of your potentialy-purchasters
jonsger has joined #neo900
arossdotme has quit [Ping timeout: 248 seconds]
arossdotme has joined #neo900
che1 has joined #neo900
che1 has quit [Ping timeout: 264 seconds]
ccnnjj has joined #neo900
che1 has joined #neo900
norly has joined #neo900
dal2 has quit [Quit: Leaving]
sparetire_ has joined #neo900
user456_ has joined #neo900
dal has joined #neo900
dal is now known as dal2
nicksydney_ has joined #neo900
nicksydney has quit [Ping timeout: 244 seconds]
dal2 has quit [Quit: Leaving]
_whitelogger_ has joined #neo900
dal has joined #neo900
nicksydney_ has quit [Ping timeout: 244 seconds]
dal is now known as dal2
Seylerius has joined #neo900
nicksydney has joined #neo900
ashneo76 has joined #neo900
<DocScrutinizer05>
commercial: "the highspeed flatrate for just 9.99 - with 500MB high speed LTE" -- ROTFL, this is equivalent to 40 seconds of full speed download
ZetaR has quit [Quit: Leaving.]
ZetaR has joined #neo900
user456_ has quit [Quit: Page closed]
arcean has joined #neo900
arcean has quit [Read error: Connection reset by peer]
jake42 has quit [Ping timeout: 252 seconds]
jake42 has joined #neo900
vizzy has joined #neo900
<vizzy>
hey ho. i have a suggestion for 2 feature in the neo900 if not already included
ZetaR has quit [Quit: Leaving.]
norly has quit [Quit: Leaving.]
<vizzy>
charging/external power: i know that from acpi on thinkpads, if i connect a 2nd battery, i can tell my tp to discharge bat1 first, or eg bat2 first. this would be a great feature in the neo900 too i think. connect external battery, and choose e.g. a) charge internal b) discharge internal and switch to external c) discharge external powersource first, then switch to internal, and setting thresholds would be cool too. i dont really know if this
<vizzy>
makes much sense in a mobile phone :) just an idea
ZetaR has joined #neo900
<DocScrutinizer05>
easy to retrofit with a simple circuit with 2 power-FETs on hackerbus
<DocScrutinizer05>
rest is software
<vizzy>
check if power on or off...: sometimes i have the situation with my n900 that it seems to sleep and react very very slowly... e.g. black screen, backlight off, and coming back after 2 or 3 minutes slowly (whatever it does, indexing maybe? ) ... or sometimes it switches off unexpectedly... so i watch my phone and ask myself: is it still running and has power? or is it powered off
dal has joined #neo900
<vizzy>
so a solution to check if there is power on very easyly would be cool
dal2 has quit [Read error: Connection reset by peer]
dal is now known as dal2
<vizzy>
DocScrutinizer05, so i definitely need the hackerbus breakout adapter :)
<DocScrutinizer05>
ooh wait, actually the 'internal' battery is not that simple to _not_ get used when inserted
<vizzy>
but maybe hold on charge while using external
<Pali>
acpi... pfff
<Pali>
some "hacker" acpified my bq2415x driver!
<vizzy>
acpi is better than no acpi :)
<vizzy>
ah, no, tpsmapi was it, not acpi
<vizzy>
*confused*
<vizzy>
however, some method to ballance charge and discharge internal and external power :)
<Pali>
everything is better then acpi!
<Pali>
no acpi is the best solution
<vizzy>
k .)
<Pali>
which idiot invented it?
<DocScrutinizer05>
for the power issue (apart from such freezen shouldn't happen on Neo900) there shall be some diagnostic LEDs that are hardwired to certain states of device and not disable-able
<vizzy>
DocScrutinizer05, aah, that sounds good
<vizzy>
i fotentry then to shutdown my n00, ... doesnt work, and often enough i opened the back just when it came back.... grml
<vizzy>
he? ^
<DocScrutinizer05>
generally I want ultra-low power diagnostic LEDs for all significantly power consuming states, like modem sending, CPU not in sleep mode (master clock enabled) etc
<vizzy>
i often try then to.... ^^
<Pali>
it is idiotic to need VM inside kernel (running at ring0) which execute 3rd code
<vizzy>
DocScrutinizer05, yes please :) i love leds and blinkning stuff - if it ha a meaning
<vizzy>
haS a meaning...
* DocScrutinizer05
too
<DocScrutinizer05>
however the LEDs will be placed in a way so it's easy to cover them for those who don't like them
<DocScrutinizer05>
I thought about a place above kbd, almost under the display when slid open
<vizzy>
mmmh.
<DocScrutinizer05>
it occurs to me that breathing light (power-indicator) on indicator LED is a silly design since it's not built like a watchdog
<vizzy>
maybe a diagnostic plug?
<DocScrutinizer05>
what for?
<vizzy>
plugi and get a full light show of all in/output...
<DocScrutinizer05>
(breathing light) on N900
<DocScrutinizer05>
resp maemo
<vizzy>
like the ... loopback adapters for rs232 or parallel interface
<vizzy>
yeah, the breathing light is nice, but it also stucks when the n900 hangs up and is still running
<DocScrutinizer05>
there shall be LEDs for e.g. VBUS. And UART3 TX, in parallel to the high power IR-LED
<DocScrutinizer05>
the N900 breathing light would work on even when CPU is removed hard from PCB while the device is on
<vizzy>
?
<DocScrutinizer05>
since the LP5523 program is a silly endless pattern
<DocScrutinizer05>
the indocator LED is 100% autonomous
<vizzy>
ok, didnt know that
<vizzy>
alway thought it may be off because something is still needed to trigger it
<DocScrutinizer05>
the LP5523 is even powered by VBAT_LEDS and thus the indicator LED *could* run on even when the CPU and whole device is shut down completely
<DocScrutinizer05>
if it wasn't for RGB_CTL_EN signal to chip's EN pin
<vizzy>
ah, so its the complete other way, the indicator may lie about the on off status :)
<DocScrutinizer05>
yes
<DocScrutinizer05>
but you could write a engine-code (aka pattern) that doesn't run endless but needs frequent retriggers from CPU, like once every 5 s
<DocScrutinizer05>
otherwise it switches to a significant error state
<DocScrutinizer05>
that *would* indicate CPU freezes
<vizzy>
with the pattern editor which is 'included'?
<DocScrutinizer05>
sure, should work
<vizzy>
ah nice, ill figure that out
<DocScrutinizer05>
of course you need a watchdog-trigger on AP-CPU then too
<DocScrutinizer05>
easy: 5 lines of bash code should suffice, using I2C-set
<DocScrutinizer05>
there's a "user var" register in LP5523 which can get used in pattern code conditional commands
<DocScrutinizer05>
and in arithmetic
<DocScrutinizer05>
and you can set it via I2C-cmd
<DocScrutinizer05>
somebody wrote a code for LP5523 that calculates primes
<vizzy>
lol
<MonkeyofDoom>
brilliant
<DocScrutinizer05>
I guess it's limited to 8bit size for the prime
<vizzy>
oh, so no bitcoins, sh....
<DocScrutinizer05>
hehe
<DocScrutinizer05>
yeah, a pity, particularly since we got THREE of those MCUs in every LP5523
Pali has quit [Read error: Connection reset by peer]
che1 has quit [Ping timeout: 276 seconds]
<Oksana>
I thought about a place above kbd, almost under the display when slid open - Cool! (a engine-code (aka pattern) that doesn't run endless but needs frequent retriggers from CPU, like once every 5 s) How does it work? (a "user var" register in LP5523 which can get used in pattern code conditional commands) Okay... Sounds complicated (somebody wrote a code for LP5523 that calculates primes)...