atk has quit [Quit: Well this is unexpected.]
atk has joined #neo900
houkime has quit [Ping timeout: 256 seconds]
Kabouik_ has quit [Ping timeout: 248 seconds]
infobot has quit [Read error: Connection reset by peer]
infobot has joined #neo900
wicket64 has quit [Read error: Connection reset by peer]
wicket64 has joined #neo900
himcesjf_ is now known as him-cesjf
knttl has quit [Ping timeout: 256 seconds]
knttl has joined #neo900
ArturShaik has joined #neo900
cybiko123 has joined #neo900
jonsger has joined #neo900
wpwrak has quit [Read error: Connection reset by peer]
wpwrak has joined #neo900
jonsger has quit [Ping timeout: 265 seconds]
houkime has joined #neo900
Kabouik_ has joined #neo900
Pali has joined #neo900
cybiko123 has quit [Quit: Leaving.]
trx has quit [Ping timeout: 264 seconds]
trx has joined #neo900
trx has joined #neo900
trx has quit [Changing host]
Kabouik_ has quit [Quit: Leaving]
Kabouik has joined #neo900
qwazix has quit [Ping timeout: 240 seconds]
qwazix has joined #neo900
Airwave has quit [Ping timeout: 265 seconds]
Airwave has joined #neo900
Pali has quit [Ping timeout: 256 seconds]
cybiko123 has joined #neo900
cybiko123 has quit [Changing host]
cybiko123 has joined #neo900
Pali has joined #neo900
threebar` has quit [Remote host closed the connection]
ctag1 has joined #neo900
ctag_ has quit [Ping timeout: 276 seconds]
trx has quit [Ping timeout: 256 seconds]
jonwil_ has joined #neo900
trx has joined #neo900
trx has joined #neo900
trx has quit [Changing host]
ilon_ has joined #neo900
trench_ has joined #neo900
Beaches_ has joined #neo900
houkime has quit [Remote host closed the connection]
jonwil has quit [*.net *.split]
ilon has quit [*.net *.split]
Beaches has quit [*.net *.split]
trench has quit [*.net *.split]
houkime has joined #neo900
jkepler has joined #neo900
houkime has quit [Ping timeout: 256 seconds]
jonwil_ has quit [Quit: ChatZilla 0.9.93 [SeaMonkey 2.49.3/20180412182658]]
comradekingu has quit [Remote host closed the connection]
wpwrak has quit [Ping timeout: 264 seconds]
trx has quit [Ping timeout: 256 seconds]
trx has joined #neo900
trx has quit [Ping timeout: 255 seconds]
ArturShaik has quit [Ping timeout: 248 seconds]
delphi has joined #neo900
delphi has quit [Client Quit]
delphi has joined #neo900
delphi has quit [Client Quit]
Kabouik has quit [Ping timeout: 248 seconds]
Kabouik_ has joined #neo900
Pali has quit [Ping timeout: 256 seconds]
Kabouik- has joined #neo900
Pali has joined #neo900
Kabouik_ has quit [Ping timeout: 260 seconds]
ArturShaik has joined #neo900
Pali has quit [Remote host closed the connection]
louisdk has joined #neo900
Pali has joined #neo900
Pali has quit [Remote host closed the connection]
wiewo has quit [Ping timeout: 276 seconds]
wiewo has joined #neo900
Pali has joined #neo900
trx has joined #neo900
ravelo has joined #neo900
jonsger has joined #neo900
jkepler has quit [Read error: Connection reset by peer]
jkepler has joined #neo900
himcesjf_ has joined #neo900
ArturShaik has quit [Ping timeout: 240 seconds]
him-cesjf has quit [Ping timeout: 260 seconds]
wpwrak has joined #neo900
<enyc> Joerg-Neo900: ok im curious now what "21:55 <+Joerg-Neo900> houkime: great" about... my machines were all down on reboot and updates ad losnt history!
<Joerg-Neo900> sorry, pastebin freaks out, so here the 3 lines
<Joerg-Neo900> [2018-05-04 Fri 20:29:15] <houkime> ooopsie, seems like Arch updates have broken eeshow. Trying to recompile
<Joerg-Neo900> [2018-05-04 Fri 20:36:33] <houkime> recompilation helps. all ok.
<Joerg-Neo900> [2018-05-04 Fri 22:55:45] <Joerg-Neo900> houkime: great
ravelo has quit [Quit: Connection closed for inactivity]
louisdk has quit [Ping timeout: 264 seconds]
Pali has quit [Remote host closed the connection]
<sicelo> enyc: also, this channel has public logs :)
<enyc> updates break package... reminds me of gentoo ;p
Pali has joined #neo900
houkime has joined #neo900
<DocScrutinizer05> isn't arch similar to gentoo somewhat?
qwazix_nc has joined #neo900
<Joerg-Neo900> never looked into it
qwazix has quit [*.net *.split]
qwazix has joined #neo900
qwazix_nc is now known as qwazix
infobot has quit [Remote host closed the connection]
infobot has joined #neo900
<enyc> DocScrutinizer05: seemingly arch can compeile much sutff from source, but doesn't have to, or something...
<enyc> DocScrutinizer05: derivatives of arch popular too, seemingly
<enyc> DocScrutinizer05: have you sorted out all your linux distro / opensuse / workspace realtad fun?
<enyc> i recall there was a time you were having trouble with build-environemnt and difficilty not wanting to change systems and break stuff
threebar has joined #neo900
threebar has joined #neo900
threebar has quit [Changing host]
threebar has quit [Remote host closed the connection]
<houkime> Arch doesn't _have_to_ compile everything from source. Arch binary repositories are usually latest-official-release.
<houkime> however Arch HAS a great community support for compiling from sources
<houkime> Community compiling support is done via AUR.
louisdk has joined #neo900
<houkime> AUR contains PKGBUILDs - scripts for a built-in packaging system
<houkime> PKGBUILDs can (and in many cases do) fetch latest sources from git, compile and package them.
<houkime> PKGBUILDs are maintained by humans and if maintained correctly can compile stuff without your own interference.
<enyc> houkime: hrrm....... =)
<enyc> houkime: makes sense, so gives you the possibility to do gentoo-like build-new-stuff and custom-build flags
<enyc> Oooohoh how I remember gentoo flags
<houkime> yep, exactly
<houkime> you can change makeflags on system level and also for each PKGBUILD
<enyc> houkime: what fun is happenig with the proto_v2 layout, anyway?? ;-)
<houkime> well, I moved some esds to LOWER (sim ones and one more)
<houkime> I wanted this for stuff that is too short in terms of traces to be protected locally
<houkime> I understood that I cannot really account for a case where BOB is not connected to LOWER but to userboard
<houkime> And now I have some troubles with usb chips
<bencoh> usb chips?
<houkime> the guys that process usb signal from the port
<bencoh> the transceiver you mean?
jonsger has quit [Ping timeout: 240 seconds]
<houkime> ooops, sorry. Wrong one. No, this one is a charger.
<houkime> It now needs to get quite displaced because of connectors.
<houkime> there was one configuration where it could be quite ok to be almost on it's metacollin's place
<houkime> buuuut because of sd holder keepout zones which got interleaving with through hole stuff this wasn't really feasible
louisdk has quit [Quit: Ex-Chat]
<houkime> *colliding. not interleaving
<houkime> and also this config was quite risky on its own(
<houkime> *esd-wise
<houkime> actually quite sad. I spent some time (maybe too much of it) to find some way to justify it.
<houkime> and now the thing is that D+- pair that goes from the port to a charger
<houkime> actually creates a stub because ther trace to a charger is much shorter than the one that actually goes to UPPER and beyond.
<houkime> I actually heard that usb D+- is not THAT sensitive (like some others) but still a little bit of concern.
<DocScrutinizer51> very short T deadebds might not hurt too much, The idea abywat was to run one straight pair from receptacle over HB conatct-vias over charger chip over LOWER2UPPER to SoC
<DocScrutinizer51> anyway*
<DocScrutinizer51> with according ESD prot etc on it
<DocScrutinizer51> this would create a via-port stub when using HB USB but would be stub-free for the common port-connected USB
xmn has joined #neo900
<houkime> by HB contact-vias you mean pogos?
<DocScrutinizer51> yes, the Vias where those contact to
<DocScrutinizer51> actually pads with a center drill to hold the pogos' tips in place
<DocScrutinizer51> just use a via for that
<houkime> ok, understood. I though about that, but these things would be quite skewed if put directly on a pair.
<DocScrutinizer51> could also serve for user soldering post connectors or wires there
<houkime> too much distance between them
<houkime> signal gets delayed in-between pogos.
<DocScrutinizer51> yes you have a length skew between D+ and D- on HB, we should elaborate on how to compensate that on the user attache PCB
<DocScrutinizer51> ideally route tuned pair to center between the two pogo pads and then split right/left
<DocScrutinizer51> then do same but inverse for the way from HB pads towards SoC
<houkime> not really feasible to do it split way. Electrical properties difference between scenario "two near" and ("7 mm apart") is biggie. This will create something like a phase transition border and signal will be deflected.
<houkime> actually the same stands for the difference between "pair in a board" and "7 mm apart in the air over pogos"
<DocScrutinizer51> we may test RealLive with a slaughtered USB cable
<houkime> that was my thought too.
Pali has quit [Remote host closed the connection]
houkime has quit [Ping timeout: 240 seconds]
pagurus has joined #neo900
cybiko123 has quit [Quit: Leaving.]
xes has quit [Quit: bye..]
xes has joined #neo900
xes has quit [Quit: bye..]
xes has joined #neo900
jabawok_ has quit [Ping timeout: 240 seconds]
jabawok_ has joined #neo900