On 4/11/10 4:26 PM, "ext Alan Cox" <[email protected]> wrote:
>>> Why isn't this driver upstream?
>>
>> We tried. No success.
>>
>> http://lkml.org/lkml/2010/8/23/191
>
> You didn't try very hard it seems ?
Maybe. The feedback was pretty clear. With this setup there is not path to
mainline.
> And is the spec in question still closed, is the hardware in fact
> tightly tied to a non-free userspace ?
Nothing has changed in the spec and how to get it. I don't see the situation
changing anytime soon.
> With my upstream hat on we have to be very careful about this because a
> GPL piece of kernel code closely tied to and not usable without a
> non-free component could be considered to be one work and then we get
> into the realm of people in suits ties and briefcases, which is a place
> we prefer not to go.
>
> Secondly its very bad to have undocumented, untestable interfaces which
> is what you are asking for.
>
> I appreciate there may be reasons it's been done that way, for example
> if the GPS enforces the checks against certain classes of usage in
> software but again with kernel upstream hat on, our primary job is to
> make sure the kernel is testable, documented, complete and open.
All of your arguments are valid. On the other hand, we need the code one way
or the other to make products based on MeeGo. That is our primary target.
And we'd like to keep the delta between that MeeGo and mainline minimal. So
if the driver does not go to mainline, next option is to include it in
MeeGo. And if that is not possible, the worst option is that we keep
maintaining our own product tree inside Nokia. This is not what we want.
It's not an ideal world. We need to make compromises somewhere.
-sakari
>
> Alan
>
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
