HVR2250 Status - Where am I?
It's best to explain it here:
http://steventoth.net/blog/hvr-2250
Regards,
- Steve
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 4 lines · Steven Toth
It's best to explain it here:
Any way to get a running total on your blog?
John
Quoted 7 lines · John Drescher
Quoted 4 lines · Steven Toth
It's best to explain it here:
Any way to get a running total on your blog?
I'll try to figure something out.
- Steve
Quoted 11 lines · Steven Toth
Quoted 7 lines · John Drescher
Quoted 4 lines · Steven Toth
It's best to explain it here:
Any way to get a running total on your blog?
I'll try to figure something out.
BTW, Can this be posted in the Mythtv forum as well? I know there are a few users there (myself included) that would be very interested in this card.
John
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line
Quoted 1 line
Quoted 1 line
Any way to get a running total on your blog?
I'm not against donating for hardware support but I would like to see the total (and it increase after I donate) and also the code tree published so others can contribute and track changes. Regards,
Andrew
PS. Thanks for all your hard work on all the drivers - not just this one. It's greatly appreciated by the MythTV community among others and myself.
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 5 lines · John Drescher
Quoted 1 line
Quoted 1 line
Quoted 1 line
Any way to get a running total on your blog?
I'm not against donating for hardware support but I would like to see the total (and it increase after I donate) and also the code tree published so others can contribute and track changes.
I don't have anything that sophisticated to be honest. If that bothers you then I understand and respect your decision not to support the project.
I can't publish any source code until the driver is largely complete, that's not my call, that's the arrangement with NXP.
Quoted 3 lines
PS. Thanks for all your hard work on all the drivers - not just this one. It's greatly appreciated by the MythTV community among others and myself.
I had specifically decided NOT to look at any HVR-2250 web stats for a week. I ran the numbers today and this is where I am:
Quoted 13 lines
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Any way to get a running total on your blog?
I'm not against donating for hardware support but I would like to see the total (and it increase after I donate) and also the code tree published so others can contribute and track changes.
I don't have anything that sophisticated to be honest. If that bothers you then I understand and respect your decision not to support the project.
I can't publish any source code until the driver is largely complete, that's not my call, that's the arrangement with NXP.
Quoted 9 lines
Quoted 3 lines
PS. Thanks for all your hard work on all the drivers - not just this one. It's greatly appreciated by the MythTV community among others and myself.
I had specifically decided NOT to look at any HVR-2250 web stats for a week. I ran the numbers today and this is where I am:
Well I just made that 5. Being a software developer myself, I know this will not go far but hopefully more people will see find the page and help out.
Also BTW the other message was from Andrew Barbaccia who replied to me instead of the list so I just forwarded it..
John
Quoted 14 lines · John Drescher
Quoted 14 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Any way to get a running total on your blog?
I'm not against donating for hardware support but I would like to see the total (and it increase after I donate) and also the code tree published so others can contribute and track changes.
I don't have anything that sophisticated to be honest. If that bothers you then I understand and respect your decision not to support the project.
I can't publish any source code until the driver is largely complete, that's not my call, that's the arrangement with NXP.
Quoted 3 lines
PS. Thanks for all your hard work on all the drivers - not just this one. It's greatly appreciated by the MythTV community among others and myself.
Quoted 8 lines
Quoted 5 lines
I had specifically decided NOT to look at any HVR-2250 web stats for a week. I ran the numbers today and this is where I am:
Well I just made that 5. Being a software developer myself, I know this will not go far but hopefully more people will see find the page and help out.
Thanks John.
Quoted 3 lines
Also BTW the other message was from Andrew Barbaccia who replied to me instead of the list so I just forwarded it..
Ahh, fair enough.
Thanks again,
Steve
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
I don't have anything that sophisticated to be honest. If that bothers
you then
Quoted 1 line
Quoted 1 line
I understand and respect your decision not to support the project.
[snip]
Quoted 6 lines
Quoted 3 lines
Quoted 3 lines
I can't publish any source code until the driver is largely complete,
that's not
Quoted 1 line
Quoted 1 line
my call, that's the arrangement with NXP.
Sorry, maybe I phrased my request as a solution which is not what I intended. I was unaware of your agreements with NXP. I see you added how much money has been donated to your post. That's more than enough of a status indicator for me.
Possibly could you roughly estimate how much more work is required and present it in the same manner?
I want to you know that I do support this project and have just contributed
- both as a thank you for your prior work and willingness to help the community in addition to the HVR-2250 support.
Thanks,
Andrew
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
On Fri, Feb 27, 2009 at 1:27 PM, Andrew Barbaccia
Quoted 9 lines
Sorry, maybe I phrased my request as a solution which is not what I intended. I was unaware of your agreements with NXP. I see you added how much money has been donated to your post. That's more than enough of a status indicator for me.
Possibly could you roughly estimate how much more work is required and present it in the same manner?
I want to you know that I do support this project and have just contributed
- both as a thank you for your prior work and willingness to help the community in addition to the HVR-2250 support.
Andrew,
I cannot speak to the saa7164, but to give you an order of magnitude, I spent over a month working on the saa7136 support, working every night and weekend for 4-6 hours. The analog support I did for the au0828/au8522 took about 100 hours.
So, while not necessarily an apples-to-apples comparison, these drivers tend to take tens or sometimes hundreds of hours of development. They are definitely a non-trivial amount of work to do.
Bear in mind that the saa7164 is a much more complicated chip than the saa7136.
Devin
Signature · 3 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller
Quoted 18 lines · Devin Heitmueller
On Fri, Feb 27, 2009 at 1:27 PM, Andrew Barbaccia
Quoted 9 lines
Sorry, maybe I phrased my request as a solution which is not what I intended. I was unaware of your agreements with NXP. I see you added how much money has been donated to your post. That's more than enough of a status indicator for me.
Possibly could you roughly estimate how much more work is required and present it in the same manner?
I want to you know that I do support this project and have just contributed
- both as a thank you for your prior work and willingness to help the community in addition to the HVR-2250 support.Andrew,
I cannot speak to the saa7164, but to give you an order of magnitude, I spent over a month working on the saa7136 support, working every night and weekend for 4-6 hours. The analog support I did for the au0828/au8522 took about 100 hours.
Quoted 6 lines
So, while not necessarily an apples-to-apples comparison, these drivers tend to take tens or sometimes hundreds of hours of development. They are definitely a non-trivial amount of work to do.
Bear in mind that the saa7164 is a much more complicated chip than the saa7136.
So now (with my donation) we have him working at $1/hour assuming that it takes only 100 hours..
John
Quoted 4 lines
So now (with my donation) we have him working at $1/hour assuming that it takes only 100 hours..
Well, $2, with mine. ;-)
_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 2 lines · John Drescher
So now (with my donation) we have him working at $1/hour assuming that it takes only 100 hours..
Well, this assumes that it would only take 100 hours, of which given the complexity of the device, it will probably take more than twice that (since it's a PCI device and the estimates I gave are for USB devices).
If nothing else, it offers some insight as to how valuable the work of people like Steven is (he has written a whole bunch of different drivers). It also demonstrates one reason there are so few developers willing to do this sort of work. Getting a developer to donate a couple of evening's worth of time is pretty easy. Getting them to make a commitment of every day for the next two to three months is quite harder.
Devin
Signature · 3 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller
Quoted 9 lines · Devin Heitmueller
Quoted 2 lines · John Drescher
So now (with my donation) we have him working at $1/hour assuming that it takes only 100 hours..
Well, this assumes that it would only take 100 hours, of which given the complexity of the device, it will probably take more than twice that (since it's a PCI device and the estimates I gave are for USB devices).
Quoted 7 lines
If nothing else, it offers some insight as to how valuable the work of people like Steven is (he has written a whole bunch of different drivers). It also demonstrates one reason there are so few developers willing to do this sort of work. Getting a developer to donate a couple of evening's worth of time is pretty easy. Getting them to make a commitment of every day for the next two to three months is quite harder.
It takes a massive amount of time from all of the core developers to keep the v4l-dvb tree up to date and to add new functionality.
Adding a new style of board to an existing driver can take a couple of hours with testing. It's bread a butter maintenance task.
However, adding a brand new bridge driver to the kernel can take 6 months just for the first release, and is then slowly improved over the next 12-24 months.
It's a large task.
- Steve