Hi there, > > > https://backports.wiki.kernel.org/index.php/Documentation/integration thanks for your comments and the link. I skip that before as I thought it's actually for backports developers, not users. I'll read it more carefully. > > Just to clarify, the entire kernel will need to be built from some tree. In my > > reading of the original post, I got the impression that Petr wanted to use a > > pre-built kernel. > Yes, indeed, that's not possible - and doesn't really make sense anyway, > since if you have access to the kernel image and sources to build > against, you might as well rebuild the whole kernel. I'm stack with very old kernel (2.6.37 for arm TI's DM365). No pre-built kernel , I've built the kernel as well, everything is working nice. But as I use embedded device, it would be nice to have the drivers build-in (performance). For some of modules I get message: "This feature depends on another which has been configured as a module. As a result, this feature will be built as a module.". I'll try to find the dependency, but is there any hint, how to search? Thanks a lot for backports, it helped me already :-). Kind regards, Petr -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
