**** BEGIN LOGGING AT Wed Jun 01 02:59:59 2016
Jun 01 03:02:48 <ZeekHuge> Abhishek_: ahh .. Nothing, I got it now :). I got it now even if SOMEHOW beaglelogic works, that would not help much as lot of has changed. So what I can do is learn from beaglelogic's firmware. and then probably use it.
Jun 01 03:03:28 <ZeekHuge> and also the buffering part of beaglelogic's kernel.
Jun 01 03:05:12 <Abhishek_> Figure out how the 4.4 rpmsg driver works first.
Jun 01 03:05:25 <Abhishek_> That's the one you'll be using.
Jun 01 03:05:51 <ZeekHuge> okay.
Jun 01 03:06:40 * ZeekHuge is going afk for breakfast.
Jun 01 03:26:13 <ZeekHuge> .
Jun 01 05:26:50 <ZeekHuge> Hi Wormo !
Jun 01 05:26:58 <ZeekHuge> have a minute ?
Jun 01 05:27:07 <Wormo> Yep :)
Jun 01 05:27:11 <ZeekHuge> https://github.com/ZeekHuge/BeagleScope/blob/master/.travis.yml
Jun 01 05:27:15 <ZeekHuge> this script
Jun 01 05:27:29 <ZeekHuge> I am running it on my system and its working fine
Jun 01 05:27:35 <ZeekHuge> but the travis fails
Jun 01 05:27:58 <ZeekHuge> https://travis-ci.org/ZeekHuge/BeagleScope
Jun 01 05:29:22 <ZeekHuge> anything you see wrong there ?
Jun 01 05:29:33 <Wormo> I'll take a look
Jun 01 05:29:57 <ZeekHuge> from the travis logs, it looks like theres something wrong with the cross_compiler
Jun 01 05:31:44 <Wormo> Yes, weren't you using the linaro toolchain?
Jun 01 05:32:21 <Wormo> this appears to be using stock ubuntu arm cross-compile toolchain
Jun 01 05:32:53 <ZeekHuge> okay.
Jun 01 05:33:16 <Wormo> Makefile:660: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
Jun 01 05:33:38 <ZeekHuge> so that may be the problem. but then, how is this working ? https://github.com/pmezydlo/SPI_slave_driver_implementation/blob/master/.travis.yml
Jun 01 05:34:48 <ZeekHuge> and this looks like linaro https://travis-ci.org/ZeekHuge/BeagleScope#L228
Jun 01 05:35:21 <ZeekHuge> 228 arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
Jun 01 05:35:44 <Wormo> linaro but old
Jun 01 05:36:21 <Wormo> we were using linaro 5.x as the default from RCN build scripts the other day
Jun 01 05:36:39 <ZeekHuge> okay. I'll change that and see.
Jun 01 05:37:08 <ZeekHuge> but pmezydlo's is still working with it. Anyway, I'll change it.
Jun 01 05:37:09 <Wormo> as far as why the other one works, I'd say different kernel .config
Jun 01 05:37:45 <Wormo> stack-protector stuff turned off I bet, so less is required of the toolchain
Jun 01 05:39:06 <Wormo> is using a slightly different kernel, the -rt varient, but I'd guess it's config difference that matters
Jun 01 15:30:11 <alexhiam> kiran4399: no status report??
Jun 01 15:30:51 <kiran4399> oops.. sorry.. alexhiam: will upload now in the mailing list.. actually wrote in my blog.
Jun 01 15:31:29 <alexhiam> ml or it's not real ;)
Jun 01 15:31:55 <alexhiam> kiran4399: also, can you fill in your links here: http://elinux.org/BeagleBoard/GSoC/2016_Projects#Project:_API_support_for_Beaglebone_Blue
Jun 01 15:46:02 * _av500_ checks beagle GSOC mailing list 
Jun 01 15:52:23 <_av500_> 6 reports
Jun 01 15:53:42 <alexhiam> _av500_: kiran4399's just arrived
Jun 01 15:54:07 <alexhiam> kiran4399: those need to be posted to the ml on tuesday from here on out
Jun 01 15:54:30 <kiran4399> alexhiam: did not get that..
Jun 01 15:55:48 <ds2> hmmmmm
Jun 01 15:56:00 <m_w> good call
Jun 01 15:56:21 <m_w> ooops wrong window :)
Jun 01 15:56:53 <kiran4399> alexhiam: I did not understand your last message..
Jun 01 15:57:12 <alexhiam> kiran4399: which?
Jun 01 15:57:17 <ds2> 6?
Jun 01 15:57:26 <kiran4399> alexhiam: those need to be posted to the ml on tuesday from here on out
Jun 01 15:58:06 <alexhiam> kiran4399: oh, the progress reports. They need to be posted to the gsoc mailing list every tuesday
Jun 01 15:58:20 <kiran4399> ok..
Jun 01 16:00:11 <bradfa> hola
Jun 01 16:00:42 <henrix_> hi
Jun 01 16:00:53 <amragaey> hi ebadawy, it's long time nice to see you
Jun 01 16:01:18 <amragaey> hi all
Jun 01 16:01:39 <m_w> meeting time?
Jun 01 16:03:00 <nerdboy> _av500_'s 5 min leeway...
Jun 01 16:03:11 <pmezydlo> hi everyone
Jun 01 16:04:18 <ZeekHuge> Happy birthday amragaey ! :)
Jun 01 16:04:35 <ebadawy> hi amragaey, exams u know!
Jun 01 16:04:51 <rma_> hi all
Jun 01 16:04:52 <ebadawy> happy birth day BTW :)
Jun 01 16:05:07 <amragaey> ZeekHuge, ebadawy thanks alot :D
Jun 01 16:05:20 <pmezydlo> rma_: Happy Birthday!
Jun 01 16:05:29 <amragaey> ebadawy, yes same here :)
Jun 01 16:05:53 <_av500_> hello everybody
Jun 01 16:05:55 <rma_> Birthday? huh, still couple of days:)
Jun 01 16:05:55 <henrix_> from me too:)
Jun 01 16:06:24 <rma_> Happy from me as well
Jun 01 16:06:30 <rma_> ;)
Jun 01 16:06:59 <_av500_> 1) WELCOME
Jun 01 16:07:11 <_av500_> 5 past, so lets start
Jun 01 16:07:11 <amragaey> thanks guys :D
Jun 01 16:07:20 <_av500_> happy birthday amragaey
Jun 01 16:07:36 <amragaey> _av500_, thanks :D
Jun 01 16:07:46 <_av500_> 2) who's here?
Jun 01 16:07:51 <_av500_> can I see 7 hands
Jun 01 16:07:52 <pmezydlo> i am
Jun 01 16:07:56 <amragaey> 2
Jun 01 16:08:03 * nerdboy schedules the birthday spanking, passes out cricket bats
Jun 01 16:08:22 <_av500_> 2 only?
Jun 01 16:08:24 <henrix_> hi
Jun 01 16:08:24 <Visaoni> ^
Jun 01 16:08:28 <chanakya_vc> I hope I am not late
Jun 01 16:08:31 <_av500_> 5
Jun 01 16:08:39 <m_w> ut oh
Jun 01 16:09:04 <_av500_> pmezydlo: kiran4399 ??
Jun 01 16:09:07 <_av500_> oops
Jun 01 16:09:13 <_av500_> pmezydlo is here
Jun 01 16:09:17 <_av500_> kiran4399 ???
Jun 01 16:09:27 <kiran4399> 6
Jun 01 16:09:30 <ZeekHuge> 7
Jun 01 16:09:40 <chanakya_vc> hello everyone!! And happy birthday amragaey !
Jun 01 16:09:42 <_av500_> great
Jun 01 16:09:48 <_av500_> all 7 on board
Jun 01 16:10:04 <_av500_> 3) reports
Jun 01 16:10:15 * nerdboy adds report agenda topic
Jun 01 16:10:35 <nerdboy> *content and timeliness
Jun 01 16:10:49 <_av500_> I count only 6 reports
Jun 01 16:10:52 <_av500_> no?
Jun 01 16:11:59 <kiran4399> _av500_: did you count mine?
Jun 01 16:12:04 <_av500_> Visaoni: did you send a report?
Jun 01 16:12:06 <_av500_> kiran4399: yes
Jun 01 16:12:09 * nerdboy will soon start calling Visaoni by his full first/middle name...
Jun 01 16:12:21 * Visaoni is waiting on mail
Jun 01 16:12:34 <Visaoni> didn't seem like a particularly useful report...
Jun 01 16:12:50 <m_w> :-/
Jun 01 16:13:02 <alexhiam> reports are required, regardless of content
Jun 01 16:13:10 <nerdboy> there was actual purchasing work/research
Jun 01 16:13:31 <ds2> Visaoni: doesn't matter... we need visibility into what is going on (or not going on)
Jun 01 16:13:39 <alexhiam> Visaoni: even if it just explains why you couldn't get anything done, it needs to be posted so we know what's up
Jun 01 16:13:56 <Visaoni> alright
Jun 01 16:14:00 <nerdboy> last parts on the way, will ship the full box of parts with the ADC oarts
Jun 01 16:14:11 <nerdboy> *parts even
Jun 01 16:14:23 <ds2> a oneline such as - "Broke arms, legs; In full body cast. No work this week" is fine.
Jun 01 16:15:00 <_av500_> Visaoni: means you did nothing this past week?
Jun 01 16:15:03 <Visaoni> sounds good nerdboy
Jun 01 16:15:35 <Visaoni> I suppose as nerdboy said there was some work looking at/finalizing parts
Jun 01 16:15:42 <nerdboy> no, we had to spec adc part and found TI eval board eventually...
Jun 01 16:16:14 <_av500_> and there was no work on BBB to be done?
Jun 01 16:16:41 <Visaoni> don't have the BBB yet
Jun 01 16:16:59 <nerdboy> *on the desk in the next room
Jun 01 16:17:14 <kiran4399> alexhiam: when will I get beaglebone blue?
Jun 01 16:17:27 <alexhiam> kiran4399: not before it exists ;)
Jun 01 16:17:51 <ds2> nerdboy: Is visaoni local to you?
Jun 01 16:18:06 <nerdboy> Visaoni: can you post a quickie paragraph on the new part/specs?
Jun 01 16:18:16 <nerdboy> "local" as in the same state
Jun 01 16:18:23 <kiran4399> alexhiam: haha lol!! so when will it come to existence?
Jun 01 16:18:29 * Visaoni actually forgot that ti board was this last week and not before
Jun 01 16:18:33 <alexhiam> kiran4399: no date yet
Jun 01 16:18:39 <nerdboy> not sure exactly how far, but I may have to show up with some "inducement" tools...
Jun 01 16:19:00 <Visaoni> 4 hours? something like that
Jun 01 16:19:25 <alexhiam> kiran4399, m_w, Abhishek_: can we take a few minutes after the meeting to sync up and make a solid plan for the coming weeks?
Jun 01 16:19:30 <ds2> nerdboy: ah.. okay. thought you were in teh same city/meeting in coffeeshops, etc :D
Jun 01 16:19:41 <nerdboy> maybe discuss the bandwidth/sampling stuff a little?
Jun 01 16:20:02 <m_w> alexhiam: ack
Jun 01 16:20:37 <nerdboy> takes about 15 hours to cross california the long way...
Jun 01 16:21:57 <kiran4399> alexhiam: yeah..sure...
Jun 01 16:22:03 <_av500_> ok
Jun 01 16:22:08 <_av500_> back to the meeting :)
Jun 01 16:22:19 <_av500_> thanks for the reports
Jun 01 16:22:29 <_av500_> as said, every tuesday, every week
Jun 01 16:22:53 <_av500_> HW for Visaoni is with nerdboy and is hopefully being shipped any minute
Jun 01 16:23:14 <_av500_> pony express please!
Jun 01 16:23:35 <_av500_> also as usualy, do not wait for the meeting to cry for help
Jun 01 16:23:53 <_av500_> if something is blocking you, say it any time
Jun 01 16:24:01 <ds2> _av500_: which list should it goto?
Jun 01 16:24:09 <_av500_> beagle-gsoc?
Jun 01 16:24:13 <_av500_> no?
Jun 01 16:24:34 <ds2> _av500_: wanted an official answer-seeing reports on themain list
Jun 01 16:25:07 <ds2> ZeekHuge: beagle-gsoc list is probally sufficent
Jun 01 16:25:22 <_av500_> you can CC beagle, put please send to beagle-gsco
Jun 01 16:25:27 <ZeekHuge> okay, so no mail ?
Jun 01 16:25:27 <_av500_> gsoc*
Jun 01 16:25:59 <ZeekHuge> just on the ml, right ?
Jun 01 16:26:06 <_av500_> I count that as a mail
Jun 01 16:26:14 <_av500_> ml = mailing list
Jun 01 16:26:20 <ZeekHuge> oh, okay.
Jun 01 16:26:49 <jic23> Keep ccing me directly if you like zeekhuge
Jun 01 16:27:03 <ZeekHuge> okay jic23 :)
Jun 01 16:27:43 <ds2> ZeekHuge: direct CC to me is fine too
Jun 01 16:28:13 <ZeekHuge> okay, will do.
Jun 01 16:29:28 <_av500_> ok
Jun 01 16:29:33 <_av500_> moving on
Jun 01 16:29:50 <_av500_> we had two volunteers for this weeks meeting
Jun 01 16:30:00 <_av500_> with a short standup report
Jun 01 16:30:18 <_av500_> pmezydlo and ?
Jun 01 16:30:44 * ZeekHuge want to bring it under notice that there is still no status on my HW ie ADC.
Jun 01 16:30:55 <m_w> the crickets?
Jun 01 16:31:06 <_av500_> ADC is in short supply this year
Jun 01 16:31:08 <_av500_> left and right
Jun 01 16:31:17 <henrix_> me
Jun 01 16:31:41 <_av500_> henrix_: can you start?
Jun 01 16:31:47 <henrix_> ok
Jun 01 16:31:55 <_av500_> you have the floor
Jun 01 16:31:59 <_av500_> ZeekHuge: noted
Jun 01 16:32:04 <henrix_> 1. project goal: Porting CTAG face2|4 Audio Card drivers to BB-X15
Jun 01 16:32:14 <henrix_> First I wanted to test the SPI and I2S interface, to avoid
Jun 01 16:32:14 <henrix_> mistakes with breakout / adapter board design (rma).
Jun 01 16:32:26 <henrix_> Unfortunatly there's no SPIDEV device tree for BB-X15 to run SPI
Jun 01 16:32:26 <henrix_> loopback test so I decided to create a device tree for the audio
Jun 01 16:32:26 <henrix_> card.
Jun 01 16:32:50 <henrix_> I did some research in the BB-X15 device tree (e.g. dra74x.dtsi,
Jun 01 16:32:51 <henrix_> dt-bindings, ...) to figure out dt offsets for McSPI, McASP, ...
Jun 01 16:33:09 <henrix_> Based on am57xx-beagle-x15-common.dtsi I realized that the master clock of McASP is differently configured compared to BBB/BBG.
Jun 01 16:33:27 <henrix_> To keep ASoC machine driver compatible with BBB/BBG I added an extra dt-binding (int; 0=BBB/BBG, 1=BB-X15) to tell ASoC machine driver which SBC is used.
Jun 01 16:33:43 <henrix_> Based on this parameter, the DAI master clock of McASP is configured diffently for BBB / BB-X15.
Jun 01 16:33:57 <henrix_> After setting up SD-Card (Debian), updating dtc and some bug fixes device tree could be succesfully loaded and compiled.
Jun 01 16:34:17 <henrix_> To test SPI and I2S interface I used an oscilloscope and detected changes on SPI and I2S interface when playing audio or setting up codec configurations.
Jun 01 16:34:36 <henrix_> Unfortunatly I couldn't connect the audio card or logic analyizer due to the very small expansion header of BB-X15 (breakout board not available).
Jun 01 16:34:50 <henrix_> So I continued with second project part...
Jun 01 16:34:59 <henrix_> 2. project goal: Create library to make use of C66x DSPs of AM5738
Jun 01 16:35:11 <henrix_> First I did some research in AM5728 DSP examples (DSPLIB, opencl, gstreamer example (TI multimedia training)).
Jun 01 16:35:25 <henrix_> To compile and run the examples I tried to set up Processor Linux SDK and SD-Card for BB-X15.
Jun 01 16:35:34 <henrix_> I had problems booting the SDK image.
Jun 01 16:35:44 <henrix_> After some help of wormo, I got a FTDI adapter for serial debug. I also got no serial debug messages.
Jun 01 16:35:56 <henrix_> To avoid mistakes with SD-Card creation script I set up a VM with Ubuntu 14.04 (I'm only using Arch Linux and Ubuntu 16.04).
Jun 01 16:36:09 <henrix_> That's my current state (VM is installing Linux SDK / CCSv6).
Jun 01 16:36:27 <henrix_> FINISH
Jun 01 16:36:33 * jkridner|work reports in to amragaey and av500
Jun 01 16:36:33 <_av500_> thanks
Jun 01 16:36:38 <nerdboy> no actual audio output test yet?
Jun 01 16:36:51 <henrix_> no, I couldn't connect the audio card
Jun 01 16:36:54 <rma_> we were requesting the connectors
Jun 01 16:37:05 <_av500_> rma_: have these been ordered?
Jun 01 16:37:26 <rma_> not yet, i requested if jason could order some, but we didnt get any response
Jun 01 16:37:32 <nerdboy> do you have speakers/amplifier with digital input?  or just analog?
Jun 01 16:37:35 <rma_> we'd need to get them asap
Jun 01 16:37:45 <_av500_> nerdboy: with I2S inout?
Jun 01 16:37:51 <_av500_> input*
Jun 01 16:38:17 <henrix_> we can't connect anything
Jun 01 16:38:19 <nerdboy> i2s has to go somewhere i assume...
Jun 01 16:38:34 <_av500_> jkridner: can the org cover for the connectors?
Jun 01 16:38:46 <rma_> we'd need 5* FX18-60S-0.8SV15   and 5*FX18-60P-0.8SV
Jun 01 16:38:59 <jkridner> yeah... payment shouldn't be a problem if you can give me an order URL.
Jun 01 16:39:25 <_av500_> great
Jun 01 16:39:26 <rma_> ok, shall we create a basked at mouser and redirect shipping to our address?
Jun 01 16:40:02 <_av500_> henrix_: thanks for the report
Jun 01 16:40:10 <henrix_> _av500_, welcome
Jun 01 16:40:14 <rma_> i will also still need to design/order pcbs which will take approx another 2 weeks, so henrix will work on the DSP part meanwhile
Jun 01 16:40:41 <_av500_> rma_: can you kludge in an existing PCB?
Jun 01 16:40:49 <_av500_> a few wires?
Jun 01 16:41:04 <rma_> will be very fragile with 0.8 width@0.4 pitch
Jun 01 16:41:05 <_av500_> CLK, DATA and FILE_NOT_FOUND?
Jun 01 16:41:11 <_av500_> ok
Jun 01 16:41:27 <rma_> these are high speed specialty plugs @ 8€ each
Jun 01 16:41:29 <_av500_> pmezydlo: you are up
Jun 01 16:41:39 <_av500_> rma_: ok, create that cart and send to jkridner
Jun 01 16:41:45 <pmezydlo> hello
Jun 01 16:41:48 <rma_> k
Jun 01 16:42:05 * nerdboy doesn't feel so bad about HW reqs now...
Jun 01 16:42:07 <pmezydlo> This week m_w reminded me that it's important that the code looks nice.
Jun 01 16:42:27 <jkridner> nerdboy: up to now, you've had the most arduous requests. ;-)
Jun 01 16:42:53 <nerdboy> it's a non-trivial device
Jun 01 16:43:27 <_av500_> sshh
Jun 01 16:43:36 <nerdboy> (and an important hole to fill in open source instrumentation)
Jun 01 16:43:39 <pmezydlo> I didn't think that these warnings would be so hard to correct, I almost felt like they were random.
Jun 01 16:44:02 <pmezydlo> some programmers are sensitive to coding style, that is, spaces or tabs, and vim or emacs.
Jun 01 16:44:10 <pmezydlo> alexhiam:^^
Jun 01 16:44:22 <alexhiam> pmezydlo: you know about checkpatch.pl?
Jun 01 16:44:35 <pmezydlo> yes, i know
Jun 01 16:44:47 <nerdboy> pmezydlo: i would mostly pay attention to compiler warnings first
Jun 01 16:44:59 <kiran4399> alexhiam: I am going to my parents house... I'll have to catch a train in about 20 minutes. can we have the discussion now?
Jun 01 16:45:10 <nerdboy> style issues last...
Jun 01 16:45:21 <_av500_> kiran4399: not on this channel
Jun 01 16:45:28 <pmezydlo> nerdboy: i already corrected them
Jun 01 16:45:32 <alexhiam> kiran4399: not during the meeting. When will you be online next?
Jun 01 16:45:41 <_av500_> sshhh!
Jun 01 16:46:00 <pmezydlo> _av500_: thanks :)
Jun 01 16:46:12 <nerdboy> don't forget /msg and /qry
Jun 01 16:46:28 <pmezydlo> soooo I solemnly announce that I chose vim.
Jun 01 16:46:49 <pmezydlo> I added a lot of plugins and it works very well.
Jun 01 16:46:58 <pmezydlo> And which environments do you use?
Jun 01 16:48:26 <pmezydlo> ping
Jun 01 16:48:43 <_av500_> pong
Jun 01 16:48:49 <bradfa> pmezydlo: just keep going explaining your progress
Jun 01 16:48:51 * nerdboy is somewhat agnostic
Jun 01 16:49:01 <m_w> pmezydlo: please talk about your project.
Jun 01 16:49:13 <pmezydlo> actually i don't have anything else to say. everything's fine. i am slowly starting to get to know how to write drivers.
Jun 01 16:49:29 <_av500_> thats good
Jun 01 16:49:48 <nerdboy> everything pushed so far?
Jun 01 16:50:10 <pmezydlo> there's no tutorials, so i have to base on someone's code
Jun 01 16:50:29 <rma_> jkridner: sent you the cart from mouser with address instructions, please ack, thx!
Jun 01 16:50:50 <nerdboy> pmezydlo: you have greg's kernel book?
Jun 01 16:51:01 <pmezydlo> well, i found a bug in master driver.
Jun 01 16:51:04 <pmezydlo> i have this book
Jun 01 16:51:09 <pmezydlo> it's great
Jun 01 16:51:43 * chanakya_vc also has it but has not read it completely 
Jun 01 16:51:59 <pmezydlo> The omap2_mcspi driver increments the base address (resources), when the driver is repeatedly installed, the address is not correct.
Jun 01 16:52:08 <nerdboy> http://lwn.net/Kernel/LDD3/ <= this one?
Jun 01 16:52:32 <pmezydlo> exactly
Jun 01 16:52:38 <m_w> pmezydlo: have you considered sending a patch for the master driver?
Jun 01 16:52:43 <pmezydlo> and I solved this problem in my driver by creating  copies of resources(memcpy).
Jun 01 16:53:18 <pmezydlo> yeah, I did. should i send it to linux-spi?
Jun 01 16:53:25 <m_w> yup
Jun 01 16:53:53 <nerdboy> http://www.kroah.com/lkn/ <= and this one?
Jun 01 16:54:19 <pmezydlo> nerdboy: nope
Jun 01 16:54:41 <nerdboy> can't have too many...
Jun 01 16:55:05 <chanakya_vc> nerdboy, Would you recommend reading both the books?
Jun 01 16:55:09 <m_w> pmezydlo: please be persistent with the patch this time, it may take a few revisions
Jun 01 16:55:28 <m_w> who reads reference books?
Jun 01 16:55:30 <pmezydlo> ok
Jun 01 16:55:38 <nerdboy> i use all the good references i can find...
Jun 01 16:55:58 <chanakya_vc> m_w, I do ; ) you don't?
Jun 01 16:56:08 <m_w> not from cover to cover
Jun 01 16:56:09 * nerdboy 's brain overflowed a couple decades ago
Jun 01 16:56:28 <chanakya_vc> Although Googling problems seems to be an easier approach
Jun 01 16:56:40 <m_w> that I look up what I need in the book
Jun 01 16:56:41 <nerdboy> using a reference and reading a book are two different things....
Jun 01 16:57:07 <_av500_> ok, 5 minutes before I turn back into a pumpkin
Jun 01 16:57:10 <pmezydlo> i haven't found much about platform device in this book
Jun 01 16:57:16 <_av500_> pmezydlo: thanks for the report
Jun 01 16:57:22 <_av500_> who is next week?
Jun 01 16:57:24 <nerdboy> if it's mostly all new to you then do read as much as you can...
Jun 01 16:57:25 <pmezydlo> no problem
Jun 01 16:57:29 <_av500_> I need two volunteers
Jun 01 16:58:20 <nerdboy> there's a reason both those books are gentoo packages under app-doc/
Jun 01 16:58:40 <ZeekHuge> ah .. me ?
Jun 01 16:58:49 <ZeekHuge> next week.
Jun 01 16:58:51 <_av500_> chanakya_vc: Visaoni ZeekHuge kiran4399 amragaey
Jun 01 16:59:04 <_av500_> ZeekHuge: ok, #1
Jun 01 16:59:05 <_av500_> who else?
Jun 01 16:59:09 <chanakya_vc> me
Jun 01 16:59:11 <amragaey> _av500_, I prefer to be the third week
Jun 01 16:59:13 <_av500_> ok
Jun 01 16:59:16 <_av500_> amragaey: fine
Jun 01 16:59:25 <_av500_> ZeekHuge: and chanakya_vc next week
Jun 01 16:59:40 <_av500_> thank you all
Jun 01 16:59:56 <_av500_> remember, reports tuesday :)
Jun 01 17:00:03 <ZeekHuge> okay. Thank you _av500_ :)
Jun 01 17:00:09 <chanakya_vc> Just to clarify _av500_ I just need to talk about what I have achieved and the problems right?
Jun 01 17:00:11 <amragaey> ok, thanks _av500_
Jun 01 17:00:13 <_av500_> nerdboy: ship that HW!
Jun 01 17:00:16 <_av500_> chanakya_vc: yes
Jun 01 17:00:24 <_av500_> chanakya_vc: its not formal
Jun 01 17:00:32 <_av500_> just for us to see what you are cooking
Jun 01 17:00:38 <chanakya_vc> Okay _av500_ .
Jun 01 17:00:41 <_av500_> and others to maybe ask a question
Jun 01 17:01:11 <chanakya_vc> Okay _av500_ Got it
Jun 01 17:01:24 <_av500_> ok, thanks again everybody
Jun 01 17:01:29 <chanakya_vc> meeting up?
Jun 01 17:01:37 <_av500_> clock says so
Jun 01 17:01:42 <_av500_> feel free to stay :)
Jun 01 17:01:47 <_av500_> but I must leave
Jun 01 17:01:51 <ZeekHuge> cool !
Jun 01 17:01:55 * _av500_ vanishes in a puff of smoke
Jun 01 17:02:17 <chanakya_vc> hey bradfa,mdp are you there?
Jun 01 17:02:39 <chanakya_vc> bradfa, Did you get a chance to go through my code?
Jun 01 17:02:41 <ZeekHuge> m_w, ds2, Abhishek_ as told by rcnee, i will wait till the 4.4.11-ti-r30 rolls out.
Jun 01 17:02:52 <henrix_> bye
Jun 01 17:03:00 <m_w> ZeekHuge: ack
Jun 01 17:03:00 <ZeekHuge> probably on Thursday
Jun 01 17:03:47 <chanakya_vc> ZeekHuge, Have you used Jekyll for your blog?
Jun 01 17:03:53 <bradfa> chanakya_vc: which code?
Jun 01 17:03:58 <chanakya_vc> You have got to try Hugo
Jun 01 17:04:20 <chanakya_vc> bradfa, I wrote the basic framework for SPI,pushed it on github
Jun 01 17:04:22 <ZeekHuge> nope, just coded in html and bit of css.
Jun 01 17:04:27 <bradfa> chanakya_vc: link please
Jun 01 17:04:51 <chanakya_vc> Wrote it in the mail.It's very basic
Jun 01 17:04:53 <chanakya_vc> Wait
Jun 01 17:05:07 <ZeekHuge> ans js, based on what gh-pages itself create.
Jun 01 17:05:15 <bradfa> chanakya_vc: ok, on your wip-on-spi branch?
Jun 01 17:05:26 <chanakya_vc> Yep
Jun 01 17:05:45 <chanakya_vc> I know not really a piece of art but it is a start :P
Jun 01 17:05:50 <chanakya_vc> bradfa, ^^
Jun 01 17:05:52 <bradfa> chanakya_vc: yes a start
Jun 01 17:06:03 <m_w> where is the miso?
Jun 01 17:06:13 <bradfa> m_w: it's a *start* :)
Jun 01 17:06:31 <chanakya_vc> m_w, Yes I did not add that because I did not know about the r31 register :P
Jun 01 17:06:42 <bradfa> chanakya_vc: you need to write a makefile for it and documentation on how to get it to actually run on the bbb
Jun 01 17:07:17 <bradfa> chanakya_vc: the one makefile example you gave me before is not the best example of a simple makefile
Jun 01 17:07:40 <chanakya_vc> bradfa, I want to first get the firmware to a presentable shape where in it is actually doing basic spi bitbanging.
Jun 01 17:09:32 <bradfa> chanakya_vc: ok
Jun 01 17:09:55 <m_w> what is the point of this --> _R30^=(0<<CLK);
Jun 01 17:10:10 <chanakya_vc> bradfa, Please excuse me for 15 minutes.Be back in that.My mother is calling me for some errand .I wish to discuss with you some stuff regarding the structure
Jun 01 17:10:18 <m_w> it does nothing
Jun 01 17:11:23 <chanakya_vc> m_w, It sets the clock to 0 first
Jun 01 17:11:33 <m_w> nope
Jun 01 17:12:04 <chanakya_vc> Sorry it will be a 1 there
Jun 01 17:12:13 <chanakya_vc> My mistake
Jun 01 17:12:17 <m_w> better
Jun 01 17:12:20 <chanakya_vc> m_w, ^^
Jun 01 17:12:26 <m_w> :)
Jun 01 17:12:48 <chanakya_vc> Idea is to set the clock to 0 before the data pin goes to 0
Jun 01 17:12:50 <chanakya_vc> m_w, ^^
Jun 01 17:13:11 <chanakya_vc> m_w, Otherwise is the logic correct?
Jun 01 17:13:32 <m_w> lets see
Jun 01 17:14:16 <m_w> yeah if you change it to _R30^=(1<<CLK);
Jun 01 17:15:00 <m_w> why is it while(1)?
Jun 01 17:15:23 <m_w> https://github.com/chanakya-vc/PRU-I2C_SPI_master/blob/wip_on_spi/pru0_spi.c#L19
Jun 01 17:16:28 <m_w> I think that the program needs some work
Jun 01 17:20:58 <amragaey> hi jkridner
Jun 01 17:21:15 <amragaey> jkridner, have you checked my email and pull request ?
Jun 01 17:24:43 <jkridner> amragaey: I'll do so now.
Jun 01 17:26:11 <amragaey> Okay, I have to go now.. Can we continue by mail please, jkridner ?
Jun 01 17:26:18 <jkridner> k
Jun 01 17:26:43 <amragaey> thanks :)
Jun 01 17:27:54 <chanakya_vc> m_w, Right now I just wanted to send a custom sequence of bytes and see what result the loop produces
Jun 01 17:29:12 <chanakya_vc> It won't be while(1) in the final program.The loop condition will be different.I will look in the example you gave
Jun 01 17:29:51 <chanakya_vc> Infact this is a doubt of mine bradfa m_w .
Jun 01 17:31:25 <bradfa> chanakya_vc: likely you'll end up making a state machine so that while(1) you have now will have a conditional to know that you've completed transacting all the bytes and then go to another state of waiting for linux to tell you what to do next
Jun 01 17:34:10 <chanakya_vc> Okay got you bradfa,I have a few doubts related to the algorithm:
Jun 01 17:35:33 <chanakya_vc> 1)When you are bitbanging,does the user type all the information all at once and then our driver would store it at a temporary loc and then according to the word size shift it to the shared mem?
Jun 01 17:36:54 <chanakya_vc> Or does the user only get to write the specific word size at one time.This is sent to the shared mem,then bitbanged.Only then the user is allowed to write the next word/information?
Jun 01 17:37:13 <bradfa> chanakya_vc: protocol drivers or spidev will effectively just call spi_async() and then it's up to the hardware layer driver to dole out the data to/from the hardware (PRU in this case) as needed, using DMA or other methods as needed
Jun 01 17:37:54 <chanakya_vc> So won't be my concern right?
Jun 01 17:37:56 <bradfa> chanakya_vc: since you will write both the PRU firmware and the linux hardware driver interface to said firmware, you can do it however you want, but you need to support sending 1 byte up to a very large number of bytes
Jun 01 17:37:59 <chanakya_vc> bradfa^^
Jun 01 17:38:52 <chanakya_vc> Okay,So I need to give the support for if the protocol driver wants to send 1 byte at one time or multiple bytes.Got it
Jun 01 17:38:57 <bradfa> chanakya_vc: yes
Jun 01 17:39:28 <bradfa> chanakya_vc: looking at how something like McSPI works both at a hardware level from the AM335X TRM and from the linux kernel driver for McSPI may be helpful to you
Jun 01 17:42:50 <bradfa> chanakya_vc: I'm not sure if having a similar FIFO system as McSPI is the best approach or not, but it may be a reasonably simple way to get started
Jun 01 17:43:31 <bradfa> chanakya_vc: once you have basics working of compiling and running simple pru code, it will likely be worth drawing up the state diagrams and planning out how the pru firwmare will work in that regard before coding a ton
Jun 01 17:44:57 <chanakya_vc> I have not had much exposure to state diagrams bradfa .
Jun 01 17:45:08 <chanakya_vc> But I will look into it
Jun 01 17:45:16 <chanakya_vc> I have seen it in many books
Jun 01 17:46:18 <chanakya_vc> bradfa,  Anyway,the next question is about the four modes.I think this can be achieved by a simple switch condition?
Jun 01 17:46:54 <chanakya_vc> bradfa, Also in SPI,as MOSI is transmitting, MISO is transmitting back right?
Jun 01 17:47:45 <bradfa> chanakya_vc: yes, it's full duplex
Jun 01 17:48:29 <bradfa> chanakya_vc: regarding the modes, you can switch or just if-then-else for each of cpha and cpol
Jun 01 17:49:14 <chanakya_vc> So I should not be concerned as to intrepret that data right?I mean all my firmware has to do is write back to the shared mem with each bit is receives?
Jun 01 17:49:34 <chanakya_vc> *it receives by the miso right?
Jun 01 17:50:28 <bradfa> chanakya_vc: yes, receive on MISO, transmit on MOSI and each of these will be sampled at the clock edge that corresponds to cpha
Jun 01 17:50:56 <chanakya_vc> bradfa, Shouldn't be diffcult.
Jun 01 17:51:24 <chanakya_vc> bradfa, I aim to implement this full duplex transmission by the next meeting
Jun 01 17:51:59 <bradfa> chanakya_vc: ok
Jun 01 17:52:24 <bradfa> chanakya_vc: if you want to try your hand at drawing state charts, have a look at the "dia" software, I've not used it extensively but it should fit your needs
Jun 01 17:52:41 <chanakya_vc> It's just that,I am thinking and writing code according to what I think is the best.But I am not sure whether that is the most optimum way or the way it is done nowadays
Jun 01 17:52:43 <bradfa> if you're more comfortable writing a text doc and processing it into a pretty chart, have a look at the "dot" language
Jun 01 17:52:45 <chanakya_vc> bradfa, ^^
Jun 01 17:53:03 <bradfa> chanakya_vc: written code, so long as it's readable, is better than no code ;)
Jun 01 17:53:27 <bradfa> chanakya_vc: in your comments, don't say what you are doing, say why you are doing things
Jun 01 17:54:30 <chanakya_vc> bradfa, I am kind of worried about the algorithm that I come up with.The speed issue is there.
Jun 01 17:54:36 <chanakya_vc> bradfa, Okay
Jun 01 17:56:36 <bradfa> chanakya_vc: if speed is an issue, we can look at making optimizations, get things working first
Jun 01 17:57:10 <chanakya_vc> Okay.I will write the code first.
Jun 01 17:59:02 <chanakya_vc> bradfa, I will mail some sort of a pseudo code logic for how I think the entire framework will  work.
Jun 01 17:59:02 <bradfa> chanakya_vc: your code relies on the pru software support package?
Jun 01 17:59:25 <chanakya_vc> If we go the RPMsg way it will
Jun 01 17:59:37 <bradfa> chanakya_vc: ok
Jun 01 17:59:40 <chanakya_vc> bradfa, Which I am inclined towards
Jun 01 17:59:54 <chanakya_vc> But that can be handeled later
Jun 01 18:00:13 <chanakya_vc> bradfa, Give me two days for it.
Jun 01 18:00:38 <bradfa> chanakya_vc: ok
Jun 01 18:01:00 <chanakya_vc> bradfa, Okay now to sigrok,if you have the time?
Jun 01 18:01:21 <bradfa> chanakya_vc: ok
Jun 01 18:01:48 <chanakya_vc> You had asked me for log of some commands?
Jun 01 18:01:51 <chanakya_vc> bradfa, ^
Jun 01 18:02:29 <bradfa> chanakya_vc: sigrok-cli --scan
Jun 01 18:02:37 <bradfa> it should return your saleae device
Jun 01 18:02:53 <bradfa> if it only returns nothing or a "demo" device, you likely need to install the fx2lafw firwmares
Jun 01 18:04:33 <chanakya_vc> bradfa, http://pastebin.com/cKmepYct
Jun 01 18:05:09 <chanakya_vc> I guess the firmware is missing
Jun 01 18:13:09 <bradfa> chanakya_vc: try "sigrok-cli --scan -l 5"
Jun 01 18:13:14 <bradfa> it'll output a ton of debug data
Jun 01 18:21:53 <bradfa> chanakya_vc: sorry, have to run now, but if you need sigrok help, the people in #sigrok are pretty helpful usually
Jun 01 18:24:13 <chanakya_vc> Okay bradfa,I will ask you tomorrow if I am unable to solve it bye : )
Jun 01 18:24:35 <chanakya_vc> Perhaps mdp could help me out today or tomorrow
Jun 01 18:26:36 <bradfa> chanakya_vc: you may want to look at the PPA for sigrok: https://launchpad.net/~daniel-elstner/+archive/ubuntu/sigrok?field.series_filter=trusty
Jun 01 18:26:53 <bradfa> that includes the fx2lafw firmwares
Jun 01 18:28:49 <alexhiam> so when I cross compile Linux on my x86_64 machine and install on the bone from debs, the build tools in /usr/src/linux-headers-blahblah/scripts are compiled for x86_64. So if I want to build a module on the bone running that kernel, I have to rebuild the scripts locally. Is there anyway to get those compiled for ARM in the debs (besides building on an ARM)?
Jun 01 18:43:41 <Abhishek_> chanakya_vc: Try running sigrok-cli in sudo and if it works, you need to add an udev rule about the USB device
Jun 01 19:08:59 <alexhiam> hey jic23b, I'm looking to write a driver for the Panasonic Grid-EYE (http://industrial.panasonic.com/ww/products/sensors/built-in-sensors/grid-eye) but not sure where it belongs... kinda seems too simple for v4l2, but maybe too complex for iio..?
Jun 01 19:09:55 <alexhiam> and by complex I'm referring to the fact that there's 64 contiguous samples, where you need to know the start and end
Jun 01 19:13:13 <alexhiam> but maybe that's not a problem in iio...
Jun 01 19:14:01 <alexhiam> a v4l2 driver would be cool, but you'd lose the actual temperature values
Jun 01 19:58:27 <jic23> Alexhiam, cool sensor. Certainly could support it in IIO but it is in the gray region between us an v4l. We bounced back some fingerprint sensors a while ago on basis they were producing an image...
Jun 01 19:58:52 <jic23> Higher res I think but not as high as you might think.
Jun 01 20:00:27 <jic23> However we do take gesture sensors which are typically 3x3 pixels and thermopiles which are basically single pixel versions of that sensor.  I'll have a read of the data sheet.
Jun 01 21:34:07 <jic23> Gut feeling is v4l as it is really an image sensor.
Jun 01 21:43:42 <jic23> Gut feeling is v4l but maybe post on relevant list before you put in much work on it to check they are happy with it.
Jun 01 21:47:24 <alexhiam> yeah, v4l makes sense, though the temp->image mapping is so application specific
Jun 01 21:48:11 <alexhiam> temp->color space that is
Jun 01 23:14:09 * Abhishek_ wonders what it'd be for FLIR sensors
Jun 01 23:19:39 <Wormo> I think it would have to be v4l for FLIR sensors, 80x60 and 160x120 are a lot more data than 8x8
**** ENDING LOGGING AT Thu Jun 02 02:59:58 2016