Hi!
> >Contrawise, if Embedded developers do contribute their
> >device driver
> >changes back to the kernel, they will be fine. ...
> ---
>
> In fairness, though, some of the developers WILL bitch
> about your not
> using a recent kernel and not providing patches until
> products ship,
> despite that meeting the letter of the license. Some of
> the notes in
Well, of course developers will complain, they _always_ complain. But
it is very different kind of complain... first is
'I think you are violating the law, you are evil'
and second is
'Thank you for playing by the rules, but you know, your code is not
mergeable right now'.
> this thread do exactly that. And I HAVE seen real
> developers say
> something very close to "Your code is based on a kernel
> too old to
> have any value to us" even though they would also claim
> abuse if the
> code hadn't been made available at all. And I've seen
Yep, and guess what, thats okay. Someone with more time than they do
may decide to forward port the code and/or rewrite it for new kernel.
I was doing exactly that with 2.4 sharp sl-5500 code.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
