Reviving an old topic...

[compugeek617]

Well, Trikx and I didn't have to go to work today and we sat around and got all the 2.5 hacks working smoothly here (thanks, Trikx, for finally sharing a working 2.5 image with the forum).

Now that 2.5 is pretty well conquered (we have Bash, fixup, working great now and can do anything else we want), there are two immediate hacks that come to mind, and have been discussed several times on the forums here (and some other cool things, like BubbaJ's all local channels effort). First is the DTivo ExtractStream puzzle (why does nobody seem to be able to ExtractStream properly from DTivo boxes) . I have had nothing but bad luck with ExtractStream, even on my SA box - so I haven't even been able to extract "dirty" video streams (no I don't mean channel 596) from my DTivo yet. Then there's the emulation puzzle (which, since we don't want to discuss emulation issues per se here, can be rephrased as the "how do I get two serial ports on my DTivo").

I am personally somewhat interested in the second - mostly for cool factor. There are a lot of useful things you could do if you had a second serial port on a DTivo, including experimenting with running certain applications that require such a setup. There was a proposal by BubbaJ that you could get around this if the built in card slot was mapped to ttySx (is it? I don't know if this path was ever fully explored).

I did a bit of experimenting today with the IR port, trying to grab access to that port for bash. It has been mentioned that this port is split and also used underneath the hood to receive IR data - this is bad, since it means even if we were able to grab that port the remote would probably cease to work == mostly useless DTivo. It seems pretty clear that the IR port is probably not the way to go though it would still be nice to understand exactly how its being used (is MyWorld talking to ttyS0 directly, etc.).

I just found a great resource, the Linux Serial HOWTO which discusses a lot of useful tools that may or may not be on the Tivo (can't get shell right now since my SA Tivo is temporarily out of order). If you are interested in this hack for whatever reasons this is a good starting point no doubt to learn a bit more details: http://www.linuxdoc.org/HOWTO/Serial-HOWTO-10.html

I did think of one other way to get that extra serial port onto the Tivo. Instead of an ethernet card in the TivoNet adapter, put in an old ISA serial card that has existing Linux drivers for it (I don't know exactly how much porting work they would require - probably no more or less than the NE2K ISA drivers took). This is a bit more kludgey and less elegant of a solution than I am looking for (also a bit costly at 100 bucks for the adapter) but damn, the result would be sweet.
And yes, I realize there is still a question as to whether the Tivo has enough CPU power to run the apps that might take advantage of two serial ports (ahemPitouahem), but we won't know for sure until we try. Oh, and if anyone has any real intel on how the Tivo software interacts with that card slot, I'd love to hear it. Sorry for the long post. :)

[Trikx]

btw -- to save everyone the time searching, the following topic:

http://dealdatabase.com/forum/showthread.php?threadid=4212&perpage=15&pagenumber=1

is the old discussion about this topic....there were some great ideas proposed, but unfortunately the thread wandered off into name-calling and discussions on the merrits of ASIC chips...

Let's talk about serial ports! ;)

[GoneSilent]

The cpu just dosnt have the speed to do emu at the same time. extractstream has problems with the vbr that dtv use's I also want to look at the kernal more what, what changes are made to make this a Dtv, At the end of the prom when viewd in hex it has some stuff about a standalone. So from that I know it changes a few things. Does extractstream still work with 2.5.1 on SA box's?

[GoneSilent]

my understanding is the prom for the "dtv" side of the tivo is under direct tv's control. Tivo is not aloud to touch it. The prom and most of the "Dtv" side of it are all stock off the self setups from good old dave himself. Dont think of your Dtivo as that. Its more Tivo with DirectTV and a digtal path right from Dave to your HD. Im sure tivo talks to the "dtv" side of tivo via ser.

[BubbaJ]

I'll never te-eellll....
:D

seriously, have fun guys, the information you seek is right there in front of your faces, and Boy is it Tasty!!

It Tastes better on 2.01 :eek:

[compugeek617]

Oh now BubbaJ that's just mean....;) C'mon...share the love...

But seriously, here are my thoughts on the "dual serial port" issue....pardon if they're novice...:

For now, let's talk about the simpler example of using existing external hardware that would plug into two serial ports (as opposed to the "all software" idea that was tossed around on the previous thread).

Also, though many claim that the box doesn't have enough CPU power, I am hesitant to believe this until it's proven one way or the other. I'm certainly not going to give up on this hack without at least trying...!

So the steps I see to victory are as follows:

1) Compile pitou for DTivo.
2) Acquire two serial ports (easier said than done).
3) Run pitou.


We have one serial port confirmed....ttyS3...that's the easy part. Now we need one more. A few ideas on how to get there:

1) Install expansion board + ISA serial board, compile drivers for TiVo, be happy.
2) Use ttyS3 as one, and figure out how to use the IR port as the second (unlikely due to remote control issues)
3) Use ttyS3 as one, and figure out if the card reader is a serial device that can be remapped
4) Use ttyS3 as one, and play around with ttyS2 (a faq I read says it's there but 'unavailable' -- what does that mean?)

Any thoughts?

[Trikx]

Whoops...logged in under the wrong account...that was me posting above...

[GITM]

I don't know where GoneSilent got his information. But from what I have seen in my DirecTiVo and it seems that a majority of the DTV stuff is handled in the Linux OS, including access card control. I just don't think it matters much. And here's why:

The ASIC in the card can take just about anything as input for generating the encryption hash (including the time, or any data on the card). This is how the current "HU hash" works, it uses code directly from the card to generate the video decode keys, so if the code on the card has been changed you will get incorrect keys. This means that no matter what you can do to the receiver you must still emulate the access card in it's entirety or you will not be able to generate the ASIC input necessary to get the correct video decode keys. Any solution we design must have a fully functioning access card emulator somewhere. Maybe BubbaJ has found something that I haven’t, but I don't think so. The best we can do is insert our own code between the DTV receiver software and the access card serial port. With this in mind I see the following solutions:

1) Compile a fully functioning Pitou emulator for the DirecTiVo and connect it to the access card serial port on the DirecTiVo. Will the system be able to handle the load? We won't know until we try, official Pitou MHz restrictions don't matter; this is a PPC not a Pentium. For those with BS H cards this is not an option.

