| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| theorem | luisbg: still here ?
I am responding back to your interest in writing a driver the device is about $100 USD OEM hvr-2255 I have reached out to KernenlLabs , and they're preparing a public driver. However, they are taking their time in doing so. this is a small improvement over the HVR-2250, which is supported I suspect if you offer your help they will be able to get a public driver out sooner. would you like me to put you in touch with the guy from KernelLabs ? I have an open dialog with them as of this week. | [00:27] |
| ...................................................... (idle for 4h25mn) | ||
| devinheitmueller | theorem: We (Kernel Labs) are pretty easy to have an open dialog with. :-) | [04:55] |
| ........................................................................................................................ (idle for 9h57mn) | ||
| luisbg | devinheitmueller: :)
devinheitmueller: do you know what is the status of the hvr-2255 driver? | [14:52] |
| .... (idle for 15mn) | ||
| devinheitmueller | luisbg: We have a driver that we currently ship to commercial customers, and plan to release publicly at some point, but I don't have the timeline on when that will be. | [15:07] |
| luisbg | devinheitmueller: sorry if this is confidential but, what is keeping it from being released?
I mean, what does the timeline entail? is there some license or business reason not to? | [15:10] |
| devinheitmueller | We're still trying to recoup the cost of development from commercial parties. | [15:10] |
| luisbg | ahhhhh :) got it
I understand | [15:11] |
| devinheitmueller | Also, there's an argument to be made that commercial customers might get a bit annoyed that they paid thousands of dollars for something that we then gave away a few weeks later. | [15:11] |
| luisbg | I have friends running an open source consulting business with the same problem
they have a 6 month statement in their contract where the development made for the costumer will be released publicly (LGPL) after 6 months of finishing it is a good balance | [15:12] |
| devinheitmueller | It's a challenging problem. If commercial customers believe they can just forego paying for something if they know that they can just wait a bit and get it for free, they are unlikely to pay for it in the first place. The problem is that it's the commercial customers money that is used to pay for the work in the first place.
A bit of a chicken/egg problem. And in some cases we can be talking about tens of thousands of dollars worth of engineering, hence it's not like we're talking about a few hundred bucks. | [15:13] |
| luisbg | true, in the case of my friends there is no guarantee anybody else will pay for the development a costumer needs
but this is more specific features in a userland framework/library very different issue than linux kernel and hardware verticality helps with consulting :S | [15:16] |
| devinheitmueller | Similar challenges with drivers. In some cases we have customers who need specific enhancements and we're the best suited to do that work. But for many customers what we've already made available in the freely available driver is "good enough", and we'll never see a dime from those users.
And since you cannot charge a per-unit royalty, it's very hard to spread that cost over a large base of users. Hence customer 1 has to pay $20000, and then customers 2-N pay zero. It's hard to find customer #1 in that case and they can get pretty angry if they then pay a boatload of money and everybody else gets it for zero dollars. | [15:18] |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |