<wpwrak>
if you run that on the latex source of the header document (in the same repo), it'll list matching connectors that meet the query criteria in that script
<wpwrak>
the ones set there are a bit different from what we eventually used (usb single vs. double row, and also pinning of some parts), but that's easy to adapt
* DocScrutinizer05
heads out for an hour of chilling
<wpwrak>
much more convenient than going through those 1440 combinations manually :)
sparetire has quit [*.net *.split]
illwieckz has quit [*.net *.split]
timclassic has quit [*.net *.split]
jake42 has quit [*.net *.split]
mva has quit [*.net *.split]
sparetire_ has quit [*.net *.split]
ShadowJK has quit [*.net *.split]
ds2 has quit [*.net *.split]
xes_ has quit [Ping timeout: 246 seconds]
sparetire has joined #neo900
illwieckz has joined #neo900
timclassic has joined #neo900
jake42 has joined #neo900
mva has joined #neo900
sparetire_ has joined #neo900
ShadowJK has joined #neo900
ds2 has joined #neo900
sparetire has quit [*.net *.split]
illwieckz has quit [*.net *.split]
timclassic has quit [*.net *.split]
jake42 has quit [*.net *.split]
mva has quit [*.net *.split]
sparetire_ has quit [*.net *.split]
ShadowJK has quit [*.net *.split]
ds2 has quit [*.net *.split]
sparetire has joined #neo900
illwieckz has joined #neo900
timclassic has joined #neo900
sparetire_ has joined #neo900
jake42 has joined #neo900
mva has joined #neo900
ShadowJK has joined #neo900
ds2 has joined #neo900
<Oksana>
So, USB reverse-feed means battery charging through hacker-bus-USB?..
sparetire has quit [Max SendQ exceeded]
<Oksana>
Secondary I2C is interesting...
sparetire has joined #neo900
<DocScrutinizer05>
USB VBUS "reverse feeding" is VBUS in aka "charging", yes
<DocScrutinizer05>
the HB VBUS oin is a straight wire duplicate of the USB jack VBUS oin
<DocScrutinizer05>
pin*
<DocScrutinizer05>
so when you attach a charger to USB jack you get the 5V from charger on HB VBUS
<DocScrutinizer05>
when you attach a charger to HB VBUS the device will charge as well
<DocScrutinizer05>
when you enter hostmode resp boosting, device will provide 5V on VBUS both on USB jack and on HB
ilon has quit [Ping timeout: 264 seconds]
ilon has joined #neo900
<DocScrutinizer05>
Secondary I2C is "interesting", yes. However note please that you can bitbang I2C on GPIO without any problem
<DocScrutinizer05>
AAAAND it just occurs to me we missed out on a very relevant detail: Several of the GPIO are also capable to trigger IRQ, even wake IRQ
<DocScrutinizer05>
and we want hw powerputton on one secondary function
<DocScrutinizer05>
powerbutton
<DocScrutinizer05>
well, maybe tertiary
<DocScrutinizer05>
also camera strobe etc will be available on tertiary, using wire jumpers
<wpwrak>
i think pretty much all GPIOs on the OMAP are interrupt-capable. so that's implicit :)
<DocScrutinizer05>
yes, that's why we forgot to mention it
ilon has quit [Ping timeout: 264 seconds]
<DocScrutinizer05>
however we need to provide such info for community review of our concept
ilon has joined #neo900
<DocScrutinizer05>
ouch! mquin gone evil
<DocScrutinizer05>
freenode is doomed ;-)
<DocScrutinizer05>
~ping
<infobot>
~pong
kolp has quit [Disconnected by services]
kolp_ has joined #neo900
Humpelstilzchen has joined #neo900
pabs3 has joined #neo900
<pabs3>
DocScrutinizer05: what tool do you use for syncing the µBlog on your website to Twitter?
Defiant has quit [Ping timeout: 256 seconds]
<pabs3>
(the Debian publicity team we are thinking about doing something similar)
<dos1>
pabs3: our µblog is operated by simple shellscript, which at the end of its execution simply sends http request to twitter
<dos1>
(and some oauth login before that, but that's actually done by a snippet found on the internet ;))
<dos1>
it's not there, it's pretty specific to our server configuration (for instance determines user name from logged in unix user, handles permissions etc.)
<dos1>
but its output is basically a html file for pelican (basic template), automatic regeneration and deploy of the site (server specific) and twitter post
<DocScrutinizer05>
dos1: could you add HB whitepaper to resources page please?
<DocScrutinizer05>
and maybe replace the OSHW text under "news" by one sentence about it. Whatever goes there, it's fne as long as the >>Don't miss this year's OpenPhoenux Hard & Software Workshop in Munich, Germany on November 29-30.<< vanishes ;-)
<DocScrutinizer05>
a sidenote on links to tmo: please try to use "showthread" instead of "showpost". The latter does center aligned and shows only the single post intead of the thread it's in
<DocScrutinizer05>
yeah, those guys nust suffer massive fs corruption ;-)
<DocScrutinizer05>
must*
* Oksana
has fsck running on N900-CSSU-Testing at almost every start-up - takes about three or four minutes
<DocScrutinizer05>
that's nasty
<DocScrutinizer05>
and worrying
<Oksana>
What is the trigger for fsck in CSSU Testing?
<DocScrutinizer05>
unclean flag in fs
<bencoh>
I wouldnt do that ...
<DocScrutinizer05>
aiui
<bencoh>
oh, you mean it runs automagically ?
<DocScrutinizer05>
err yes, that's what maemo does
norly has joined #neo900
<Oksana>
Yes. So, what is the trigger - is it being forcibly (power-button) shut-down by the user, or is it being discharged to red-battery-shut-down, or is it changing battery not quickly enough to avoid date-time-loss?
* Oksana
honestly lost track of when fsck does and doesn't run...
<DocScrutinizer05>
1 and maybe 2 (2 depending on bme et al)
<DocScrutinizer05>
1 for sure
<DocScrutinizer05>
3 is unrelated
<Oksana>
And I do wait for shut-down-finished system sound before changing batteries. Or should I wait an additional minute or two after the sound happens?
nox- has joined #neo900
<DocScrutinizer05>
2 usually shouldn't be a problem, system shall shut down gracefully on low batt
<dos1>
hmm... I've seen fsck forcing the check due to timestamps on fs being set "in future"
<DocScrutinizer05>
OOOOOOOHOOOHOH
<dos1>
not on n900 though
<DocScrutinizer05>
system shuts down for another 20s even after it seems completely off
<DocScrutinizer05>
*never* remove battery too quickly after shutdown
<Oksana>
Ok, so I would better wait for a minute after the shut-down sound goes off, before changing batteries...
<dos1>
Oksana: lifehack: modify LED patterns and make the shutdown one end with some light still being on - you will see when it truly shuts down :)
<Oksana>
Will do.
<DocScrutinizer05>
yes. Or until - on pressing power button shortly(!) - the white ondicator light immediately starts shining
<dos1>
but that one will work only with r&d mode being disabled
<DocScrutinizer05>
immediately after shutdown you'll notice that the white indicator light does _not_ shot up on pressing powerbutton
<DocScrutinizer05>
s/shot/show/
<DocScrutinizer05>
his is since the bootloader doesn't get started yet on press of power button, since the system is still shutting down
<bencoh>
that's how I check as well :)
<DocScrutinizer05>
when system is truly down, power button starts bootloader on no time, and bootloader ramps up white LED and shuts down immediately when you release power button sooner than 2s after pressing it
<DocScrutinizer05>
so: press power button for <0.5s,, when short white light it's safe to swap battery. when no light, (or steady light) it's not!
<Oksana>
I would rather change LED pattern to something which shines as long as the system is still here
<DocScrutinizer05>
and: disobeying that rule *will* result in fs corruption and fsck
<DocScrutinizer05>
Oksana: sure. That's the smart way. Mine is the lazy way
<DocScrutinizer05>
both work
<DocScrutinizer05>
dos is the smart guy here ;-)
<Oksana>
Power-button-press-check is too much like compulsory phone checking - check, check, check again...
<DocScrutinizer05>
but it will teach you patience ;-)
<DocScrutinizer05>
you can get away without _any_ checking: simply wait >90s ;-P
<DocScrutinizer05>
btw every user runs into this issue: on reboot
<Oksana>
Then I will forget to change the battery altogether ;-P
<DocScrutinizer05>
symptom: you cannot start up device immediately after shutdown
<Oksana>
Ok, is there a rainbow-style pattern? Like, red-orange-yellow-green-cyan-blue-violet-repeat?
<DocScrutinizer05>
no, it cannot
<DocScrutinizer05>
since engine3 is occupied by MCE for kbd backlight ramp-up-down
<dos1>
spoiler alert: it will be possible on neo900 :D
<DocScrutinizer05>
and the 16 steps of prog code are too short for fancy LED remapping
<Oksana>
Rrr-meow... Thank you for spoiler alert :-)
<DocScrutinizer05>
it's also possible with hacked MCE
<Oksana>
hacked?
vakkov has quit [Remote host closed the connection]
<DocScrutinizer05>
kbd backlight 500ms ramp __really__ can be done in software
<DocScrutinizer05>
you do not at all need a fancy LP5523 engine for that
<DocScrutinizer05>
and with 3 engines you obviously can create all the fancy rimbow patterns youlike
<DocScrutinizer05>
rainbow*
<DocScrutinizer05>
dos1: good point, on Neo900 we got kbd backlight away from LP5523 to a dedicated controller (actually 2 iirc)
<Oksana>
The 6 for kbd are going to be RGB, too, right?
* Oksana
would find it funny if, on incoming call, the kbd (when open) would have half-green, half-red backlight, and pressing on a key would either answer or reject the call, depending on which half of keyboard it is in...
<dos1>
yup, "Keyboard LEDs (6 x MSL0201RGB)"
<Oksana>
Not particularly power-saving, but helps for broken-screen case...
<dos1>
hehe :)
<dos1>
well, the white leds are lit anyway, so it won't really be more power-hungy than on n900 now
<Oksana>
I thought that slide2answer allows one to answer a phone call by sliding open the keyboard; but it turned out that slide2answer is slide-the-knob on the touch-screen, so not exactly helpful. Still, an excellent starting point...
<DocScrutinizer05>
IF we manage to get kb backlight to work *at all* - given the nasty domesheets issue
<DocScrutinizer05>
Oksana: slide-to-answer would make so damn much sense using the kblock sliderswitch to answer call. Absolutely immune against accidentally accepting calls. And works without screen as well. Muting call is already handled by "face down" gesture. So what's missing then was "reject" which might get done by e.g.power button doubleclick
<DocScrutinizer05>
or cam trigger doubleclick, if you prefer
fling has quit [Ping timeout: 252 seconds]
<DocScrutinizer05>
I consider the lack of any such hw-button-based phone function a major design flaw of maemo, culprit; Nokia
<DocScrutinizer05>
there's headroom for improvement in maemo UX
<DocScrutinizer05>
actually all such details SHOULD get handled in a user-config
<Oksana>
I wonder whether current slide2answer replaces incoming-call window, or simply puts itself above it...
<DocScrutinizer05>
the latter
<DocScrutinizer05>
tricky stuff
<Oksana>
[Shudders] Replacing would have been better. But difficult.
<DocScrutinizer05>
I suggested to patch the dialer (maybe via LD_PRELOAD) to replace the gtk pushbuttons (red, green) by slider buttons
<DocScrutinizer05>
if only somebody would RE that dang dialer. Can't be THAT hard
<DocScrutinizer05>
I mean, what's in there? a silly GUI to eneter digits plus a half a dozen function buttons. A dropdown menu to select the connectivity (cmt, SIP, ...). A textbox to display ascii info. And a dbus interface sending and receiving signals/msgs
<DocScrutinizer05>
NB dialer and call history SHOULD be separate binaries
<dos1>
if that dialer handles the "during the call" window, then there's also video call support
<DocScrutinizer05>
oooh, plus there's that USSD/SCC dialog, prolly also inside dialer
<DocScrutinizer05>
HAH, viedo. Good point
<DocScrutinizer05>
dos1: ta! :-)
<DocScrutinizer05>
anyway video most likely is a silly mafw interface plus an overlay
<DocScrutinizer05>
compositor stuff
<DocScrutinizer05>
I bet you could make that video "window" show up in arbitrary context on top of arbitrary apps' GUI
<DocScrutinizer05>
wouldn't be surprised if that was mediaplayer (also based on mafw) in a special windowed (non-fullscreen) mode
<DocScrutinizer05>
to start with, I never ever used video calls (no skype on my hardware!), so *I* would be very happy about a FOSS dialer not capable of videocalls
<dos1>
there's support for video calls via jabber
<dos1>
works pretty well :)
<DocScrutinizer05>
I _think_ there are some proprietary vide call extensions for UMTS calls too. Prolly invented by Apple
<dos1>
hmm... they have their "facetime" protocol iirc
<DocScrutinizer05>
yep, that's what I meant
<dos1>
however, umts video calls were a thing long before iphone I think?
<dos1>
even some old nokia phones supported that
kolp_ has quit [Read error: Connection reset by peer]
<DocScrutinizer05>
dunno. no "videocall" button ever shown up on my N900 on any regular call. There's one when I do SIP calls to another video capable SIP client
<dos1>
n900 doesn't support that for sure
<dos1>
actually I doubt any modern phone still does
<DocScrutinizer05>
anyway, REing dialer can't be rocket science
<DocScrutinizer05>
simply ignore the video stuff to start with
<DocScrutinizer05>
plus, video itself most likely is simple since I bet it's implemented using mafw and/or gstreamer
<Oksana>
:-)
<Oksana>
It's not urgent, yet. How is it going with FPTF, I wonder?..
<DocScrutinizer05>
well, donno what freemangordon and Pali did, recently
<DocScrutinizer05>
I'm tempted to send eaither of both a beagleboard-xm and ask them to finally install maemo on it
<DocScrutinizer05>
not that this was something particularly new
<bencoh>
23:11 <+DocScrutinizer05> anyway, REing dialer can't be rocket science
<bencoh>
why dont we just "rewrite" it ?
<bencoh>
it's just dbus calls isnt it ?
<DocScrutinizer05>
could be done, yes
<DocScrutinizer05>
but I guess REing would at least provide a "requirements spec"/"IT spec"
<bencoh>
I guess even dtmf are sent this way to telepathy/cmt-speech ?
<DocScrutinizer05>
err there's a dtmf daemon
<bencoh>
hmm, where does it sit ?
<DocScrutinizer05>
dunno if dialer or telepathy uses it
<bencoh>
tonegend ?
<DocScrutinizer05>
(maybe I'm wrong, lemme dig up details)
<DocScrutinizer05>
yes
<DocScrutinizer05>
:-)
che1 has quit [Remote host closed the connection]
<DocScrutinizer05>
I admit I have no hard facts about it
<DocScrutinizer05>
so it's mere guessing
<DocScrutinizer05>
maybe mildly educated guessing
<bencoh>
to me it looks like something used to "play" dtmf to user when he presses a digit, but ... dunno
<DocScrutinizer05>
sure
<bencoh>
I guess we can send gsm inband dtmf, and something has to generate those at some point
<DocScrutinizer05>
but either DTMF is generated inband in a media-specific way (e.g. AT command for modem) or the (e.g. SIP) stack will most likely use same DTMF generator to send the same tones to far end too
<DocScrutinizer05>
GSM DTMF is miost commonly a job of modem
<bencoh>
(as you probably know) there are many ways to send dtmf with SIP :)
<DocScrutinizer05>
at least P*S8 can do DTMF, I'm sure about that
<bencoh>
(inband or rfc-I-forgot with out-of-band signaling)
<DocScrutinizer05>
yes, SIP DTMS is funny
<DocScrutinizer05>
rfc2833?
<bencoh>
"""funny""" :-)
<bencoh>
yeah, 2833 rings a bell
<DocScrutinizer05>
inband
<DocScrutinizer05>
and INFO iirc
<bencoh>
ooh, INFO too ... havent played with those since years ago
<DocScrutinizer05>
~rfc2833
<P-G>
Mhm. Just those three.
<bencoh>
err, for years*
<DocScrutinizer05>
~rfc 2833
<P-G>
Inband seems nice but RFC seems more popular with SIP clients these days. Not sure why, I haven't read much of it.
<DocScrutinizer05>
wth
<DocScrutinizer05>
~ping
<infobot>
~pong
<DocScrutinizer05>
(why) simple: inband is not reliable, depending on codec
<bencoh>
and 2833/INFO are not reliable, depending on your providers and its providers/peers :-)
<DocScrutinizer05>
it's basically a far end issue
<bencoh>
and whether it's properly converted/routed to POST network
<DocScrutinizer05>
depends on what peer/farend supports
<bencoh>
yeah
<DocScrutinizer05>
sipgate gateway for example works great with 2833
<P-G>
Auto-negotiation is possible.
<bencoh>
end-to-end ?
<bencoh>
sounds "risky" :)
<P-G>
Yes. I don't know how but I've seen it in a few places.
<P-G>
Fine with me as long as it's all encrypted properly.
<P-G>
Asterisk can auto-detect on both ends (incoming and outgoing are seperate calls). RFC is preferred by default.
<P-G>
That's as of version 11 but I assume still true.
<DocScrutinizer05>
P-G: yes, twinklephone for example has "DTMF: auto"
<P-G>
I guess it just tried them all one by one.
<DocScrutinizer05>
AUTO afaik simply means "send all three channels"
<P-G>
Oh...
<DocScrutinizer05>
they are independant
<P-G>
Well, asterisk manual used the term "prefers" for RFC, whatever that means.
<P-G>
I've got to go AFK though.
<DocScrutinizer05>
some channels offer ACK/NAK maybe
<DocScrutinizer05>
inband for sure doesn't ;-)
<DocScrutinizer05>
INFO most likely does
<Oksana>
Anybody willing to look over the LED pattern, to see if it makes sense? PatternPowerOff=10;3;0;rGb;9d80 4000 04ff e004 05ff e100 0000 ; 9d80 40ff 05ff e080 04ff e002 0000
<DocScrutinizer05>
I admit I have no idea what's rfc2833 doing
<DocScrutinizer05>
Oksana: use LED pattern editor!
<DocScrutinizer05>
Oksana: basically any pattern that doesn't end in dim LED (so either keeps a steady LED active as last state, or is cyclic) will do
<Oksana>
cyclic is better. Show that it is not a trick of light...
* DocScrutinizer05
goes editing his power-down pattern, finally
<DocScrutinizer51>
lets see
* Oksana
has seen dim violet led at power down enough to become confused about where it comes from - there is no led pattern, afaik, involving violet...
<DocScrutinizer05>
no, not a standard one
<DocScrutinizer05>
maybe that's from vboost (USB hostmode)?
<DocScrutinizer05>
I introduced such a pattern for active vboost
<DocScrutinizer05>
(just because there was no other violet one)
<Oksana>
Well, I do not recall ever installing USB hostmode...
<DocScrutinizer05>
anyway my editing I just done was _too_ simple (almost). I somply reduced number of ramp-down steps a tad so the LED stays at ~50%
<Oksana>
And I have only ever seen it at shut-down. It's rare, it's dim, it's violet, and I have even seen it one year ago.
<DocScrutinizer05>
was basically like 4 clicks
<Oksana>
Did you preview it?
<DocScrutinizer05>
(violet) sounds like a hw defect
<DocScrutinizer05>
sure I did preview
<Oksana>
:-)
<DocScrutinizer05>
btw the power-down pattern is silly. It has lots of cruft in it. E.G. the waits at end are completely useless
* DocScrutinizer05
doesn't feel like shutting down IroN900 just to test the LEDpattern
<DocScrutinizer05>
ohmy already midnight. Feels strange when you're up since 4h
<Oksana>
:-) Maybe, the waits at the end were in order to get the shut-down finished before LED pattern finishes? But such waiting with already-off LED does sound strange... No final blink to tell the user after the waiting...
<Oksana>
Good night :-)
<DocScrutinizer05>
Oksana: to me? Nah, morning!
<Oksana>
What's the name of LED Pattern editor? I am trying to add shortcut to desktop, and it's alphabetically sorted...
<DocScrutinizer05>
it's a settings applet
<DocScrutinizer05>
I got settings as shortcut. Mad useful
<DocScrutinizer05>
you usually canot call settings applets directly afaik
<Oksana>
Ok, added Settings shortcut. Cannot see it, though. When in portrait mode I add a new shortcut, what's the default location for it - top left corner, top right corner, something?..
<Oksana>
Hooray! Top right corner, I guess.
<sixwheeledbeast>
they very often stack on top of each other
<Oksana>
My problem was that top (in portrait) half (at least) of the screen is invisible (due to display damage), currently. So it's just "let's drag blindly, and hope there is something being dragged"
<sixwheeledbeast>
ah, i see.
<FIQ>
* DocScrutinizer05 doesn't feel like shutting down IroN900 just to test the LEDpattern
<FIQ>
the "start brighy cyan-ish, wait for 5 seconds, then dim slowly" thing?
<Oksana>
I would say white-ish, but yes, the dimming-at-shut-down one, the powerOff one.
<Oksana>
I managed to assign violet to engine 1 and green to engine 2, by now (test-previewed it), but I do not see how to change the actions themselves, yes (see above)... Ah well, will figure it out, hopefully.
<DocScrutinizer05>
hmm? simply tap on an "action"
<Oksana>
(top (in portrait) half (at least) of the screen is invisible (due to display damage), currently) So it's just "tap anywhere, and see where it goes" (scrolling into visibility helps when it is possible).