| |||||||||||||
The embedded Linux nightmare - an epilogueThe embedded Linux nightmare - an epiloguePosted May 2, 2007 15:51 UTC (Wed) by tglx (subscriber, #31301)In reply to: The embedded Linux nightmare - an epilogue by NAR Parent article: The embedded Linux nightmare - an epilogue
> I guess they want the new feature (e.g. wireless stack), but don't want the new bugs in e.g. the memory management, scheduler or block layer. And please don't tell me there are no new bugs.
Right, and therefor they backport the wireless stack, which includes the modifications to the network stack on which it relies. Now they need to fixup the memory managment changes in both and some other nasty details all over the place.
This is done by a very small group of people. Do they have the full expertise and overview on all this and the testing and verification capacities at hand to verify this hackery on their own ?
If yes, then they should really go and identify and fix the bugs in mainline. They would be a great asset to the kernel community.
If no, the nightmare is there in it's full glory.
(Log in to post comments)
The embedded Linux nightmare - an epilogue Posted May 2, 2007 16:02 UTC (Wed) by NAR (subscriber, #1313) [Link] They are probably a little naive and think that e.g. the wireless network stack and the block layer are independent of each other and there are well defined and stable internal APIs within the kernel, so it doesn't get redesigned in every two months.
|
|||||||||||||