2) Compile the Pitou emulator that uses a different server to access the card. We could use the current serial port or a TiVoNET card to do this. This is probably faster than (1), but I haven’t looked at the code so I don't know. If it isn't much faster we can always rewrite it so the DirecTiVo sends the raw serial stream to the server, I can't imagine the DirecTiVo's processor won't have the power to redirect a serial stream over an ethernet port. You will be able to handle multiple DirecTiVo's with one card too :).

3) Design a system that can process the entire satellite stream and generate video decode keys for every channel. The DirecTiVo would send the channel it is tuned to and the server would send the keys as they are generated. You would need only one server for the entire world, but good luck designing it.

I think (2) is the best solution. I want to be able to hopefully run TiVoWeb and ExtractStream and InsertStream on my DirecTiVo as well so the solution that uses the least resources would be best. And sending all your access card queries over TiVoNET would be a very elegant and invisible solution.

Sorry for the length, it's hard to stop once I get going.
-GhostInTheMachine

[GoneSilent]

I have seen a full working emu setup inside a Dtivo. WITH the cover off. The unit had the 9thtee board but no network card just another small bakcplate style computer and a floppy drive. The card was in the stock card location. So it has been done but not with it running on the Dtivo my self. Im sure they changed some of the tivo code as well.

[BubbaJ]

BubbaJ has definitely found something that you haven't... :D

Yes, the access card is still required, but pretty much just for the ASIC. I know EXACTLY where the ASIC gets its info, and with a little snooping (particularly on 2.01) you'll know too.

[IWantMyDTV]

Since my tivo went 2.0 to 2.5, I am sans 2.01. Wanna point me in the right direction? ;)

[_Formula]

I'd have to guess it has something to do with /dev/cam and /dev/cam2. I couldn't figure out how to snoop on either device file, but that doesn't mean anything. Maybe someone with a little more linux knowledge could check them out. Trying to cat /dev/cam said invalid argument...

[BubbaJ]

_Formula


that is *NOT* the direction I followed, but Your Methods May Vary

[T_RJ]

With the dual tuners do you think that perhaps the bin on the card is being laoded as a device so each tuner is addressing it own virtual card? And then using the asic to generate the key? If we were to chattr the info for that device it would allow us to write our own virtual bins that would be untouchable by dave.

T_RJ

[BubbaJ]

T_RJ:

definitely not.

[IWantMyDTV]

Two questions:

So you're saying that the information about your hack does not exist in 2.5, or you just haven't checked if it does?

Are you joining #tivo? ;)

[dsboyce8624]

