On Fri, Sep 19, 2008 at 4:50 PM, Woodruff, Richard <r-woodruff2@xxxxxx> wrote: > Hi Igor, > >> -----Original Message----- >> > Where do you think the lineage of the hardware and software is? Do >> you believe it just jumped into being in open source? All hardware and >> software is full of deliberate design and hacks. Its true cooperate >> design constraints are driven by the bottom line and for some in open >> source it is not. >> >> Getting the HW to work somewhere is not good enough. It must be >> supported in mainline, the more code you generate out of mainline, the >> less likely anybody can get it to work after a while and it slows down >> everybody. > > Sure. In this case I'm just airing some frustration. It is not like some version of this isn't already shipping years back in N800. Rapid development/advancement is great but there should be a working spot which isn't by just by chance. > > In this case a tree is just like a branch. We have done some new development outside on this branch to enable a new dma mode to boost performance. Hopefully that will be folded back in before too much time. I think I've seen a patch even. In the past we would have just 2x the performance on some old kernel and made it available. But probably so out of phase you really had to work to get it. Today using a current tree it is there and there is a lot better chance we or some community person will push it back. Nobody cares about tree vs branch, the problem is that the branch is forked from way back in the history. If you want your changes to be merged you need to rebase continuously, and not have a single ompazoom branch, but many. That way people can pick the patches they are interested in. The difference is a branch for changes to-be-merged vs a fork. For the vast majority of people, code that is not in upstream, is code that doesn't exist. That's why good branches should be temporal forks; as short in time as possible. Permanent forks go against collaboration. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
