tag:blogger.com,1999:blog-8201318254944513910.post7508327723957765055..comments2024-02-14T09:15:01.200-08:00Comments on Blogging the Monkey: Building DCE firmwareRobhttp://www.blogger.com/profile/00061851853178706566noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-8201318254944513910.post-8838053133430056282015-10-24T22:57:15.406-07:002015-10-24T22:57:15.406-07:00This comment has been removed by a blog administrator.ahmadsamidi3https://www.blogger.com/profile/04660195217446989475noreply@blogger.comtag:blogger.com,1999:blog-8201318254944513910.post-32953174581731660222012-08-04T10:33:32.632-07:002012-08-04T10:33:32.632-07:00Coming about 6 months late, but do you still have ...Coming about 6 months late, but do you still have a copy of HDVICP2? We currently have a bunch of very hard working folk trying to port a working version of ICS on the Nook Tablet, based on the 3.x kernel, and we're stuck because of a timer conflict between ducati and the backlight. At this point, the only hope is to rebuild ducati with timer 10 as the watchdog, but to do that we need HDVICP2. Promise no sinister or evil repurposing, you can check their work out here. http://forum.xda-developers.com/showthread.php?t=1480586Shawn Crahanhttps://www.blogger.com/profile/00420581673076022317noreply@blogger.comtag:blogger.com,1999:blog-8201318254944513910.post-62216477921839218842012-02-22T09:16:07.092-08:002012-02-22T09:16:07.092-08:00Yep good guestion. Where is it possible to find HD...Yep good guestion. Where is it possible to find HDVICP2 ?<br /><br />Regards<br /><br />ttyttypubhttps://www.blogger.com/profile/09698699484638189958noreply@blogger.comtag:blogger.com,1999:blog-8201318254944513910.post-44748536314309196002011-12-22T08:24:09.773-08:002011-12-22T08:24:09.773-08:00Hi,
The link for HDVICP2 is down.
Any idea how to...Hi, <br />The link for HDVICP2 is down.<br />Any idea how to retrieve codec ?<br />Regards,<br />Olivier.Unknownhttps://www.blogger.com/profile/13464396479560103547noreply@blogger.comtag:blogger.com,1999:blog-8201318254944513910.post-91170800305519317562011-08-17T12:56:53.455-07:002011-08-17T12:56:53.455-07:00oh, actually, I think this could also be solved by...oh, actually, I think this could also be solved by adding this patch on linux kernel side:<br /><br />https://github.com/robclark/kernel-omap4/commit/29ee955ea139c10afc2dd97420c21878dd471028<br /><br />ok, probably snafu was my fault.. I think maybe originally that patch was on ti-omap4-drm and then got moved to ti-omap4-drm-syslink..Robhttps://www.blogger.com/profile/00061851853178706566noreply@blogger.comtag:blogger.com,1999:blog-8201318254944513910.post-17577875918615493012011-08-17T12:40:55.511-07:002011-08-17T12:40:55.511-07:00ahh, good catch. Did you just revert to the previ...ahh, good catch. Did you just revert to the previous commit for userspace syslink?<br /><br />I guess the wiki page should be updated ;-)Robhttps://www.blogger.com/profile/00061851853178706566noreply@blogger.comtag:blogger.com,1999:blog-8201318254944513910.post-76472863274906245962011-08-14T19:42:04.279-07:002011-08-14T19:42:04.279-07:00Hi,
I answer myself :
this syslink commit http:/...Hi,<br /><br />I answer myself :<br />this syslink commit http://git.omapzoom.org/?p=platform/hardware/ti/syslink.git;a=commit;h=bbbedc6f626b016a78bf51bd95dc75714986cfc6 broke the compatibility with your kernel (at all existing kernels I fear) because RPROC_IOCSTART and RPROC_IOCSTOP are no longer the same in the kernel (arch/arm/plat-omap/include/plat/remoteproc.h) and for syslink (syslink/api/include/ProcMgrDrvDefs.h)...<br /><br />RegardsAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8201318254944513910.post-50515706010022008152011-08-14T13:46:20.394-07:002011-08-14T13:46:20.394-07:00Hi,
First of all, I would like to thank you for a...Hi,<br /><br />First of all, I would like to thank you for all your work : You help to open the big black block on the ducati side...<br /><br />I followed very carefully your tutorial. <br />I have the following versions :<br />Ducati side :<br />-TMS470/ARM Code Generation Tools (CGT) - 4.6.1<br />-XDC tools - 3.20.07.86<br />-BIOS (the RTOS) - 6.31.03.25<br />-Codec Engine (CE) - 3.20.00.16<br />-Framework Component (FC) - 3.20.00.22<br />-XDAIS - 7.20.00.07<br />-HDVICP2 API and HDVICP2_CODECS - 1.00.000<br />-bios-syslink - commit-id 48e98007e21e311c126f89ff51616bf6d7067b9d <br /><br />A9 side :<br />- kernel 2.6.38 form you github account - drm branch commit id 731fe43cb2c0996c6593bdd92df5fe9816bc5deb <br />config file : I tried both config.common.ubuntu and omap4_defconfig<br />- syslink 2 from omapzoom commit id dcf86d4baef4ab86addf615c865a7217979d2f82<br />- tiler/memmgr 2 from omapzoom commit id a6dda467f9689cb8c4e2c252f53524afd07c2392<br />- libdce from you github account commit id b253492309bbeb65a82fea095e053d3774d6244c<br /><br />Unfortunately, syslink_daemon returns these errors : http://pastebin.pandaboard.org/index.php/view/10494108<br />I noticed my dmsg looks like the one posted by another user here : http://groups.google.com/group/pandaboard/browse_thread/thread/5301d877ca1b0965/62ecec93fc28a3c4<br /><br />I fear there is still a version issue between the different components (maybe a recent commit in syslink or memmgr broke the compatibility ?).<br /><br />I also tried to work with an old libdce (the one for kernel 2.6.35 L24.11). <br />With this one syslink_daemon works fine but when I try to decode (dcetest and gst-ducati behave the same), I always get some extendedErrors=00000401...<br /><br />I you have any clue I would really be very grateful ...<br /><br />RegardsAnonymousnoreply@blogger.com