<nicksydney>
eintopf: i've seen lots of phone repair people or shops can do those kind of thing easily...it takes practise :)
<eintopf>
I think, I am more a software guy
<nicksydney>
eintopf: most of us are ... same like us too we have done the time and practise while the repair people have done their time in soldering :)
xiangfu has joined #qi-hardware
xiangfu has quit [Ping timeout: 255 seconds]
xiangfu has joined #qi-hardware
porchao has quit [Quit: Leaving...]
sb0 has joined #qi-hardware
porchao has joined #qi-hardware
rz2k has joined #qi-hardware
xiangfu has quit [Ping timeout: 240 seconds]
<whitequark>
kyak: it's not doomed to be interpreted!
<whitequark>
I believe there's a K compiler
<whitequark>
e.g. "kcc" for C
<kyak>
oh, no.. the kcc just produces an a.out that is then interpreted
<kyak>
(my understanding)
<whitequark>
ah
<whitequark>
well... yes, that makes sense given their article
<kyak>
they call a.out "an executable script" :)
porchaso0 has joined #qi-hardware
porchao has quit [Ping timeout: 245 seconds]
xiangfu has joined #qi-hardware
jekhor has quit [Ping timeout: 252 seconds]
xiangfu has quit [Ping timeout: 276 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
<paul_boddie>
Just when the Arduino line-up couldn't get more confusing.
atommann has quit [Quit: Leaving]
<paul_boddie>
I think it's weird that on their hybrid boards they seem to emphasise the microcontroller specifications above the higher-end CPU specifications so that the 2.5K of SRAM available to the ATmega on the Tre appears before the 512MB available to the TI ARM Cortex-A8.
jekhor has joined #qi-hardware
viric_ has joined #qi-hardware
viric has quit [Ping timeout: 255 seconds]
viric_ has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
viric has quit [Read error: Connection reset by peer]
viric has joined #qi-hardware
valhalla has quit [Ping timeout: 258 seconds]
valhalla has joined #qi-hardware
rz2k has quit []
michael_lee has joined #qi-hardware
michael_lee has quit [Remote host closed the connection]
jow_laptop has quit [Ping timeout: 264 seconds]
michael_lee has joined #qi-hardware
viric has quit [Read error: Connection reset by peer]
<paul_boddie>
So the obstacle isn't the engineering, sourcing or manufacturing, and not even a lack of resources, but the financial management part.
<paul_boddie>
I can't help thinking there are people who manage this kind of thing for Free Software projects that could at least advise for open hardware projects like this.
<dos1>
it was a falstart with fundraiser...
<dos1>
GDC being liable to customers + Joerg being a project leader just didn't worked together
<paul_boddie>
Well, provided people don't get disillusioned and start thinking it'll never get done, you know now that there is demand.
<dos1>
we just need to convinve people to donate once again, this time directly to Neo900 UG
<dos1>
may be hard, but we'll see
<whitequark>
I wonder if you'll accidentally trip some cognitive bias
<whitequark>
like some projects do trip the sunk cost one, for example. not sure though
<dos1>
Nikolaus already said that he's willing to cooperate as a contractor (so the other way around than before), he won't manage the production then
<paul_boddie>
It could easily work out better this way.
<dos1>
sure
<dos1>
it was a bit unfortunate that Nikolaus decided to put his announcement in a way that suprised us a bit
<dos1>
we knew some hour before public announcement that he's going to do that, but we didn't know that it's going to arrive at our inboxes just yet
<whitequark>
paul_boddie: well, kickstarter does have an issue with bullshit promises
<dos1>
his wording was also a bit unfortunate, so both Joerg and me paniced a bit after reading that (as probably most of the supporters did)
<dos1>
but now when emotions settled down a bit, it indeed seems like an opportunity (sans the risk of losing people who already paid before)
<paul_boddie>
dos1: Yes, it does sound a bit like he won't be doing anything more with the project.
<dos1>
(sorry if my grammar is gibberish, it was really an exhausting day...)
<paul_boddie>
whitequark: I think the biggest problem is fulfilment with GCW-Zero, which is why some of these sites actually deal with that on behalf of the projects. Don't remember which, though.
<nicksydney>
Guide.pdf&ei=aU11U6TROZGE8gWipIKYAQ&usg=AFQjCNEznuPZigdEcdsupesPP7lnMVPD-A&sig2=Cr8kXzSKMtW74BJEONxuqg&bvm=bv.66917471,d.dGc&cad=rja) it is a chip for debugging .. i thought that having a JTAG connection already allows you to do debugging ? or am i missing something ?
<nicksydney>
the question is why do they need to introduce another EDBG chip for debugging ?
<whitequark>
well not everyone wants to buy an atmel in-circuit debugger
<whitequark>
they just took that separate device and integrated it
<whitequark>
ST does the same with their devboards
<nicksydney>
whitequark: so you mean the JTAG connector is using with atmel in-circuit debugger ?
<whitequark>
yea
<nicksydney>
ahhh i looked the labelled at the wrong place..it's not the USB that is labelled JTAG it's the ping connector that is labelled the JTAG ..ok got it now
<nicksydney>
so those 2 USB is used for debugging and power i assume ?
<nicksydney>
so the USB labelled as DEBUG is used for programming and debugging and the other is used for power I assume ?
<whitequark>
power and communication
<nicksydney>
cool...understand now thanks whitequark