Kodi Community Forum

Full Version: [AppleTV] CrystalHD Driver for XBMC Launcher
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
anybody knows where to report this bug?
Honestly, I can't figure out what you're talking about. Are you sure you have the right thread?
fixed in trunk
davilla Wrote:fixed in trunk

you D man.
I guess we have to still remove the Wireless Card on the ATV1? Is there any way to have both on ATV1 ?

I need to remove the card.. whats the best 'tutorial' to see how I can do that?

Also, which card is it that comes out? I am wondering if I can use it in a laptop?
These are the steps I followed

Tools needed
Torx T5
Needle Nose Pliers (for removing nylon post from WAN card)
Tape (to tape down antenna leads)

Disassemble
http://www.bluefish.net.nz/2010/02/apple...-card.html

Install CrystalHD Drivers
http://forum.xbmc.org/showthread.php?tid=69321
defaults write com.teamxbmc.xbmclauncher XBMCAdditionalDownloadPlistURLs -array-add http://crystalhd.sartori.at/files/crystalhd.plist

I hope this helps!!
andy204 Wrote:This is the easiest way to install the CrystalHD driver onto your AppleTV!

To make this easy install available log into your AppleTV

and enter:
Code:
defaults write com.teamxbmc.xbmclauncher XBMCAdditionalDownloadPlistURLs -array-add http://crystalhd.sartori.at/files/crystalhd.plist

This will add a new download source to your "Downloads" section in Launcher.

Current revision: r174 (Build Date: 20101027)

If you have Problems with a new build, you can enable the last working release CrystalHD r156 (20100826):

Code:
defaults write com.teamxbmc.xbmclauncher XBMCAdditionalDownloadPlistURLs -array-add http://crystalhd.sartori.at/devel/crystalhd.plist

--

Wollte mich nur bedanken… hier hat's geklappt!! Big GrinSmile
bitte Smile
I don't recommend anyone the r174, all versions after r156 or 3.6.0 tend to work OK in unix but are not very good with OSX

In particular if you have a 70012 card you should also use dharma beta 2
with a 70015 instead 10.1 is fine

All based on my personal experience having tried both cards
I have ordered the 70015 card from Logic Supply. Specifically, this card:

http://www.logicsupply.com/products/bcm970015

I have followed the instructions online and have swapped out the wireless card and replaced with with the new card but it doesn't seem the system is seeing the card.

System Info:

Platform - AppleTV
OS - 3.0.2
Launcher version - 3.2.5
Install Method - via Launcher
SVN - 10.1 Git:e9e9099 - Compiled Mar 9 2011

Here are the logs:

xbmc.log - http://pastebin.com/gXUxwGay
console log - http://pastebin.com/ajZBjWd4
No crashreporter log exists

I have done a fresh install of Dharma 10.1, but the menu choice to allow for hardware acceleration is not present in the Video settings.

I have tried the terminal commands listed earlier in this thread such as:

sudo dmesg|grep crystalhd

and

sudo dmesg|grep BroadcomCrystalHD

but nothing is reported back in Terminal.

If I try to play a 1080p video, it does play back better than a stock ATV but it is still a bit choppy at times.

I have let the video play for a few minutes and then tried the commands again but still nothing gets reported back via Terminal.

Not sure what else I can try at this point and am open to any suggestions.

Thanks!
You need to install the driver (r156 adviced) from launcher and then reboot
interceptor121 Wrote:You need to install the driver (r156 adviced) from launcher and then reboot

Ah, I thought the listing in Launcher was for a full version of XBMC, not just a driver. In your posting above, where you stated that "with a 70015 instead 10.1 is fine", I incorrectly assumed that meant that 10.1 included the driver. That is what I get for assuming. Blush

So not to be redundant, but rather to make sure, I need to:

1) Update Launcher via Terminal to add the r156 download option (right now, I only have r174 as an option currently)

2) Install the r156 driver via Launcher

3) Boot into XBMC and make sure the hardware acceleration is an option and turned on

4) Double-check via Terminal that the card is being seen

Thanks again!
Probably not proper forum etiquette to answer my own posting but I did the outlined steps in my previous post following intercepter121's recommendation to use the r156 driver and everything is working great. Now on to install the two remaining 70015 cards in my two other ATV boxes.

Thanks to the devs and the everyone's postings that has made my ATV with XBMC an even more awesome device!
Hi,
i installed the actual nightly pre-11.0. can add the crystal hd driver by installing adon/ Zip? Because XBMC does not show the Crystal Card in the playback options...

Thanks!
I recently resurrected my Gen 1 AppleTV (with V1.0 software) and installed the 'old layout' BCM70012 I bought off ebay from China waaayy back when.

I've been trying to understand the R156 .vs. R174 OSX driver 'controversy', digging back through postings here, on the crystalhd-development mailing list, and looking at the various commits in the crystalhd-for-osx SVN repository.

I think I found something. Let's review...

R151 'reduce number of DMA buffers'
R157 'Tag the 3.6.0 release'

Then: R159 'sync to git tree' where a LOT of stuff changed (BCM70015 support comes in??)

AFTER this, there was a BCM70012 specific fix that went in (twice)
R161 'pause/resume was disconnected from bcm70012 cards'
R172 'sync osx to linux regarding bcm70012 pause/resume values'

Basically, r161 and r172 were changes TRIGGERED BY R151 - some other limits needed to be adjusted as a result of the lowering of the number of DMA buffers.

So to summarize,
R156 is pre-R159 bulk changes, but has bug re: BCM70012 pause/resume.
R174 is post-R159 bulk changes, but has fix for BCM70012 pause/resume.

I assume everyone knows where this is leading...

For us BCM70012 owners, a R156 era OSX driver (ie without the R159 bulk changes) WITH the fix for BCM70012 pause/resume might be, uh, interesting???

Anybody got a setup that would allow them to build such a creature? (I don't)


Notes: Using R161 diff as a model, I come up with -

ref: crystalhd/darwin_lib/libcrystalhd/libcrystalhd_if.cpp

Code:
- if(pStatus->ReadyListCount > 10 && !Ctx->hw_paused && !Ctx->fw_cmd_issued) {
+ if(pStatus->ReadyListCount > 7 && !Ctx->hw_paused && !Ctx->fw_cmd_issued) {

- else if (pStatus->ReadyListCount  < 6 && Ctx->hw_paused && !Ctx->fw_cmd_issued) {
+ else if (pStatus->ReadyListCount < 3 && Ctx->hw_paused && !Ctx->fw_cmd_issued) {
FYI: the '7' and '3' are what r161 effectively did; r172 on OSX yields '6' and '3'

PS: the same basic changes are applicable to r156 linux_lib/libcrystalhd/libcrystalhd_if.cpp
-- however -- someone ought to review inconsistencies in "enum _crystalhd_ldil_globals" in
linux_lib/libcrystalhd/libcrystalhd_priv.h .vs. darwin_lib/libcrystalhd/libcrystalhd_priv.h
(Are the BC_RX_LIST_CNT dependant -calcs- *supposed* to be differant on OSX vs Linux???)
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30