Did this idea get picked up somewhere else, or did it die?

[smokeman]

I think BubbaJ needs to elaborate a bit....

It is no fun seeing someone say nah nah ne boo boo :-)

Can you give us some direction?

tail is a utility to log a stream of data to a file.
tail -f /dev/whatever

I haven't tried that though....is that utility in the stuff tridge cross compiled....

Time has gotten away from me, and I simply have not had time to devote to this...

One of my main motivation factors was the dual reciever functionality, which with 2.5 at the time being impossible to hack, I tabled this project.....

I will jump back in with my limited linux abilites (RHCE :-)

BTW, My Sony T-60 has no problems with a h card....did anyone else notice this....no wink....

I wanted to also mention the find a made a while back,, about the reference design having a pci bus on it, so I was wondering if some reverse engeneering could result in the use of a whole bus, like a pci 10/100 card, and/or a scsi card, or a promise ide raid card for ultimate storage space.

I'll have to find the thread...

[BubbaJ]

The PPC does not support PCI. There is an external bus controller that is PPC compatable that does, but I doubt that would be ideal. I have heard that someone designed a board with a cpu and 100Mbit lan chip and programmed it to act like a debug board, but as yet have not personally seen one. If that became available, it'd be real cool and I'd sure buy one..

Clues:
something that is different between 2.1 and 2.5
something that is potentially a gold mine
something that directly relates to the DirecTV part of the DirecTiVo
something that is either in or called by rc.sysinit

I've not offered any new clues, just summarized them. If you can't figure it out, then too bad. (though I'd love it if a few people interested WOULD figure it out so I could get some help)

[dsboyce8624]

Alright, I'll bite, but I need a little more help. I'm new to this stuff, been submerged in DVT/Dish/ExpressVu for too long. You say it's different from 2.01 to 2.5, meaning it's in one but not the other?

I don't have a virgin rc.sysinit from either, can you post one of each here for me.

Dennis

[azdssguy]

<<<--- From Smoke --->>>

BTW, My Sony T-60 has no problems with a h card....did anyone else notice this....no wink....

<<<--- End of Quote --->>>

Can anyone else comment on this statement from
Smokeman? I tried to verify this with my DSR6K
w/2.5xtreme and I get "card not compatible call
ext 752". Is the prom hack different on the T60?
Smoke are you sure you aren't using an HU zkt
on your card / core? You didn't say how you were
using the card. Could it be that the 745 ZKT
check was removed? I guess I could try using a
CAM in the HU range to test that theory.

Hey guys and gals want to respond and save me
some time re-discovering what others might know?

-S

[T_RJ]

send5505?

[dsboyce8624]

Originally posted by IWantMyDTV

Are you joining #tivo? ;)

Where is this?

[smokeman]

I had an hu in, and had to loan it to someone....since my t-60 is my play thing....(not the reciever I normally watch), and I was running a h in it, with a bootsleeve. I did not have an hu zkt in it.
This is pre 2.5(2.0.1 I think), so that may be the key...

[dsboyce8624]

I think we are getting off topic here folks.

The original idea here was, how much control do we have by manipulating the Tivo software. ie. How much control does the Tivo have of what you see, and how much does the IRD have.

Dennis

[grooves12]

don't want to let this thread die... there is a lot of interesting talk that was going on here...

Can anyone post those virgin rc.sysinit files from 2.01 and 2.5?? I would like to do some searching myself, but dont feel like reloading the image on my system to figure it out...

[BubbaJ]

The modified rc.sysinits contain all you need..

[synthesis]

Not to get off on a tangent, bu I'm with RJ- can anybody tell me exactly what the send5505 command DOES (beyond "BERR test :) )? Executing it from bash as below (heh) blanked my feed until I rebooted, even with the -i1 command.

/tvbin/send5505 "wr299 28 40"
/tvbin/send5505 -i1 "wr299 28 40"

taken from rc.sysinit:
echo "Enabling Tuner BERR Test"
/tvbin/send5505 "wr299 28 40"
/tvbin/send5505 -i1 "wr299 28 40"

[BubbaJ]

send5505 sends messages to the STi5505 cpus. I *THINK* the -i specifies an interface, which would be 0 by default

[xmetalloid]

This thread is about serial ports, right? If I understand what you want them for, it seems only one is needed - to communicate with the ASIC. So you intercept communication to your access card (don't yet know what code does this), channel it through another program (you know what one) and have THAT program communicate with the ASIC as if it was in a pheonix programmer on a serial port ('cause it is, really).

You'd have to use fastaux=no, but that's not a biggy. Imagine, no hardware except your Tivo, with an H card in the card slot. Secure, safe, and no external cables. And still have a port for your bash prompt.

Sorry for my vagueness, but I'm staying within the rules :^)

[xmetalloid]

I think GITM had it right with suggestion number 1 (I just re-read the post and it looks like (s)he is saying the same thing I am - or I guess I am saying the same thing as him/her).

Pitou could be compiled to work with the card slot serial port, with an H card in it. Since BubbaJ knows how the ASIC gets it's info (I'm assuming within Tivo and not within Pitou), that's the last half of the puzzle, no?

