Planned wireless MVP support?

[kminder]

Can someone from Frey comment on whether or not the "soon to be released" wireless MVP will be supported "out of the box".

I'm hoping that they added some support for static IP addresses since I can't get the two MVPs that I currently have to acquire them on my network.

Furthermore one could dream that the mvp.bin could even be flashed to the device. Now that would eliminate some support calls.

[PGPfan]

To the best of my understanding the MVP (wireless) will be supported by default by Sage as there shouldn't be any difference between them from a Sage perspective (for the most part).

As for 'flashing' the mvp.bin, that gets done anytime the MVP is power cycled. The mvp.bin has no persistant storage which is what enables Sage to boot and run 'natively' in this device to begin with.

-PGPfan

[jquinlan]

I guess the question could be does the SAGE bin file for the MVP have the support built in for the wireless chipset in the new wireless unit? You could still need additional drivers in the bin image for the wireless to work.

Would this be a true statement?

[stanger89]

I think, that Sage doesn't even deal with anything at that level, that's taken care of by the "OS" on the MVP. The MVP has to initialize the network device, and then connect to the boot server (SageTV) and get the application loaded (for lack of a better explanation).

[kminder]

Well there has to be some difference between the way the "OS" for the MVP will work because I will need to be able to establish things like my SSID and WPA-PSK.

I would expect that this type of thing will need to be done like you typically would with a WAP. Meaning that you need to run a cable to it and work with a web based interface (or config app) before it will do anything useful. (Obviously speculating here)

I'm just hoping that this difference...
a) does not preclude SageTV from using the device from the get go (or ever)
b) might help me solve some of my MVP networking issues (which I would rather spend $150 to fix than doing more Ethereal trace analysis at this point)

I guess I'm just a lazy optimist.

[Deadbolt]

More importantly...will sage support the SPDIF port on the new MVP and allow us to stream DVD isos to the box?

[stanger89]

Originally Posted by kminder

Well there has to be some difference between the way the "OS" for the MVP will work because I will need to be able to establish things like my SSID and WPA-PSK.

I would expect that this type of thing will need to be done like you typically would with a WAP. Meaning that you need to run a cable to it and work with a web based interface (or config app) before it will do anything useful. (Obviously speculating here)

But the box has to boot itself and initialize the network to get the mvp.bin file, so practically, the drivers/config to setup the ethernet (or wireless) interface can't rely on the wiz.bin. That's my point, that the MVP must handle the low level network interface.

Originally Posted by Deadbolt

More importantly...will sage support the SPDIF port on the new MVP and allow us to stream DVD isos to the box?

Now that, is the real question

[kminder]

Absolutly stanger but I can just see the Hauppauge folks deciding to "build in" the mvp.bin file since they will need to have much more complex internal behavior than just BOOTP. If this is the case Sage may not be able to bootstrap its mvp.bin.

Basically I'd like to know now so that I can just bite the bullet and get my wired MVPs working.