DocScrutinizer05 changed the topic of #qi-hardware to: 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 and http://irclog.whitequark.org/qi-hardware
dos1 has quit [Ping timeout: 264 seconds]
viric has quit [Ping timeout: 240 seconds]
viric has joined #qi-hardware
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
dos11 has joined #qi-hardware
<apelete> */
<apelete> usb_setb(dev, JZ_REG_UDC_POWER, USB_POWER_SOFTCONN);
dos1 has quit [Ping timeout: 246 seconds]
<apelete> looking in programming manual (21.4.3.2
<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?
<mth> unsignedsoft_con:1 __deprecated; /* soft connect required */
<mth> this exists in include/linux/usb/musb.h
<mth> you can use "git blame" to look up the commit in which it was deprecated
<mth> usually the commit comment then says what it was replaced by
<DocScrutinizer05> we started funraiser: neo900.org
<apelete> mth: found the commit:
<apelete> commit c58bfa6b97731590e42cba6bd13829c4e480992f
<apelete> $ git show c58bfa
<DocScrutinizer05> fund, but he!
<apelete> Author: Felipe Balbi <felipe.balbi@nokia.com>
<apelete> Date: Thu Jan 21 15:33:55 2010 +0200
<apelete>
<apelete> USB: musb: deprecate what we don't use
<apelete>
<apelete> after 2.6.34, those fields will be removed from
<apelete> struct musb_hdrc_platform_data, it's expected
<apelete> that other architectures are fixed by then.
<apelete>
<apelete> Signed-off-by: Felipe Balbi <felipe.balbi@nokia.com>
<apelete> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
<DocScrutinizer05> felipe balbi, UGH
<DocScrutinizer05> KH is ok, but this balbi guy seems a good indicator for stuff that's giving you headache
<whitequark> DocScrutinizer05: ooooh a keyboard
<apelete> well, that commit message does not help finding out what should be used instead of those deprecated fields
<whitequark> I haven't seen a phone with a keyboard for years
<whitequark> oh and LTE. hm.
* whitequark looks at his wallet
<whitequark> DocScrutinizer05: is there a full list of specs?
<mth> DocScrutinizer05: I can't judge his code quality, but he did respond quickly and friendly when I mailed him once
<DocScrutinizer05> whitequark: click on "specs" - though "subject to change"
<whitequark> resistive display, huh
<mth> apelete: that sounds like the generic code ignores it, so then the glue would have to take care of it
<apelete> mth: unsigned softconnect:1;
<apelete> that's in struct musb in musb_core.h
<apelete> so it seems it has been moved there
<mth> ah, it still exists but it is no longer platform data?
<apelete> well, found it in musb_core.h, I don't know how it is supposed to be used
<apelete> mth: do you think the glue should write that field to use soft connect capability ?
<mth> only if the generic code doesn't
<apelete> generic code does not seem to handle it, but I may be wrong here
<mth> look for writes to that particular register offset
<mth> the generic code might use different names for it, but the address will be unique
viric has quit [Ping timeout: 240 seconds]
<DocScrutinizer05> whitequark: http://neo900.org/faq#touch
<whitequark> that's... wishful thinking
<whitequark> for one, it's not multitouch. completely different pattern of interaction
<whitequark> though it's not going to matter, considering all FOSS shells are stuck in 90's anyway
<DocScrutinizer05> well, we don't have multitouch in any of it's ancestors either
<whitequark> sure. I mainly wanted to know whether it's still in the "it's way inferior but yeah FOSS" category
<whitequark> got better, but still there.
* whitequark shrugs
<whitequark> personally, I'm somewhat torn between "a foss phone" and "fuck phones completely"
<wpwrak> both at least have the "f" in common :)
dos1 has joined #qi-hardware
<wpwrak> a third option would be "feature phone"
<whitequark> wpwrak: well, I use my current android phone, in order of importance: GPS nav, SIP, web, SMS
<whitequark> so, uh, feature phone ~ no phone at all
<whitequark> it's great in emergencies, but not as something I'd use daily.
<wpwrak> ah, my car nav can't make phone calls :)
viric has joined #qi-hardware
<wpwrak> and my feature phone does SMS and voice. that's all.
<whitequark> SIP & web are good enough on the notebook
<whitequark> GPS's kinda inconvenient
<apelete> mth: you're right, it is handled in generic code indeed:
<apelete> $ find drivers/usb/musb/ -type f -exec grep -Hin "MUSB_POWER_SOFTCONN" {} \;
<apelete> drivers/usb/musb/blackfin.c:270:val |= MUSB_POWER_SOFTCONN;
<apelete> drivers/usb/musb/blackfin.c:265:val &= ~MUSB_POWER_SOFTCONN;
<apelete> drivers/usb/musb/musb_gadget.c:1616:power |= MUSB_POWER_SOFTCONN;
<apelete> drivers/usb/musb/musb_gadget.c:1618:power &= ~MUSB_POWER_SOFTCONN;
wolfspraul has quit [Quit: leaving]
<apelete> drivers/usb/musb/musb_regs.h:46:#define MUSB_POWER_SOFTCONN0x40
<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
<DocScrutinizer05> we're busy porting fremantle
<DocScrutinizer05> see
<DocScrutinizer05> link on post#1
lekernel has quit [Quit: Leaving]
<apelete> DocScrutinizer05: that's what I was going to ask: "who's working on it and how far has it gone ?" :)
<apelete> it's great to see an attempt at building a phone with a keyboard, really
<DocScrutinizer05> see FPTF thread, though the devels are not really updating that one frequently
<DocScrutinizer05> well, hw kbd been one of the must-have's
<DocScrutinizer05> otherwise I wouldn't have left my bed for this
<apelete> I'm still using a Nokia N9, but wish a phone with a keyboard will be available by the time the N9 isn't working anymore
<apelete> DocScrutinizer05: going to keep an eye on this, let's see if I can give a hand when that little musb project of mine is ready :)
* apelete looks at his wallet too...
<DocScrutinizer05> :-)
<DocScrutinizer05> much appreciated
<whitequark> frankly it's tempting
<whitequark> but I just don't want to have yet another phone that doesn't work, for the cost of iphone this time