wpwrak has quit [Read error: Connection reset by peer]
wpwrak has joined #neo900
jonsger has quit [Ping timeout: 260 seconds]
Pali has quit [Remote host closed the connection]
herpderphurr has joined #neo900
chainsawbike has quit [Ping timeout: 276 seconds]
Humpelstilzchen has quit [Ping timeout: 240 seconds]
Defiant has joined #neo900
chainsawbike has joined #neo900
chainsawbike has quit [Ping timeout: 260 seconds]
xray256 has quit [Ping timeout: 264 seconds]
xray256 has joined #neo900
chainsawbike has joined #neo900
lobito has quit [Quit: Leaving.]
pagurus has joined #neo900
dal has quit [Quit: Leaving]
pagurus has quit [Remote host closed the connection]
pagurus` has quit [Ping timeout: 276 seconds]
pagurus has joined #neo900
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #neo900
dal has joined #neo900
chainsawbike has quit [Ping timeout: 244 seconds]
chainsawbike has joined #neo900
chainsawbike has quit [Ping timeout: 260 seconds]
xman has quit [Quit: Leaving.]
illwieckz has quit [Ping timeout: 244 seconds]
jonsger has joined #neo900
jonsger has quit [Quit: jonsger]
jonsger has joined #neo900
freemangordon has quit [Remote host closed the connection]
freemangordon has joined #neo900
fling has quit [Read error: Connection reset by peer]
fling has joined #neo900
fling has quit [Ping timeout: 258 seconds]
fling has joined #neo900
fling has quit [Read error: Connection reset by peer]
fling has joined #neo900
SylvieLorxu has joined #neo900
Pali has joined #neo900
galiven__ has joined #neo900
galiven_ has quit [Ping timeout: 276 seconds]
xman has joined #neo900
xman has quit [Ping timeout: 252 seconds]
<ceene>
hi guys, DocScrutinizer05, wpwrak
<ceene>
we've been pretty busy this week at work
<ceene>
as DocScrutinizer05 read on #maemo we were even on the verge of being fired :)
<ceene>
crisis averted, though
<DocScrutinizer05>
you did the job in one week instead one month?
<ceene>
:D
<ceene>
not yet
<ceene>
we explained the boss it was impossible to do
<ceene>
and he was okay with that
<ceene>
we still don't understand shit
<ceene>
because we're the only ones worried about the future
<ceene>
the boss, who is a stakeholder, though, isn't worried about anything
<ceene>
i think he has reached nirvana
<ceene>
or whatever
<DocScrutinizer05>
or he got puts on the own stocks
<ceene>
ahycka still has to design a board based on an artix fpga, and i have to code its firmware
<ceene>
my work is easier, though, and i'll reach the timeline at least with "something", whatever it means
<ceene>
don't think, this is a very small company, so the only people he could be able to buy from are all people he's personally met, so i don't suspect any evilness behind... just stupidity
<ceene>
anyway, we haven't had time to look at the neo900
<ceene>
but i think we've given enough time to help finish schematics and clarify component position
<ceene>
as little as i read the irc, i think wpwrak has been working a lot on that
<DocScrutinizer05>
the schematics will get finished after we got a lazy component placement for real-estate estimation
<ceene>
i'll see if we can get that done tomorrow after work (or during...)
<DocScrutinizer05>
the schematics are split into a leading UPPER section (up to sheet#20 iirc) and a trailing LOWER section
<DocScrutinizer05>
great!
<DocScrutinizer05>
please just don't place 3 WLAN chips/modules on LOWER ;-)
<DocScrutinizer05>
Nik added three variants, of which only the WL1837 will get used
<ceene>
yeah, that'd be overkill :D
<DocScrutinizer05>
shet #9 which is 3 sheets in one
<DocScrutinizer05>
rather 4
<DocScrutinizer05>
ooh the 4th is FM, so this is needed with the WL18xx
<DocScrutinizer05>
I think we should do a Note about components with special placement requirements, and keep-out areas as well as areas with height restrictions (basically applies to all areas)
<DocScrutinizer05>
but for a first lazy placement trial it's mostly irrelevant
<ceene>
yeah, let's just see first if everything in dark blue fits on lower
<DocScrutinizer05>
would be great if we can get any such lazy placement tomorrow
<DocScrutinizer05>
:nod:
<ceene>
is there also a requirement for things going on some particular side?
<DocScrutinizer05>
err, not *really* (I think atm) but a few things have a preference of sorts
<DocScrutinizer05>
but that can get sorted later, I guess
<DocScrutinizer05>
when we need a particular component to move S2->S1, we can move others S1->S2 to compensate
<ceene>
yes, that wouldn't be too troublesome
<DocScrutinizer05>
wpwrak also will do a concurrent scripted algorithmic approach to simply add up the footprint areas of the components
<DocScrutinizer05>
then we have two sources of info and we cna compare and jugle and go on with refining stuff (incl schamtics)
<DocScrutinizer05>
schematics*
aw has joined #neo900
<DocScrutinizer05>
soory for above mistake: leading *LOWER* and trailing *UPPER* in schematics
<DocScrutinizer05>
except sensors (sheet#10) which all may go to upper
<DocScrutinizer05>
for sheet#18 (hackerbus) please see the note and refer to the HB.pdf from resources which has details on the connectors to be used
<DocScrutinizer05>
so in short again: LOWER is sheet#1 to and incl sheet#20 but exycluding the sensors of sheet#10
<ceene>
ok, great
<ceene>
that and the diagram above are clear by now :)
<DocScrutinizer05>
on sensors please discard S1002 and S1003
dal has quit [Quit: Leaving]
Pali has quit [Ping timeout: 252 seconds]
<wpwrak>
ceene: (specific side) just the usual: buttons, connectors, keyboard contacts. for the chips, we should try to keep large things from the bottom of the keyboard area, due to the pcb flexing a little when hammering on the keys.
<DocScrutinizer05>
yes, the latter is very important for the final design
<DocScrutinizer05>
we also have some predefined positions for e.g. SoC since it has a dedicated cutout in the slider steel
<DocScrutinizer05>
the SoC-PoP stack is quite a bit higher than 'usual' components
<wpwrak>
pigeons: just wait util they replace read(2) and write (2) with systemd_read(3) and systemd_write(3)
<pigeons>
i would not be surprised anymroe
<wpwrak>
it will get interesting when poettering does an rms on us and demands that linux be called systemdix because there's now more systemd than any of the old cruft
<DocScrutinizer05>
I responded to that with a sarcastic echo "killall -u">~/.bash_logout beats systemd hands down ;-P
<DocScrutinizer05>
even worse than the systemd cabal are package maintainers that eat that sh*t faster than it's served by systemd
<DocScrutinizer05>
the whole consolekit/polkit/logind systemd-session-management doesn't serve any useful purpose in my book. Unless you plan to go direction TrustedComputing where the platform is absolutely safe *from user's tampering with DRM protected stuff*
herpderphurr has quit [Ping timeout: 240 seconds]
<DocScrutinizer05>
the only other faintly valid purpose that comes to mind is for multiseat installations. And honestly... who's actually considering to use that exotic nonsense today?
<wpwrak>
package maintainers really shouldn't have to play arbiters in this sort of conflict
<wpwrak>
(multiseat) isn't it aimed a sequential multiseat ? that would be rather common setup at many places
<wpwrak>
(e.g., schools, internet cafes, ...)
<DocScrutinizer05>
there's no reasonable way to solve sequential multisession issues with multimedia etc
<DocScrutinizer05>
and systemd won't come uop with any either