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
pcercuei has quit [Quit: dodo]
atommann has joined #qi-hardware
kyak has quit [Quit: Lost terminal]
wolfspraul has joined #qi-hardware
wej has joined #qi-hardware
<apelete> Hi larsc
wej_ has quit [Ping timeout: 250 seconds]
<apelete> larsc: is it possible to do early debugging on mips ?
<apelete> trying to debug the dma-jz4740.c driver (modified to work with jz4770), and my kernel seems to be going into panic *before* kgdb driver is loaded
<apelete> which could mean dma driver is loaded before the serial_8250 driver
<apelete> larsc: is it possible to load the serial driver earlier in order to have early debugging ?
fmeerkoetter has joined #qi-hardware
porchaso0 has joined #qi-hardware
qi-bot9 has joined #qi-hardware
qi-bot has quit [*.net *.split]
porchao has quit [*.net *.split]
qi-bot9 is now known as qi-bot
<larsc> apelete: yes, I think we have support for early_printk on jz4740
<larsc> set CONFIG_EARLY_PRINTK=y
<larsc> see arch/mips/jz4740/prom.c and prom_putchar()
<apelete> larsc: I set CONFIG_EARLY_PRINTK=y on jz4770 too, but it didn't help
<larsc> if there are multiple UARTs you may have to select the correct one
<larsc> check the jz4770 prom_putchar function
<apelete> larsc: looks like prom_putchar is writing to a UART2_BASE register address
<apelete> does that mean it might be the wrong UART to write to ?
<larsc> I don't know, which uart are you connected to?
<apelete> ttyS2 from the cmdline point of view
<larsc> sounds like uart 2
jow_lapt1p is now known as jow_laptop
<apelete> larsc: compared to an old jz4740 boot log, serial driver is loaded late too -> http://paste.debian.net/117756/
<apelete> loads at line 82
jluis has quit [Remote host closed the connection]
jluis has joined #qi-hardware
atommann has quit [Ping timeout: 260 seconds]
<larsc> early printk bypasses the serial driver
jluis has quit [Ping timeout: 260 seconds]
fmeerkoetter has quit [Ping timeout: 250 seconds]
fmeerkoetter has joined #qi-hardware
<apelete> larsc: so it's not possible to launch the serial driver earlier than what is done on jz4740 ?
jluis has joined #qi-hardware
atommann has joined #qi-hardware
kyak has joined #qi-hardware
atommann has quit [Quit: Leaving]
uwe__ is now known as uwe_
pcercuei has joined #qi-hardware
<DocScrutinizer05> make sure your UART doesn't load DMA driver ;-)
<DocScrutinizer05> aaah >><larsc> early printk bypasses the serial driver<< makes sense
<DocScrutinizer05> wpwrak: (browsers)
<DocScrutinizer05> TECHNISCHE WARNUNG TW-T14/0079
<DocScrutinizer05> Titel: Sicherheitsupdate für den Google Chrome Browser
<DocScrutinizer05> >> Der Google Chrome Browser vor Version 37.0.2062.94 für Windows, Mac und Linux enthält mehrere kritische Sicherheitslücken. Diese können von einem entfernten Angreifer ausgenutzt werden, um beliebiegen Programmcode auszuführen, .....<<
<DocScrutinizer05> oops ECHAN
<DocScrutinizer05> well, not that bad anyway
jluis has quit [Ping timeout: 260 seconds]
fmeerkoetter has quit [Quit: Konversation terminated!]
<ysionneau> would be cool if Ingenic would liberate as open source HDL its Xburst core
<ysionneau> like it would be cool if I win the lottery also
<larsc> otror space travel!
<larsc> for everybody!
<wpwrak> DocScrutinizer05: hmm,sounds nasty. thanks ! let's hope chromium on ubuntu gets fixed quickly
rz2k has joined #qi-hardware
woakas has quit [Ping timeout: 240 seconds]
arhuaco has quit [*.net *.split]
tumdedum has quit [*.net *.split]
apelete has quit [*.net *.split]
arhuaco has joined #qi-hardware
tumdedum has joined #qi-hardware
apelete has joined #qi-hardware
<wpwrak> whitequark: speaking of quantum conscience and such ... http://www.smbc-comics.com/index.php?id=2657#comic
wej has quit [Ping timeout: 250 seconds]
<arhuaco> wpwrak: Old but good! (new to me).
<wpwrak> (old) yeah, found smbc only recently. and i can't spend all day to catch up :)
<arhuaco> wpwrak: Happens to me with XKCD. I do not know if it is (just) me, but now they are way too many and I can no longer keep up with them. Even if they are in my feeds.
wej has joined #qi-hardware
<wpwrak> yes, the list keeps growing. slowly, but steadily. so far, i can still manage but the comicalypse seems inevitable in the long run
<pcercuei> wej, hi, I have a request for GMU: make the file selector point to $HOME when you start GMU, instead of the data directory (which is generally in /usr/share in Linux)
* kristianpaul removed its xkcd rss time ago
<wej> pcercuei: hi, actually, that directory is configurable (DefaultFileBrowserPath), which by default is set to the working directory (which might be /usr/share as you said). The reason for that "current directory" default simply was that on the handhelds were Gmu originated, it was useful to assume that directory. On PCs and similar devices the user's home directory probably is more useful.
<wej> maybe i'll change the default to the user's home
<pcercuei> hmmok
<pcercuei> I could do DefaultFileBrowserPath=/usr/local/home but then it may break if we decide to move the home directory
<pcercuei> other than that, I made an OPK for it
<wej> maybe i could add support for ~ in the path, so one could specify that and it picks the right home directory of the user, whatever that is
<pcercuei> ah, that would be great, yes
<wej> i'll add it to my todo list ;)
<wej> so i don't forget :D
<pcercuei> thanks!
<pcercuei> you said that GMU is resolution-independent now?
<wej> yes, it is
<wej> you can even run it windowed and resize its window
<wej> on platforms that support windows that is ;)
<pcercuei> and does it use the highest resolution by default?
<pcercuei> or the current screen's resolution?
<wej> usually you specify the desired resolution it Gmu's config file
<wej> SDL_frontend.Width=640
<wej> SDL_frontend.Height=480
<wej> like so
<wej> and then there is SDL_frontend.Fullscreen=yes/no
<wej> for devices that support windowed and fullscreen operation
<pcercuei> so if I set SDL_frontend.Width=640 SDL_frontend.Height=480 but I only support 320x240 maximum, will it crash?
<wej> it won't crash, but it won't run properly either. the sdl frontend will try to use that resolution and if that fails it does not continue to start
<pcercuei> hmmok
rz2k has quit []
woakas has joined #qi-hardware
pcercuei has quit [Quit: leaving]
pcercuei has joined #qi-hardware
newcup has joined #qi-hardware
<apelete> larsc: testing kgdb with a working kernel -> http://paste.debian.net/117889/
<apelete> it loads after the serial driver as expected, which itself loads late in the boot process, after the lcd driver...
<apelete> ...looks like I'm screwed :-(
<larsc> I still don[t understand the problem
<mth> what do you want to debug with it?
<larsc> or is the problem that kgdb is not working?
<apelete> I want to debug the dma driver
<mth> do you need to catch it before it initializes?
<apelete> problem is the kernel is crashing in the dma driver before kgdb driver is loaded
<larsc> you can try to build the dma driver as a module
<apelete> didn't think about that, silly me
<mth> although that won't work if the module is on an SD card and the mmc driver depends on the DMA module...
<apelete> mth: by the time I start working on the mmc driver I expect the dma one to be stable enough
<apelete> at least I hope so :)
<pcercuei> kgdb requires you to hit some keyboard keys, no?
wh1tequark has joined #qi-hardware
<wh1tequark> if pointless a bit
wh1tequark has quit [Quit: Page closed]
<apelete> pcercuei: the kernel can be configured to automatically pause during boot and wait for gdb to be attached to it
<DocScrutinizer05> that's cool
<whitequark> DocScrutinizer05: the laser thing?
<DocScrutinizer05> laser thing? nah, gdb sync
<whitequark> oh, right
<DocScrutinizer05> laser thing the 3W lasers intrigue me. Would like to use those for proper soldering tasks - though the absolute failure to work on covered solder points like BGA is obvious
<whitequark> indeed, it's sorta pointless except as a curiosity
<whitequark> I wonder what is the absorption spectrum of solder
<whitequark> like, maybe IR won't be reflected? I don't know
wolfspraul has quit [Quit: leaving]
<whitequark> huh
<DocScrutinizer05> with *that* laser power you actually can start tooling
<whitequark> I dunno, you can get a tube with hundreds or thousands of W pretty easily
<DocScrutinizer05> I don't think you can get it (operating) for that pricetag
<DocScrutinizer05> nor is it in a format where you could integrate it into e.g. a CNC head
<DocScrutinizer05> nevertheless I might be interested *where* to get such tube easily. Since I'm musing about building a nice show laser since long
<DocScrutinizer05> it's simply I'm adicted to light emitting objects, and particularly monochromatic ones. And when they are even coherent and focused, all the better
<DocScrutinizer05> doesn't mean the tritium light keyring in my pocket lost its fascination ;-)
<whitequark> DocScrutinizer05: ebay
<whitequark> some CO2 laser tube is pretty cheap
<whitequark> well
<whitequark> $600
<whitequark> maybe half that if you DIY
<DocScrutinizer05> CO2 is fine, but has one obvious flaw for an addict to light emitting objects - that addiction is pretty much a perception driven thing
<DocScrutinizer05> yeah, I checked for 50W range CO2 lasers nly 6 months ago. Wasn't too easy to spot something that sounded like it might actually pan out and work in the end
<DocScrutinizer05> the 70$ blue one is awesome https://sites.google.com/site/dtrlpf/home/diodes/9mm-445nm