MonkeyofDoom has quit [Read error: Connection reset by peer]
Humpelstilzchen has quit [Ping timeout: 244 seconds]
Defiant has joined #neo900
jonsger has quit [Remote host closed the connection]
jonsger has joined #neo900
dal has joined #neo900
herpderphurr has joined #neo900
vakkov has quit [Ping timeout: 244 seconds]
vakkov has joined #neo900
herpderphurr has quit [Ping timeout: 244 seconds]
herpderphurr has joined #neo900
herpderphurr has quit [Ping timeout: 244 seconds]
pagurus has quit [Ping timeout: 276 seconds]
pagurus` has joined #neo900
pagurus` has quit [Remote host closed the connection]
pagurus has joined #neo900
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #neo900
Xiaoman has quit [Ping timeout: 276 seconds]
Xiaoman has joined #neo900
dal has quit [Ping timeout: 260 seconds]
dal has joined #neo900
jonsger has quit [Ping timeout: 264 seconds]
ecloud_wfh is now known as ecloud
arcean has joined #neo900
arcean_ has joined #neo900
arcean has quit [Read error: Connection reset by peer]
vakkov has quit [Ping timeout: 244 seconds]
vakkov has joined #neo900
Kabouik has joined #neo900
vakkov has quit [Ping timeout: 264 seconds]
vakkov has joined #neo900
john324r has joined #neo900
Pali has joined #neo900
john324r has quit [Quit: Page closed]
paulk-collins has joined #neo900
<wpwrak>
freemangordon, Pali: hmm, does anything in fremantle actually use ECI ? i can see ECI[5] (eci_sw_gpio) getting initialized in the kernel, but that's all i can find.
<Pali>
ECI? do you mean Nokia ECI headsets?
<Pali>
IIRC they are not supported by N900 HW
<wpwrak>
yes, that famout "Enhancement whatever Interface". well, there's a fancy bit of circuit for it in n900.
<Pali>
but I read somewhere it N900 HW could support it somehow
<Pali>
but answer from Nokia kernel developer was "unsupported by HW"
<wpwrak>
kewl :)
<wpwrak>
DocScrutinizer05: are you sure we want to keep that mess ? the protocol specification is some secret nokia took to its grave, it seems. the msc thesis about eci says nothing about the protocol. the kernel driver nokia once submitted assumes the use of an unknown controller chip. i couldn't find any other sources / leaks / reverse-engineering either. so for all practical purposes, this seems unusable.
<Pali>
eci headsets are supported on Nokia N9 and Nokia N950
<wpwrak>
thanks ! let's clone the whole bugger then ...
<Pali>
there is also v2.6.28-nokia branch in which is official nokia n900 kernel source code
<Pali>
(versioned with all publically available versions)
<wpwrak>
i suspect what i'll find is that driver that talks to the mystery chip. but let's see ...
<Pali>
IIRC that code from 2.6.32 just export some memory via sysfs
<Pali>
and userspace ohmd plugin parse it
<Pali>
ohmd with all plugins were opensourced in harmattan
<Pali>
on gitorious
<Pali>
so now when gitorious is working in R/O mode again, you can look into source code
<wpwrak>
when / if ever :)
<wpwrak>
pity that they didn't just a do a "forced" migration to gitlab. granted, some people would have complained, but there's also a lot who just can't be bothered to migrate anywhere
<wpwrak>
anyway, that's a great lead. thanks a lot !
heinrich5991 has quit [Ping timeout: 260 seconds]
heinrich5991 has joined #neo900
Venemo has joined #neo900
<DocScrutinizer05>
wpwrak: ECI is also generic AV jack detection, so please don't try tro optimize that out
<DocScrutinizer05>
((answer from Nokia kernel developer was "unsupported by HW")) they seen there is a driver that uses an external MCU and they answered "we don't have any such MCU so we don't support ECI"
<DocScrutinizer05>
the SoC has a way to enable and disable the micbias (I suggest video analog switch) and it has an ADC to read in the inbound signal. That's honestly all that's needed for ECI
<wpwrak>
(optimize out) what i'm trying to figure out are the timing requirements. so far, all i have is that the msc thesis 1) says that ECI is basically I2C, and that 2) it operates I2C at 400 kbps. thus, there is nothing to indicate that ECI does not operate at a fairly high speed.
<wpwrak>
and twl5031 (undocumented, right ?) appears to have a dedicated hardware block (ACI) for it.
<wpwrak>
so that would also suggest non-trivial speed
<DocScrutinizer05>
there were scope pics (iirc from jacekowski) that didn't look like highspeed
<DocScrutinizer05>
iirc they looked more like HDQ
<wpwrak>
would you have some bit rate ? :)
<DocScrutinizer05>
I first would need the scope snapshots
<DocScrutinizer05>
anyway for the IO extenmder stuff it's fair to assume all three GPIO being low-latency IRQ
<DocScrutinizer05>
maybe it's more economic when I evaluate the IRQ timing?
<wpwrak>
hmm, isn't ECI[5] an output ? (goes to 2SEL of the switch)
<DocScrutinizer05>
so?
* DocScrutinizer05
afk for coffee
<wpwrak>
that seems to contradict "all three GPIO being low-latency IRQ"
<wpwrak>
(irq timing) well, i was preparing a detailed analysis since you rejected my first quick assignment. but sure, if you want to do it, please go ahead
<wpwrak>
all i really want is to place the io expander chip in the block diagram ;-)
<DocScrutinizer05>
no, it doesn't, see [5]
<DocScrutinizer05>
we have two comparator outputs plus one direct ADC line
<DocScrutinizer05>
all THREE are low-latency, the rest (4, 5) are most likely outputs
<DocScrutinizer05>
you're looking at the schematics (I hope), while I talk from top of my head
<wpwrak>
where is [4] ?
<wpwrak>
(sch) yes, of course
<DocScrutinizer05>
and where is [0]?
<DocScrutinizer05>
thje Nokia schematics are a mess sometimes