viric has quit [Remote host closed the connection]
viric has joined #qi-hardware
pcercuei has quit [Ping timeout: 260 seconds]
viric has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
eintopf has quit [Ping timeout: 245 seconds]
eintopf has joined #qi-hardware
jekhor has joined #qi-hardware
valhalla has quit [Ping timeout: 260 seconds]
valhalla has joined #qi-hardware
wolfspraul has joined #qi-hardware
xiangfu has joined #qi-hardware
lekernel has joined #qi-hardware
leosaeba has joined #qi-hardware
pcercuei has joined #qi-hardware
xiangfu has quit [Remote host closed the connection]
dos1 has joined #qi-hardware
mth_ is now known as mth
dos1 has quit [Ping timeout: 264 seconds]
dos1 has joined #qi-hardware
dos1 has quit [Remote host closed the connection]
dos1 has joined #qi-hardware
dos1 has quit [Ping timeout: 248 seconds]
dandon has quit [Quit: .]
<whitequark>
lol, my android phone just BSOD'd
<whitequark>
the modem crashed
<whitequark>
so it displays a blue screen with white text with instructions of how to get a memory dump
<kristianpaul>
hehe
<cde>
whitequark: which brand/model?
rjvizit has joined #qi-hardware
<whitequark>
cde: lg e973
<whitequark>
it was fine on an unofficial cyanogenmod port
<kyak>
android phone BSODed? how is that possible?
<whitequark>
then I for some reason decided I should upgrade it to the official port done by the same person
<whitequark>
nothing works since
<whitequark>
wtf
<whitequark>
kyak: well, it's not windows' bsod, but it is blue and signifies death
<kyak>
ah, not *that* BSOD! :)
<whitequark>
well duh
rjvizit has quit [Remote host closed the connection]
<whitequark>
if it was winphone, then it'd be possible though.
<cde>
whitequark: can you reproduce the blue screen and take a picture of it?
<cde>
it is relevant to my interests
<whitequark>
cde: I don't think so but if it repeats I can do that
<whitequark>
which interests?
<kyak>
blaming lg :)
<cde>
whitequark: professional
<whitequark>
cde: you work for lg and collect bsods of custom firmwares? :p
<cde>
unfortunately, I'm not allowed to say
<whitequark>
I can take a memory dump if you want
<whitequark>
pretty sure the required sw is leaked somewhere
<whitequark>
yea it is
<kyak>
the question is whether it is allowed to use memory dumps of custom firmware taken by leaked tools :)
<cde>
whitequark: awesome! which tool?
<whitequark>
cde: qpst
<cde>
ah cool. I have it too, but never tried on an actual phone
<cde>
you need to switch the phone to modem mode right?
<whitequark>
download mode, basically a bootloader
<whitequark>
bsod handler can do that on its own
<cde>
awesome, I had no idea it could do that
<whitequark>
(also, whoever wrote it accidentally swapped the only two keys used in its UI. grr)
<whitequark>
well, it writes that in plain text
lekernel has quit [Quit: Leaving]
lekernel has joined #qi-hardware
pcercuei_ has joined #qi-hardware
pcercuei has quit [Ping timeout: 246 seconds]
xiangfu has joined #qi-hardware
rvthorn has joined #qi-hardware
rvthorn has quit [Read error: Connection reset by peer]
nickoe has quit [Remote host closed the connection]
rz2k has joined #qi-hardware
dos1 has joined #qi-hardware
xiangfu_ has joined #qi-hardware
xiangfu has quit [Ping timeout: 240 seconds]
nickoe_ has joined #qi-hardware
nickoe_ is now known as nickoe
nickoe is now known as nickoedd
nickoedd is now known as nickoe
rzk has joined #qi-hardware
rzk has quit [Client Quit]
rz2k has quit [Ping timeout: 240 seconds]
dos1 has quit [Ping timeout: 256 seconds]
dandon has joined #qi-hardware
dos1 has joined #qi-hardware
arhuaco has joined #qi-hardware
lekernel has quit [Ping timeout: 264 seconds]
lekernel has joined #qi-hardware
leosaeba has quit [Quit: leosaeba]
<apelete>
larsc mth: Hello there
wolfspraul has quit [Ping timeout: 272 seconds]
wolfspraul has joined #qi-hardware
<apelete>
still trying to understand why the udc does not seems to be detected as it should (bulk endpoint not being detected -> http://paste.debian.net/60583/, and musb->endpoints member being left initialised to O in struct musb -> http://paste.debian.net/62655/)
<apelete>
I read something interesting in the jz4740_udc code:
<apelete>
/* Let host detect UDC:
<apelete>
* transistor on and pull the USBDP pin HIGH.
<apelete>
* Software must write a 1 to the PWR:USB_POWER_SOFTCONN bit to turn this
<apelete>
s/looking in programming manual (21.4.3.2/looking in programming manual (21.4.3.2 POWER), bit 6 used in jz4740_udc.c is advertised as "Version specific" but undocumented/
<apelete>
but section 21.5.1 titled "Soft connect/disconnect" explains usage of what is called "PWR:USB_POWER_SOFTCONN bit" in the jz4740_udc code
<apelete>
larsc mth: is that SOFTCONN mechanism standard to musb controllers or do you think I should implement it specifically in the jz4740_musb driver too ?
jekhor has quit [Ping timeout: 240 seconds]
dos11 is now known as dos1
dos1 has quit [Ping timeout: 240 seconds]
<mth>
apelete: is there anything in the generic code that can write that particular bit?
<apelete>
looks like set_vbus() call in musb glue will need fixing
pcercuei_ has quit [Quit: dodo]
<apelete>
DocScrutinizer05: just read http://neo900.org/faq, I was thinking the device would ship with a phone OS (no matter how limited), ie. could make phone calls and/or sms out of the box
<DocScrutinizer05>
we will ship a rudimentary dialer
<DocScrutinizer05>
actually I guess by the time we're shipping SHR should be ported and ready to use
<DocScrutinizer05>
after all it's working on GTA04 already afaik
<apelete>
DocScrutinizer05: great. so the device would be more of a foss dev phone than an actual ready to use phone, like the GTA04, right ?
<DocScrutinizer05>
right
<DocScrutinizer05>
GolDeliCo doesn't ship a ral OS - that's up to commuity