2014-07-18 00:07 FDCX has joined #qi-hardware
2014-07-18 00:07 FDCX has quit [Read error: Connection reset by peer]
2014-07-18 00:07 FDCX has joined #qi-hardware
2014-07-18 00:08 FDCX_ has joined #qi-hardware
2014-07-18 00:08 FDCX_ has quit [Read error: Connection reset by peer]
2014-07-18 00:08 FDCX has quit [Remote host closed the connection]
2014-07-18 00:09 FDCX has joined #qi-hardware
2014-07-18 00:43 FDCX has quit [Remote host closed the connection]
2014-07-18 00:43 FDCX has joined #qi-hardware
2014-07-18 01:13 <nicksydney> wpwrak: http://www.instructables.com/id/How-Can-StikNPeel-TM-Rework-Stencil/
2014-07-18 01:17 uwe_ has quit [Ping timeout: 240 seconds]
2014-07-18 01:18 uwe_ has joined #qi-hardware
2014-07-18 02:01 xiangfu has joined #qi-hardware
2014-07-18 02:23 <hozer> hey at least with the linux kernel we get to see all the bad code. No such chance will all the damn firmware for various hardware devices
2014-07-18 03:45 rz2k has quit [Read error: Connection reset by peer]
2014-07-18 04:29 nicksydney has quit [Remote host closed the connection]
2014-07-18 04:29 nicksydney has joined #qi-hardware
2014-07-18 05:59 nicksydney has quit [Remote host closed the connection]
2014-07-18 06:52 wej_ has joined #qi-hardware
2014-07-18 06:55 wej has quit [Ping timeout: 250 seconds]
2014-07-18 07:02 BlackGyver_ has joined #qi-hardware
2014-07-18 07:03 <BlackGyver_> eggcelent
2014-07-18 07:03 <BlackGyver_> Good morning everyone
2014-07-18 07:03 <BlackGyver_> I'm a bit of a newb when it comes to hardware
2014-07-18 07:03 <BlackGyver_> I was looking to know what kind of performance increases (and in which kind of applications) I would get by having my RAM's clock speed higher than what my CPU asks for
2014-07-18 07:04 <BlackGyver_> ie. grabbing 2133Mhz RAM on a processor asking for 1333/1600
2014-07-18 07:05 <BlackGyver_> oh I don't think I'm actually on a good channel for that kind of questions, am I
2014-07-18 07:05 <BlackGyver_> whoops
2014-07-18 07:06 <BlackGyver_> Well, feel free to answer anyway if you have an idea
2014-07-18 07:07 BlackGyver_ is now known as BlackGyver
2014-07-18 07:21 <DocScrutinizer05> BlackGyver: for the channel it's maybe a tad off topic, but anyway faster RAM will do nothing when your CPU doesn't use faster speed.
2014-07-18 07:21 <DocScrutinizer05> clock speed of RAM bus even
2014-07-18 07:22 <DocScrutinizer05> it's like with your car engine: it doesn't get more horsepower when your fuel has higher octane
2014-07-18 07:23 <DocScrutinizer05> fuel needs suppicient octane for the compression of your engine, and RAM needs to be fast enough for the RAM bus clock speed of your CPU. Using more than "sufficient" doesn't bring any benefit
2014-07-18 07:24 <ysionneau> well ram is not only about bus speed
2014-07-18 07:24 <ysionneau> it's also about switching from one bank to another speed
2014-07-18 07:24 <ysionneau> switching from read to write speed
2014-07-18 07:24 <ysionneau> etc
2014-07-18 07:25 <ysionneau> so "speed" of RAM matters (for DRAM I mean)
2014-07-18 07:25 <DocScrutinizer05> of course there are car engines that dynamically optimize the ignition point, and there are CPU memory controllers that "dynamically" adapt memory bus clock speed
2014-07-18 07:27 <DocScrutinizer05> ysionneau: well, yes. There are more parameters than only mere clock speed. There's stuff like RAS timing etc. But all that are parameters of the memory controller and unless the memory controller adjusts them, no increased speed of the RAM you use will change the system performance
2014-07-18 07:27 <BlackGyver> Alright! Thanks a bunch
2014-07-18 07:27 <BlackGyver> Sorry for the confusion about the channel
2014-07-18 07:28 <BlackGyver> Cheers! Have a good day!
2014-07-18 07:28 <ysionneau> these are parameter of the RAM, but indeed the memory controller needs to "know" them and use them
2014-07-18 07:28 <DocScrutinizer05> for PC architecture (x86) it's usual that CPU reads the parameters out of a config ROM in RAM and adjusts parameters of mem controller
2014-07-18 07:28 <ysionneau> yes
2014-07-18 07:28 BlackGyver has left #qi-hardware ["Bangarang, motherfucker."]
2014-07-18 07:28 <DocScrutinizer05> but often you need to set them manually in BIOS
2014-07-18 07:28 <ysionneau> but then, if your memory controller is clever and know how to adapt, the limiting factor is the speed of your RAM
2014-07-18 07:29 <ysionneau> if your memory controller is stupid then indeed you don't care about RAM parameters
2014-07-18 07:29 <ysionneau> you just access it slowly, in a non pipelined way etc
2014-07-18 07:30 <DocScrutinizer05> there's no such thing like stupid memory controllers nowadays in all but the most stupid CPUs which only come with embedded RAM
2014-07-18 07:32 <DocScrutinizer05> usually RAM sticks have a small serially attached (EP)ROM with the parameters of the RAM on that stick, and the BIOS of your PC reads that out and sets memory controller parameters accordingly
2014-07-18 07:33 <DocScrutinizer05> some RAM sticks come with bogus or broken info in that ROM, and then you need to config RAM parameters in BIOS setup manually
2014-07-18 07:34 <DocScrutinizer05> there's no mem controller that can really autodetect speed of RAM
2014-07-18 07:35 <DocScrutinizer05> since there's no physical parameter on the signal lines that tells mem controller if RAM can cope with the speed
2014-07-18 07:36 <DocScrutinizer05> and RAM access is not async, i.e. there's no data-ready or other ACK feedback from RAM to controller
2014-07-18 07:36 <DocScrutinizer05> afaik
2014-07-18 07:40 <DocScrutinizer05> and re >><BlackGyver_> ie. grabbing 2133Mhz RAM on a processor asking for 1333/1600<< I doubt there are CPUs out there that "ask for" 1333/1600 but could go as fast as 2133
2014-07-18 07:41 <DocScrutinizer05> usually the SPI data has not even parameters for RAS/CAS etc on other than max clock speed of RAM
2014-07-18 07:43 <DocScrutinizer05> so when the RAM is saying 2133;3CAS;5RAS then a CPU running the RAM at 1333 nevertheless will use 5 CAS clock cycles and 3 RAS. So no speed increase at all, unless you calculate CAS/RAS etc manually and config it in BIOS setup manually. --- disclaimer AFAIK
2014-07-18 07:44 <DocScrutinizer05> and even that isn't worth it, the speed increase is rather marginal
2014-07-18 07:45 <apelete> Hi larsc
2014-07-18 07:45 <apelete> yesterday I was testing my mmc async requests patches against 3.16-rc5, and I hit a dma-jz4740 related bug: http://paste.debian.net/110350/
2014-07-18 07:46 <apelete> this is the one solved by these two patches:
2014-07-18 07:46 <apelete> http://git.seketeli.net/cgit/~apelete/qi-kernel.git/commit/?h=jz-3.15&id=1bddbc0ac2a7df1eeb2ebf9810fdbee272acdf17
2014-07-18 07:46 <apelete> http://git.seketeli.net/cgit/~apelete/qi-kernel.git/commit/?h=jz-3.15&id=523058459f54e391ae1ee1f62f2bdb81002fbc93
2014-07-18 07:46 <apelete> I think this is the first time I hit it the bug on the upsteam mainline, found it funny :)
2014-07-18 07:47 <apelete> larsc: anyway, mmc async requests is now working, by mapping only dma area in pre_request(), like you said
2014-07-18 07:48 <apelete> and it was also explicitely documented in dmaengine.txt, must have missed the point when I first read it
2014-07-18 07:51 <larsc> good :)
2014-07-18 07:54 <DocScrutinizer05> larsc: do you know anything (existence for example) of crtouchb10 touchscreen controller drivers in upstream or elsewhere?
2014-07-18 07:57 <apelete> larsc: is there anything substantial left to do on qi-kernel ?
2014-07-18 07:58 <larsc> DocScrutinizer05: no
2014-07-18 07:58 <DocScrutinizer05> thanks! :-)
2014-07-18 07:58 <DocScrutinizer05> though actually :-S
2014-07-18 07:58 <larsc> apelete: migrating to the common clock framework
2014-07-18 07:59 <DocScrutinizer05> larsc: wpwrak: could you have a look at http://www.freescale.com/webapp/sps/download/license.jsp?colCode=CRTOUCH_DEMO_LINUX_BSP_IMX53QSB&location=null&fpsp=1 and see if that's any useful?
2014-07-18 08:00 <apelete> larsc: \o/ (<-- infinite hacker joy)
2014-07-18 08:00 <apelete> was thinking you would say no :)
2014-07-18 08:00 <larsc> apelete: I started with that some time ago, but never finished it
2014-07-18 08:01 <eintopf> huhu
2014-07-18 08:01 <apelete> larsc: what is that about, any more details ?
2014-07-18 08:02 * apelete just found a lwn article about common clock framework
2014-07-18 08:02 <DocScrutinizer05> wpwrak: larsc: http://privatepaste.com/6f58478d6f
2014-07-18 08:02 <DocScrutinizer05> excerpt from the .pdf to be found in above URL
2014-07-18 08:09 <larsc> apelete: we implemnt the clock API with a custom implementation right now
2014-07-18 08:09 <larsc> switching over to the common clock framework means we'll use the the generic implementation
2014-07-18 08:11 <apelete> larsc: does "custom implementation" mean "not upstream" ?
2014-07-18 08:11 <larsc> custom means, we implement the API functions in arch/mips/jz4740/clk.h
2014-07-18 08:11 <larsc> custom means, we implement the API functions in arch/mips/jz4740/clk.c
2014-07-18 08:12 <apelete> ok, will take a look at that
2014-07-18 08:15 <larsc> DocScrutinizer05: do you know where the touchscreen_crtouch.patch is?
2014-07-18 08:15 <DocScrutinizer05> http://www.freescale.com/webapp/sps/download/license.jsp?colCode=CRTOUCH_DEMO_LINUX_BSP_IMX53QSB&location=null&fpsp=1
2014-07-18 08:15 <DocScrutinizer05> tarball
2014-07-18 08:15 <DocScrutinizer05> only click accept
2014-07-18 08:16 <DocScrutinizer05> all the way down at bottom
2014-07-18 08:16 <larsc> well, thats a /dev/input/eventX driver, but not upstream material
2014-07-18 08:16 <DocScrutinizer05> nfc what I accepted ;-P
2014-07-18 08:17 <DocScrutinizer05> yup, guessed that much. Does it look useful though?
2014-07-18 08:17 Textmode has quit [Quit: "It was one dev, naked in a room with a carton of cigarettes, a thermos full of coffee and bourbon, and all his summoned angels."]
2014-07-18 08:17 <DocScrutinizer05> IOW could some kernel hacker easily build an upstream compliant driver from it?
2014-07-18 08:18 <larsc> it doesn't look to complex
2014-07-18 08:18 <DocScrutinizer05> I'm asking you since I have no idea about "easily"
2014-07-18 08:18 <DocScrutinizer05> fine \o/ :-D
2014-07-18 08:18 <DocScrutinizer05> thanks a megaton!
2014-07-18 08:19 * apelete was thinking about hacking on JZ4770 kernel support for GCW0 soon, maybe he'll have to manage workload on both qi-kernel and gcw-kernel
2014-07-18 08:19 <apelete> nights are going to get ever shorter...
2014-07-18 08:20 <DocScrutinizer05> longer ;-)
2014-07-18 08:20 <DocScrutinizer05> and the days are endless then
2014-07-18 08:20 <larsc> I have a at least somewhat working gcw board now
2014-07-18 08:20 <apelete> haha, good point
2014-07-18 08:21 <apelete> larsc: oh, you're working on gcw0 already ?
2014-07-18 08:22 <larsc> no
2014-07-18 08:22 <larsc> but I have the board
2014-07-18 08:22 <larsc> I could work on it if I had time
2014-07-18 08:23 <larsc> I think they were looking on switching to the jz4740 mmc driver
2014-07-18 08:34 jow_lapt1p is now known as jow_laptop
2014-07-18 08:51 <apelete> yes, I'll talk with pcercueil and mth about that
2014-07-18 09:20 <DocScrutinizer05> http://www.vox.com/2014/7/17/5913089/did-this-ukrainian-rebel-commander-take-credit-for-shooting-down-the/in/5677250
2014-07-18 09:22 <DocScrutinizer05> http://www.vox.com/2014/7/17/5912677/plane-ukraine-malaysia
2014-07-18 09:22 <DocScrutinizer05> I don't like vox too much, but those sites sound not too much biased and unfair
2014-07-18 09:47 <whitequark> ugh
2014-07-18 09:48 xiangfu_ has joined #qi-hardware
2014-07-18 09:51 xiangfu has quit [Ping timeout: 250 seconds]
2014-07-18 10:45 jekhor has joined #qi-hardware
2014-07-18 10:54 pcercuei has joined #qi-hardware
2014-07-18 11:06 jekhor_ has joined #qi-hardware
2014-07-18 11:06 jekhor has quit [Ping timeout: 240 seconds]
2014-07-18 12:33 wej_ has quit [Ping timeout: 245 seconds]
2014-07-18 12:47 wej has joined #qi-hardware
2014-07-18 13:12 xiangfu_ has quit [Remote host closed the connection]
2014-07-18 13:44 jekhor has joined #qi-hardware
2014-07-18 13:47 jekhor_ has quit [Ping timeout: 240 seconds]
2014-07-18 15:02 jekhor_ has joined #qi-hardware
2014-07-18 15:03 jekhor has quit [Ping timeout: 264 seconds]
2014-07-18 15:29 jekhor_ has quit [Ping timeout: 250 seconds]
2014-07-18 15:29 jekhor__ has joined #qi-hardware
2014-07-18 15:59 jekhor has joined #qi-hardware
2014-07-18 16:00 jekhor__ has quit [Ping timeout: 240 seconds]
2014-07-18 16:04 jekhor_ has joined #qi-hardware
2014-07-18 16:07 dos1 has quit [Quit: Kabum!]
2014-07-18 16:08 jekhor has quit [Ping timeout: 240 seconds]
2014-07-18 16:09 dos1 has joined #qi-hardware
2014-07-18 16:15 qwebirc13105 has joined #qi-hardware
2014-07-18 16:16 qwebirc13105 is now known as rjeffries
2014-07-18 16:19 <rjeffries> wpwrak: suggest you add "anelok password device" to list of what channel covers
2014-07-18 16:20 dos1 has quit [Quit: Kabum!]
2014-07-18 16:22 dos1 has joined #qi-hardware
2014-07-18 16:22 <kyak> we can't discuss it without adding it to the list? :)
2014-07-18 16:38 rjeffries has quit [Ping timeout: 246 seconds]
2014-07-18 16:50 <wpwrak> DocScrutinizer05: (license) hmm, i guess it depends on what you want to do
2014-07-18 16:51 <wpwrak> e.g., "to use, only as part of, or integrated within, Authorized Systems" and ""Authorized System" means the hardware system(s) or software program(s) marketed by you which contains an i.MX"
2014-07-18 16:53 <wpwrak> also, it only allows you to distribute object code, no source
2014-07-18 16:54 <wpwrak> so i'd heed nancy reagan's wide advice and "just say no" :)
2014-07-18 16:56 <wpwrak> "The included patches were created based on" sounds like derivative work. if the work it was derived from in under that license, then it may even be in violation to that license.
2014-07-18 16:57 <wpwrak> general rule: if some piece of hardware doesn't come with sufficient documentation to let you write your own complete firmware, but instead requires something provided by the vendor, then this almost always means that you can't use it for Free Software
2014-07-18 17:13 <DocScrutinizer05> sorry, I can't follow. We have a .c fule with a GPLv2 license and we have a datasheet that for sure has all needed info to write whatever you want
2014-07-18 17:13 <DocScrutinizer05> file*
2014-07-18 17:14 <DocScrutinizer05> I don't give a **** which way that .c file got created
2014-07-18 17:15 <DocScrutinizer05> the chip manufacturer provided c code with a GPL and in my book that GPL can't be overridden by any random general license that obviously is a standard disclaimer used for all code that manuf provides
2014-07-18 17:16 <wpwrak> ah, so freescale released source under GPL ? and added a non-GPL license ? nice organization :)
2014-07-18 17:16 <DocScrutinizer05> btw this is kinda ECHAN
2014-07-18 17:16 <wpwrak> i was just commenting on the license, since you asked for opinions on it
2014-07-18 17:17 <DocScrutinizer05> I honestly wonder what you refer to when you haven't seen the original
2014-07-18 17:17 <wpwrak> <DocScrutinizer05> larsc: wpwrak: could you have a look at http://www.freescale.com/webapp/sps/download/license.jsp?colCode=CRTOUCH_DEMO_LINUX_BSP_IMX53QSB&location=null&fpsp=1 and see if that's any useful?
2014-07-18 17:17 <DocScrutinizer05> http://projects.goldelico.com/p/neo900/issues/527/#ic1922
2014-07-18 17:18 <DocScrutinizer05> I obviously didn't mean that nonsensical biolerplate "licence"
2014-07-18 17:18 <DocScrutinizer05> how could *that* be useful?
2014-07-18 17:18 <wpwrak> oh, there are buttons at the bottom ;)
2014-07-18 17:18 <wpwrak> well, "useful" as in "can we live with that"
2014-07-18 17:19 <DocScrutinizer05> please reread full chanlog
2014-07-18 17:19 <DocScrutinizer05> just two lines later I told that there are buttons
2014-07-18 17:19 <DocScrutinizer05> and the convo with larsc wasn't about licence issues
2014-07-18 17:20 <DocScrutinizer05> afk
2014-07-18 17:39 <DocScrutinizer05> http://privatepaste.com/a479e57648
2014-07-18 17:41 <DocScrutinizer05> https://github.com/EmcraftSystems/linux-emcraft/blob/master/drivers/input/touchscreen/crtouch_mt.c
2014-07-18 17:42 rz2k has joined #qi-hardware
2014-07-18 17:44 <DocScrutinizer05> https://bitbucket.org/htdevices/linux-2.6-imx/commits/37e59882247048f3c144022e0be67fc0f7eb0018
2014-07-18 17:44 <DocScrutinizer05> https://bitbucket.org/htdevices/linux-2.6-imx/commits/4876309f1c2636c1a7aa13848dca1372fc74fc2c
2014-07-18 18:35 wej has quit [*.net *.split]
2014-07-18 18:38 wej has joined #qi-hardware
2014-07-18 19:05 jekhor_ has quit [Ping timeout: 256 seconds]
2014-07-18 19:55 wolfspraul has quit [*.net *.split]
2014-07-18 19:55 jow_laptop has quit [*.net *.split]
2014-07-18 19:55 jow_laptop has joined #qi-hardware
2014-07-18 19:55 wolfspraul has joined #qi-hardware
2014-07-18 19:55 newcup has quit [*.net *.split]
2014-07-18 20:15 jekhor has joined #qi-hardware
2014-07-18 22:12 Luke-Jr has quit [Read error: Connection reset by peer]
2014-07-18 22:13 Luke-Jr has joined #qi-hardware
2014-07-18 22:21 jekhor has quit [Ping timeout: 240 seconds]
2014-07-18 23:56 wolfspraul has quit [Ping timeout: 240 seconds]
2014-07-18 23:58 wolfspraul has joined #qi-hardware