A BS H card should also work, with a bootloader. It's kind of ugly hanging out of the back of the Tivo, but still viable.

[Digitz]

Perhaps we're looking for this??? If so then it can only be found in 2.0 or earlier.

opening driver
Subscriber ID = xxxxxx
CAM ID = xxxxxxxxxxx

Digitz

[Digitz]

Which means I need a dissassembler and we should look real close at

/dev/oslink
/dev/oslink2
/dev/apg
/dev/apg2
/dev/dtune
/dev/dtune2
/dev/cam
/dev/cam2

Digitz

[Digitz]

I can't believe DTV allowed TIVO to use the 5505s oslink to bootstrap with. Can you say huge gapping hole in security!!!! but extremely cool for the rest of us. Now to figure out how to make this work to our advantage. I'm guessing this discussion is being held elsewhere since DTV hacks aren't allowed here. Anyone want to point me in the right direction? PD perhaps? Hadn't been there in a while.

Digitz

[Digitz]

Anyone have a copy of IDA pro?? I thought I had it but apparently not. I'd rather not write a disassembler.

Digitz

[Mentler]

[xmetalloid:]

[...]
Pitou could be compiled to work with the card slot serial port, with an H card in it.

Based on the 2.5 system scripts, it appears that DTiVo's serial ports are the same as on standalone, i.e., modem, debug board, IR blaster, and DSS.

(That reminds me of something I thought of earlier today: I'm having hiccups setting up PPP between DTiVo and my Linux PC, so I might try using TiVo's modem and DSS serial port to have a terminal and a PPP connection at the same time. Don't mind me, just rambling.)

Anyway, this is my first post here, so I'll just tell you all a teeny bit about myself^H^H^H^H TiVo.

I'm running a Philips DSR6000R with 2.5 and a 40 GB `B' drive. I performed the PROM fast-boot patch just after it came out (I tried disassembling the PROM myself, but it was tough going without any symbols). I *should*'ve been straight into the initrd then, but I was looking at the wrong kernel partition.... :-[ After fixing up the initrd, all was fine. Now I'm having fun trying to figure out TCL and some other stuff.

[Mentler]

[Digitz:]

Which means I need a dissassembler and we should look real close at
/dev/oslink
/dev/oslink2
/dev/apg
/dev/apg2
/dev/dtune
/dev/dtune2
/dev/cam
/dev/cam2


bash-2.02# ls -al /dev/{apg,cam,oslink,dtune}*
crw-rw-rw- 1 0 0 95, 1 Oct 31 05:09 /dev/apg
crw-rw-rw- 1 0 0 96, 1 Oct 31 05:09 /dev/apg2
crw-rw-rw- 1 0 0 95, 3 Oct 31 05:09 /dev/cam
crw-rw-rw- 1 0 0 96, 3 Oct 31 05:09 /dev/cam2
crw-rw-rw- 1 0 0 95, 2 Oct 31 05:09 /dev/dtune
crw-rw-rw- 1 0 0 96, 2 Oct 31 05:09 /dev/dtune2
crw-rw-rw- 1 0 0 95, 0 Oct 31 05:09 /dev/oslink
crw-rw-rw- 1 0 0 96, 0 Oct 31 05:09 /dev/oslink2

All four of these pairs are on majors 95 and 96, which means they are all handled by oslink.o (as I understand it, only one module can handle any given major number?).

[Digitz:]

Anyone have a copy of IDA pro?? I thought I had it but apparently not. I'd rather not write a disassembler.


You'll need the Advanced version for PowerPC support. Sorry, I can't remember the company's name just now, so you'll have to Google for ida pro advanced, or perhaps ask on the newsgroups and see if someone knows where you can get it. ;-)

