[mythtv] [mythtv-commits] Ticket #8108: dvd playback on via epia M10k causes mythfrontend or X to segfault

[Robert McNamara]

On Mon, Mar 1, 2010 at 5:01 PM, Simon Kenyon <simon at koala.ie> wrote:
> Michael T. Dean wrote:
>>
>> On 03/01/2010 02:24 PM, Simon Kenyon wrote:
>>>
>>> MythTV wrote:
>>>>
>>>> #8108: dvd playback on via epia M10k causes mythfrontend or X to
>>>> segfault
>>>>
>>>> Changes (by danielk):
>>>>
>>>>  * status:  new => closed
>>>>  * resolution:  => invalid
>>>>
>>>> Comment:
>>>>
>>>>  Stuart, that's the API. You request surfaces until the driver says no
>>>> or
>>>>  until you have enough (32) whichever comes sooner. We already have some
>>>>  hacks for this driver, but at this point it doesn't make sense to add
>>>> more
>>>>  hacks for yet another regression in a driver for a dead platform.
>>>>
>>> not dead for me
>>
>> Is this your volunteering to fix the issues with the Via XvMC and maintain
>> the code for it?  (Because I'm pretty sure you can't volunteer someone else
>> to do so.  :)
>
> i know you sent it with a big smiley
>
> but i didn't write that code
> nor would i know how to fix it
>
> i do what i can. i run the latest code on a number of machines.
> and as a result i have to accept the ridicule and anger directed at me from
> my family when it breaks. i test stuff. i try to debug stuff. i send it the
> odd very small patch.
>
> but right now, i cannot afford to abandon three perfectly good machines just
> because of a bug. it's not a dead platform to me.

There comes a time where we have to break with the past, and the above
commit was more or less a declaration that that's what we need to do
here.  None of the devs own the hardware in question, none are
interested in acquiring it, and most importantly, some people don't
want to see unclean or hacky code included (and maintained) to support
ancient hardware.  I'm sure that everyone is sympathetic to your
desire to make your hardware go as far as it can, I certainly am.  But
given the choice between devoting time, money, and free time to
hardware, I think this isn't going to see any more attention by the
project officially.  If it goes on working, that's great, but if it
requires dirty code to fix, the answer is probably going to be no.

Robert