**** BEGIN LOGGING AT Sun May 31 02:59:59 2015 May 31 09:48:10 gm May 31 12:42:14 Gm May 31 15:55:32 _av500_: ping May 31 15:56:29 jkridner: ping May 31 15:57:01 <_av500_> jo May 31 15:57:41 _av500_ couldn't reach to DiegoTc May 31 15:58:12 till now I didn't start coding and couldn't untill DiegoTc finish May 31 15:58:43 so how should I fix that? May 31 16:13:06 <_av500_> ebadawy: I am reachin out to them May 31 16:13:39 _av500_: OK May 31 17:00:34 moin May 31 17:32:44 mornin May 31 17:32:51 how is it going ? May 31 18:13:32 ds2 :ping May 31 18:20:09 apaar___: pong May 31 18:20:24 apaar__: pong May 31 18:25:56 ds2 :the driver sysfs is working but i am having trouble accessing shared mem :( looks like i have the base wrong address May 31 18:27:32 apaar__: you might have to map it in seperately May 31 18:27:42 the address is fixed May 31 18:27:56 or check the length of your mapping May 31 18:31:11 ds2 :do i have to use mmap? right now i am just using a volatile int pointer May 31 18:33:10 not mmap. there is a kernel equiv. May 31 18:33:18 can't remember the name of the call May 31 18:33:27 it is like iomap or ioremap May 31 18:33:47 ok thanks :) i will have a look May 31 18:36:35 oh beware... the size info may not come from DT...these chips at one point had a resource manager that defined it. and it may have defined it in multiple chunks rather then a monolithic blob Jun 01 01:24:01 What is a hot path?in the 'MMC and DMA Linux performance' project **** ENDING LOGGING AT Mon Jun 01 02:59:59 2015