[chipster]

:p

[smokeman]

Have we found the dss smart card slot as a device, so we can just re-route pitou?

Has pitou been compiled to work on a dtivo yet?

just wondering how the pieces are falling together....

[digitalAir]

Has anyone successfully communicated with /dev/cam?

I wrote a little c file to open read and write file streams, but all it read back was FF's :confused: on an H card and an HU...

I'm guessing I've overlooked something... :)


-digitalAir


P.S. I haven't been brave enough to comment out all the dtv initialization code in the rc.sysinit yet. I'm thinking that it may be similar to the /dev/mpeg0a device -- where you have to disconnect myworld from the device before you can manually send an audio stream to it.

[tivomon]

is it possible to get to the zkt information on a hu card plugged into the receiver ?

[tivomon]

I found ida pro but the full version is needed to disassemble PPC code, they want $299 for it. So let's get 100 people to contrib 3 bucks a head.

[digitalAir]

Originally posted by tivomon
is it possible to get to the zkt information on a hu card plugged into the receiver ?

tivomon,

I'm in a mood, so I'll answer your question with a definition:
ZKT: Zero Knowledge Test

:)

[tivomon]

thanks for sharing :) but I think we all know what ztk is. :) just curious if that could be pulled of from the receiver vs getting a huloader and going thru all that drama. Will I wack the atr etc...

[IWantMyDTV]

Now that would be something I would love to see. Then I could start watching DTV again. ;)

Damn blacklist.

[digitalAir]

Ok, I admit, that was a rather smart@$$ reply.

The point I was attempting to make is this:

zero knowledge test, by it's very definition means the IRD has no knowledge of the test.

In other words, I ask you, "What's 2 + 2?"

you answer, "4"

I don't know how you came up with the answer; calculator, 40 years of knowledge, c program, asked your moma, etc.

I don't care, but you came up with the correct answer, so I'll continue displaying video...

(sorry for the previous post...) :p

[tivomon]

no worries I was in a wierd form yesterday also. I think my wife must be on the rag again... :) What I getting at is this, the DirectTivo has a H[U] card reader build in. Couldn't we utilitze it and read off all the bits on our h[u] cards. It a valuable thing to get you cam/zkt off and shove that into a cor file for emulation. it tends to keep you of the black lists.

[AlphaWolf]

Sorry if this is going off topic a tad, but this thread sparked an idea in myhead:

There are various known physical modifications that you can do to make different models/makes of IRDs not care if the zkt does not match the cam ID. With a tivos current setup, would it be at all possible to make it have the same behavior with a software hack? Or is DTVs signal descrambling portion *that* well segregated from the tivo portion?

[mrblack51]

the zero knowledge test, like digitalAir was mentioning, is based on the fact that the ird doesnt know the number on the card. the ird takes the camid, does some manipulation, then the card does some stuff, and returns a number. both of these numbers relate to the magic number N, determined by NDS. hence, the reciever knows nothing about the zkt on the card, other than that its calculation and the one that the card produces.

ok, so then the other option would be to use the unit to read the card directly. well, first off, can you read the zkt off of an hu card with a regular programmer right now? nope, because there arent any holes on the hu that have been made public. so, the only option left is going in directly. well, that requires a properly formed and signed packet. i certianly dont think anyone will be figuring out how to make those packets any time soon, otherwise that is what would have been used on h's as well as hu's.

[IWantMyDTV]

I like alphawolf's take on this issue. It seems that the TiVo software has alot of control over how the DTV part works. If a hack like the 303 mod (I believe that's what it's called) could be accomplished, then the blacklist wouldn't be a problem.

[AlphaWolf]

Bear in mind that there are several known techniques of adding your own backdoor to an HU card so that it can in fact be read/programmed with a normal card reader.

If you don't emulate, then also consider that when properly hidden through the use of uncommon jump points, and secured by means such as a password, it can be quite ECM proofed too....

[digitalAir]

The TiVo side talks to the CAM through the STi5505 chip. How this is done has not been documented, yet.

[tivomon]

ok this sparked a though in my walnut size brain. From the H card days I rember the teir activation scripts. So I'm thinking instread of activating teirs on the HU cards now, could we incept the quiery of the card for the teir validataion and on the tivo just say yes it's valid and active, and then let the hu card provide the video decript keys. Ie in theroy you could take a subscribed card and it would activate all channels, and the card it self would have been modified, just the software on the receiver. Just a though, but hey maybe I'm in outer space on this one.

