Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
cladamw has joined #qi-hardware
xiangfu has joined #qi-hardware
cladamw has joined #qi-hardware
wolfspraul has joined #qi-hardware
wolfspraul has joined #qi-hardware
rejon has joined #qi-hardware
<wolfspraul>
Artyom (in absence) thanks a lot for detailing all your thoughts and decision making process!
<wolfspraul>
that's very helpful to understand...
<wolfspraul>
I didn't understand what judgment of mine you referred to though - did I say anything?
<wolfspraul>
I planned to email the Qi list pointing to your great blog post, but haven't done that yet...
<wolfspraul>
anyway, all good. thanks for the background info!
<wpwrak>
whitequark: no idea. try and find out ;-) i wouldn't expect very visible damage. and it may be at a hidden layer. but you never know ...
<Artyom>
wolfsraul: I meant this statement: "wolfsprauldismissing arm is not smart and good imho". May be I just didn't understand the meaning correctly. But anyway I decided to explain why I had switched to MM SoC and put ARM away for some time.
<wolfspraul>
ah
<wolfspraul>
:-)
<wolfspraul>
that was in NO WAY at all a reference to you
<wolfspraul>
in fact you are very balanced and objective in comparing all this, which helps me (and others I think)
<wolfspraul>
it's more a reminder to self to appreciate what ARM has done (and keeps doing), and take Milkymist to the next level, instead of trying to catch up
<wolfspraul>
and of course, your findings may take you back to ARM, and why not?
<wolfspraul>
we are passionate about making things work, I think
<wolfspraul>
I would do that too, I want to get stuff to work...
<wolfspraul>
meanwhile we improve Milkymist SoC, which will eventually be chosen because IT IS the best, not because it's a dogmatic choice
<Artyom>
wolfspraul: I think we undertand each other fine now :) As I said I could misunderstand the true meaning of your statement ;)
Artyom has joined #qi-hardware
xiangfu has joined #qi-hardware
cladamw has joined #qi-hardware
jekhor has joined #qi-hardware
orson_zhai has joined #qi-hardware
wolfspraul has joined #qi-hardware
wolfspraul has joined #qi-hardware
cladamw has joined #qi-hardware
wolfspraul has joined #qi-hardware
xiangfu has joined #qi-hardware
mstevens_ has joined #qi-hardware
jivs_ has joined #qi-hardware
DocScrutinizer has joined #qi-hardware
<whitequark>
can anyone answer a relatively simple question?
<DocScrutinizer51>
whitequark: maybe I can answer, but only qhwn you pose the question here
<DocScrutinizer51>
when*
<DocScrutinizer51>
no way I'll open a webpage to rea it now, on mobile
<DocScrutinizer51>
anyway the URL suggests you want to plug mic-in to errr line-out?
paroneayea has joined #qi-hardware
emeb has joined #qi-hardware
<DocScrutinizer51>
PLRASE KILL E!!
<DocScrutinizer51>
ME
<DocScrutinizer51>
or rather, kill billyboy gates
* DocScrutinizer51
can't stop headdesking
<DocScrutinizer51>
c:\foo\bar\boo\CPU-A\conf\brd.cfg gets displayed in sourceinsight as brd.cfg[c:\foo\bar\...\conf\]
<DocScrutinizer51>
BUT THERE'S ALSO CPU-B!!!
<DocScrutinizer51>
guess what's display for cpu-b brs.cfg file in source-inight
* DocScrutinizer51
continues headdesking, while pondering suicide or 500kg TNT
jekhor has joined #qi-hardware
kilae has joined #qi-hardware
dvdk has joined #qi-hardware
zear_ has joined #qi-hardware
jluis has joined #qi-hardware
Ayla has joined #qi-hardware
mstevens has joined #qi-hardware
GNUtoo has joined #qi-hardware
Ayla has joined #qi-hardware
<DocScrutinizer>
in explorer you got a decent full pathname in top addr textbox. Not so in "Open" and "Save as" dialogs :-(((
<DocScrutinizer>
FSK wincrap!
<DocScrutinizer>
+C
<DocScrutinizer>
is there any tool to resize non-resizable dialogs, on windoze?
<DocScrutinizer>
prolly not, and even if you could resize the "window" of that dialog, I'd bet the widgets inside won't resize accordingly - unless the unlikely luccky case the requester is coded in Qt
<whitequark>
oh, was afk
<whitequark>
DocScrutinizer: yeah, I have a GSM module with line-out and mic-in (electret)
<whitequark>
actually, two modules
<DocScrutinizer>
:nod:
<whitequark>
and I want to plug the line-out of one to mic-in of another
<whitequark>
should be pretty trivial, but I was unable to google it
<whitequark>
bonus points for not letting TDMA noise to the line
<whitequark>
both the line-out and mic-in are differential
<DocScrutinizer>
use a R-divider to attenuate, with a 2kR across the mic lines and a 50..1000kR series to line, in series with a 100nF decoupling C
<DocScrutinizer>
use a 1k load R across line-out
<DocScrutinizer>
for the TDMA noise, you might or might not run into problems. Worst case you need a NF-transformer
<DocScrutinizer>
but then, you as well can use some active circuitry, like e.g an optocoupler
<whitequark>
ah. I thought that I could just use coaxial cables (I have a lot of these) for connecting the audio i/o to a shielded board
<DocScrutinizer>
depending on particular line-out differential design, you might already have sufficient bias on one of the lines to GND, to drive the opto's LED with just a series R as external components
<whitequark>
not sure if that would help actually
<DocScrutinizer>
whitequark: regarding TDMA noise your main problem is common GND of both modules
<DocScrutinizer>
the TX draws massive current bursts and thus introduces TDMA noise floor to its own GND level and in turn also to all inputs and outputs
<whitequark>
cool, thanks. I'll buy the components tomorrow and assemble the device
<whitequark>
ah, one more thing
<whitequark>
the module has SMT antenna pads, so they recommend to lay out a PCB, then calculate a 50 Ohm trace and so on
<whitequark>
I'm going to wire-wrap the entire device, so I want to buy a 50 Ohm antenna with a cable, cut its SMA connector off and just solder it directly to pads
<whitequark>
would that work?
<DocScrutinizer>
should
<whitequark>
ok thanks again. I need to run now
<DocScrutinizer>
if it's an unbalanced 50Ohm output, I.E. one of the two pads is GND
<DocScrutinizer>
whitequark: you should calculate R2 so it attenuates your line-out level to sth like 100mV for 2k mic load R
<DocScrutinizer>
err R1
<DocScrutinizer>
for R1 you might reconsider 1k according to properties of your line-out. If that's e.g. no line-out but a dedicated speaker output, you may need a 100R rather than 1k, maybe even a 33R though I doubt the line-out amp is that picky
<DocScrutinizer>
1k is proper load for standard line-out as found on any arbitrary home audio equipment
<DocScrutinizer>
standard line-out maybe 2Vss, so R1=50k
<DocScrutinizer>
poti should be log type
<DocScrutinizer>
with the spead end (the origin) towards mic-