**** BEGIN LOGGING AT Sat Jul 09 02:59:58 2016 Jul 09 13:51:58 alexhiam: there? Jul 09 14:48:56 alexhiam, There? Jul 09 16:48:10 hi jkridner , I got to the half of state diagram Jul 09 17:00:56 moin Jul 09 17:01:53 jkridner: fixed this up just for you... https://github.com/VCTLabs/RTIMULib2 Jul 09 18:21:56 we must be running low on gophers... Jul 09 18:22:32 houdini just ran across the driveway dragging a pigeon Jul 09 22:10:33 ds2: Wormo Abhishek_ : zeekhuge.me/post/some_shots/ Jul 09 22:10:36 Hi ! Jul 09 22:10:39 you there ? Jul 09 22:11:52 better link : https://zeekhuge.github.io/post/some_shots/ Jul 09 22:22:21 Cool. Jul 09 22:22:41 Hi Abhishek_ ! Jul 09 22:23:15 So as reported earlier, my bbb pins were fried up. Jul 09 22:23:25 So I got this other loader bbb Jul 09 22:23:34 and its usb port was broken Jul 09 22:24:04 so I have used a 2A brick and 5V regulator to be its power source Jul 09 22:24:49 And ... theres not much I could get at local shops here ( they mostly deal in full kits like arduino boards and all, not in parts ) Jul 09 22:25:06 DId you try CrazyPi? Jul 09 22:25:07 So this is what i could make out of all of them Jul 09 22:26:20 ahh .. I wanted to start it as soon as i could. though it took me sometime to find stuff and then make all this out of it. Jul 09 22:28:01 You stuck with anything? Jul 09 22:28:19 confused .. basically Jul 09 22:28:52 So I was reading some IIO drivers and the dummy driver and ... Jul 09 22:29:02 I am unable to make the next step .. Jul 09 22:29:41 I mean ... I am able to understand the driver .... but ... I dont what the next step I should take. Jul 09 22:30:15 So ahh .. well I thought that I should start with the probe ... Jul 09 22:30:50 the device drivers get porbed by the bus, on getting a matching device name Jul 09 22:31:01 and then they check the id Jul 09 22:31:06 of the device Jul 09 22:31:44 so for my board that id is to be through i2c bus, as there is an EEPROM on the board Jul 09 22:32:24 but the board's documentation says nothing about that, so I guess its actually blank and we can write a device id there. Jul 09 22:32:52 So i got into hardware, to the adc ready to be used ... Jul 09 22:33:12 and had to do all this, in those pics, along ... Jul 09 22:33:38 Abhishek_: btw, did you notice ? I have almost completed the firmware :D Jul 09 22:34:10 and yeah .. what about the RPmsg related issues I mentioned in the report ? Jul 09 22:35:07 and yeah ... some more things were confusing me earlier.... Jul 09 22:35:53 that we already are getting probed once ... when the fw is loaded onto the pru Jul 09 22:36:40 but that probe was for the rpmsg-device (aka rpmsg-channel) Jul 09 22:37:58 thus I realized that as the project will progress, we will have to take the virtio_rpmsg_bus driver, and modify it. that is because the rpmsg-channel approach that we use, is like a device on the virtio bus Jul 09 22:38:53 What kind of modifications? Jul 09 22:39:01 So later, when we will be separating out the pru_parallel_bus, we dont want it to be implemented as a device, but as a bus itself. Jul 09 22:40:35 I am not sure of that modification yet..... But sure that the rpmsg-channel that we are using in a our driver as of now, is like a virtual device on virtio_rpmsg_bus and we dont want that. Jul 09 22:41:08 Though we can implement it that way too ... but it will just create extra overheads Jul 09 22:44:26 oh .. and about the ADC's power supply, I have used a variable voltage regulator... to start from the lowest voltage it can work on .. Jul 09 22:44:56 and I will probably be starting with 2.8 Jul 09 22:45:03 2.8V Jul 09 22:46:17 I will be testing the clock on Monday ( the scope is in college ) till then, I need to do work on the driver side. Jul 09 23:30:54 ZeekHuge: you there? Jul 09 23:40:20 https://www.kernel.org/doc/htmldocs/iio/index.html **** ENDING LOGGING AT Sun Jul 10 02:59:58 2016