[digitalAir]

unfortunately, it's not that easy...

all the tier validation (and mpeg decrypting) is done before the tivo gets hold of any of the data...

Remember, the STi5505 is a stand-alone processor. it takes the data steam off of the dish, parses out the low speed data, sends it to the CAM, get a key from the CAM, and uses that key to "attempt" to decrypt the video. All this is done before any interaction is with the PPC. (I say attempt, because the CAM returns a key no matter what. But, if the card doesn't contain a valid tier for the channel being viewed, that key what properly decrypt the video stream.)

[BubbaJ]

what would be rather fun is to take a vanilla card, apply activation for everything, then convince the ird that it has a different card. .. :)

can you figure out why??

[digitalAir]

what do you mean by "then convince the ird that it has a different card."?

[tivomon]

humm well if by vanila card you mean a standard iso7816 then in theroy I don't see why you couldn't load the h or hu code, it's just bits in memory slots at the very basic level. But when the ird tries to run any of the code, at some point would be a call to the oncard asic and humm it just wouldn't be there, soo what kind of key would be returned, my guess is a null or random garbage. I'm not sure that this would work, of course there migh be something up the perverbial sleve that I'm just not seeing yet. Can you say easter bonus ?

[BubbaJ]

by vanilla card I mean a 'virgin' H or HU, or a subbed one for that matter.. or a 'cleaned' one yada yada yada


That would NOT be the direction I want you to go with this.

By convince the IRD that it has a different card, I mean exactly that. What if the card has one number and the IRD thinks the card has a different number?

[digitalAir]

Well, that, plus a few other tweaks here and there, and you could actually plug the ird into the phone line...

[smeghead]

Originally posted by BubbaJ
what would be rather fun is to take a vanilla card, apply activation for everything, then convince the ird that it has a different card. .. :)

can you figure out why??

Not sure about the how, but as to the why - would this mean that the tiers would never be wiped because the IRD would be trying to wipe tiers from the wrong CAM ID?

Maybe I'm braindead, and I almost certainly don't know what i'm talking about here, but this thread has me rivetted - I need more info... (open up a bit more please BubbaJ!!)

[cali]

I'm new around here, but pretty deep into the DAVE side of stuff.
I just wanted to comment on the quote below:

That has been done before and some are still doing it...but that however does not offer any advantages (illegal or not).

The asic has to spit out the decryption keys for video.


Originally posted by BubbaJ
by vanilla card I mean a 'virgin' H or HU, or a subbed one for that matter.. or a 'cleaned' one yada yada yada


That would NOT be the direction I want you to go with this.

By convince the IRD that it has a different card, I mean exactly that. What if the card has one number and the IRD thinks the card has a different number?

[emc2]

I am new here but not to hacking. Thought this thread was for looking for a dev for the card slot to talk to card with peetuu or some form of a ostrich.:confused:

[opticalcarrier]

This thread was discussing reading/writing to the DSS card from the linux OS on the dtivo. has anyone ever had any success?

It would be extremely useful to just be able to pull zkt/camid from a subbed p4 card.....

-OC

[BubbleLamp]

Originally posted by opticalcarrier
This thread was discussing reading/writing to the DSS card from the linux OS on the dtivo. has anyone ever had any success?

It would be extremely useful to just be able to pull zkt/camid from a subbed p4 card.....

-OC

That's not a discussion for this board, take it elsewhere.

[dsboyce8624]

Actually you would want to look into the infamous 303 mod.

Dennis

[smokeman]

as I've said in the past,
this seems to be the only open place for discussions of this sort...
other forums boot people for discussing things like this, and I know a lot of people on this forum are involved in other dss related projects such as pitou, etc...
there have been many posts about dtivo, and emulation, etc...

now, actual dss hacking as a topic can be discussed on forums, such as id-discussions, and atsdss, etc...
but as this pertains specifically to the dtivo, this is the perfect place, as opposed to a tivo only forum.

If the mods do not want this discussed here, then they have been very laxed in the past on the topic.

[opticalcarrier]

im not talking about doing anything with the card. Im trying to determine if the linux OS does anything with the card at all.

[BubbleLamp]

Originally posted by opticalcarrier
im not talking about doing anything with the card. Im trying to determine if the linux OS does anything with the card at all.

Linux runs the Tivo. Tivo tunes IRD. Hence Linux talks to card. To what degree, well that's where we stop talking in public.