[AppleTV] Compiling crystalhd-for-osx Lib/Kext - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Mac OS X (https://forum.kodi.tv/forumdisplay.php?fid=56) +---- Thread: [AppleTV] Compiling crystalhd-for-osx Lib/Kext (/showthread.php?tid=66174) |
- rpineau - 2010-01-14 SO I recompiled the lspci kernel extension as well as the lspci tools (2.9) and lspci does see the BCM70012. So this is a good sign : 12:00.0 Multimedia controller: Broadcom Corporation BCM70012 Video Decoder [Crystal HD] (rev 01) XBMC still crash the box and here is the relevant part of the report to be sent after reboot : Code: Wed Jan 13 20:38:06 2010 in the xbmc log : Code: 21:39:11 T:2691036416 M:9397776384 DEBUG: SECTION:LoadDLL(libcrystalhd.dylib) So the lib is properly loaded. Let me know if you need more debugging. I could also recompiled the kernel extension in 64 bits mode as a test. The machine has 10GB or RAM .. in case this could be relevant to the fact that the kernel tries to get a physical segment address that is beyond the 32 bits address space. R - tegalus - 2010-01-14 Bobby Blixberg Wrote:With current SVN r26711 it has become worse. I'm seeing the same increased stuttering the current SVN. Thanks - IG82 - 2010-01-14 I have installed my card into my Mini but don't think it is being detected properly. I have installed the drivers and the kext is loading successfully but no joy in r26715. My xbmc log is stating that the device hasn't been found so the library is unloaded. sudo dmesg is OSX returns no mention of the BCM70012 device. Is there anything else I can do/check? I have tried reseating the card to ensure its not an installation error. Thanks Ian edit - OSX 10.4.11 btw - davilla - 2010-01-14 rpineau Wrote:SO I recompiled the lspci kernel extension as well as the lspci tools (2.9) and lspci does see the BCM70012. So this is a good sign : Very odd, the kext driver explicitly requests physical DMA memory to be below the 4GB boundary. Someone is not paying attention I will look at this under 10.6 this weekend. - rpineau - 2010-01-14 davilla Wrote:Very odd, the kext driver explicitly requests physical DMA memory to be below the 4GB boundary. Someone is not paying attention I will look at this under 10.6 this weekend. Ok, Thanks. In the mean time I recompiled the kext in 64 bits (a few changes were needed but nothing drastic) and I'll try with this sometimes tomorrow. R. - rpineau - 2010-01-16 So with my 64 bits version of the kernel extension, xbmc no longer crash and I can select the crystal HD as the video playback render option. If you want my patches for the 64 bits code let me know. R. - davilla - 2010-01-16 rpineau Wrote:So with my 64 bits version of the kernel extension, xbmc no longer crash and I can select the crystal HD as the video playback render option. sure, email to davilla [at] xbmc [dot] org, thanks. - rpineau - 2010-01-16 Well , I might have speak to soon. I still get the same error from time to time. Even if the kext is now said to be 64 bits : Code: BroadcomCrystalHD: The error still show an issue with 32 bit addressing : Code: panic(cpu 0 caller 0x55648d): "getPhysicalSegment() out of 32b range 0x15dfc6000, len 0x1000, class IOBufferMemoryDescriptor"@/SourceCache/xnu/xnu-1486.2.11/iokit/Kernel/IOMemoryDescriptor.cpp:1597 The rest of the stack trace is similar to the one I posted before. So it looks like there is still an issue and as my Mac Pro is a 2006 model I "can't" run the kernel in pure 64 bits and that's probably part of the problem as at some point there are 32 bits calls being done to the kernel. I'll send you a tgz of the xcode project as I had to tweak it to build 32 and 64 bits in the same kext so that you can see what I did. Look for the #ifndef __LP64__ in the code (in crystalhd_misc.c and linux_compatible.c). So it looks like there is still a need to fix the 32 bit issue to make sure the kext request a DMA buffer below 4GB. R. |