Am 24.01.2013 um 11:53 schrieb Bas Laarhoven: > On 24-1-2013 11:14, Michael Haberler wrote: >> Am 24.01.2013 um 09:48 schrieb Bas Laarhoven: >> >>> On 23-1-2013 23:25, Charles Steinkuehler wrote: >>>> On 1/23/2013 1:33 PM, Bas Laarhoven wrote: >>>>> On 23-1-2013 19:52, Michael Haberler wrote: >>>>>> Am 23.01.2013 um 16:17 schrieb Bas Laarhoven: >>>>>> >>>>>>> Since you have experience with patching xenomai on top of a kernel, is >>>>>>> there any chance applying the patches on the 3.2.34 kernel? >>>>>>> You can download that kernel from >>>>>>> https://github.com/modmaker/linux/tree/linux-ti33x-psp-3.2.34-r18a+gitr720e07b4c1f687b61b147b31c698cb6816d72f01. >>>>>>> The link might not work directly, but it contains all the relevant >>>>>>> information to find the branch in my kernel tree. >>>>>>> >>>>>>> The advantage of this kernel is that it contains the relevant drivers >>>>>>> for GPIO, PWM, ADC, PRUSS, etc. It also contains the EEPROM based >>>>>>> configuration decoder that I wrote. It's used by my BeBoPr board to >>>>>>> automatically configure the I/O, so one doesn't need to load drivers, >>>>>>> set the multiplexers and so on (Charles: This might save you a lot of >>>>>>> work!). >>>>>> I am now looking into it, and I am not so sure about the last paragraph. >>>>> ??? Huh, I'm not sure if I understand what you're saying here. Do you >>>>> think the TI branches are better., is that what you're saying? Then I >>>>> suggest that you read back the IRC logs on #beagle over the last year. >>>> From my perspective, the fancy BeagleBone specific kernel bits that Bas >>>> is wanting are not particularly necessary for LinuxCNC. >>> Charles, >>> The capes have an EEPROM containing configuration information that is used >>> to configure the BeagleBone's I/O when the kernel boots. If you want (or >>> need) to do that yourself, that's of course a choice you are free to make. >>> It's indeed fancy, and user friendly : ) >>>> Running under Xenomai, we can't call into the Linux kernel to update >>>> anything without a severe latency hit, so we'll have to talk to the raw >>>> hardware anyway. It's easy enough to talk to the PRU directly since >>>> it's unused by Linux, but some of the other hardware (like the ADC and >>>> PWM) is a bit trickier. I'm actually hoping I don't have to *disable* >>>> the Linux drivers for the AM335x hardware to keep the kernel from >>>> stepping on registers while we're talking directly to the hardware via >>>> Xenomai/userspace. >>>> >>> Ah, it wasn't clear to me that you were going to do all the low level stuff >>> yourself. >>> Is this necessary? Can't you use the standard drivers for the not time >>> critical parts? >>> If not, I hope you're an expert and have lot's of time to spend ; ) >> >> Bas, >> >> this is getting a bit lop-sided. >> >> I concur with Charles that you havent come forward with a good argument to >> change horses at this point for _LinuxCNC_, given the new horse pretty much >> rides as fast as the old one. >> >> If you need that kernel with Xenomai for your de-facto proprietary >> application which nobody over here can gain anything from, I suggest to go >> about it as follows: >> >> - take your tree and branch at commit >> d3f8f7cc6d6ee6f50d3cfee335ad0994ad910d1c , the 3.2 mergepoint, which will >> make the 3.2-core ipipe patch apply cleanly >> - follow these instructions from line 34: >> http://git.mah.priv.at/gitweb/linuxcnc-kernel.git/blob/c7422c10a84e122ebb561d98e750b043390fd527:/linuxcnc/README.beaglebone >> - when reaching line 55, try a build and see if Xenomai works properly >> - if yes, work your way forward through the 2000 or so mystery commits while >> still have a running kernel >> >> let us know how it goes and publish results, it's always good to have more >> than one option >> >> - Michael > > Charles, Michael, > > Indeed, it makes no sense to continue this discussion 'en public'. > > I remember when we had first contact that I stated that if someone else took > care of the kernel part I could work on the (open source) PRUSS code. > Now it's getting clear to me that both of you don't want to go this way and > have already made your mind up about which kernel to use etc. > > I'll stop wasting your (and my) time,
c'mon, Bas - a son of the great Dutch trading nation skimping on the sales job - that's unheard of sell us on the upside and we'll vanish in the sunset hand in hand -Michael ps: is there something to the rumor that 'failure to conclude a deal' is a reportable offense at Dutch embassies ;-? > > -- Bas > > >> >>> -- Bas >>> >> >> ------------------------------------------------------------------------------ >> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, >> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current >> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft >> MVPs and experts. ON SALE this month only -- learn more at: >> http://p.sf.net/sfu/learnnow-d2d >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
