[PATCH] Add USB to MPC8349 PB platform support
Kumar Gala
galak at kernel.crashing.org
Thu Jul 20 06:55:05 EST 2006
[snip]
> Having my changes for our boards that are very specific since they are
> connected to FPGAs would IMHO serve little purpose in the Linux
> kernel:
> there is very limited access to the hardware and it would only
> serve to
> clutter the kernel with an exponentionally growing number of ports
> that
> most ppl will never use. I think (even though using ARCH and
> CROSS_COMPILE during compilation limits the audience); the target
> audience between U-Boot and the Linux kernel is slightly different.
>
> Though I do agree that there is a gap: it would be nice to have some
> place to submit the kernel patches; possibly not included in the main
> tree; just to see how other ppl are tackling the same problem and
> avoiding re-doing the same work for the nth time (e.g. writing some
> communciation protocol where there are a number of references of ppl
> haveing done them, but no real code).
This should be the kernel. The general rule of thumb I've used is if
its useful to more than one other person its worth trying to get into
the kernel. However, I can see if you are doing a one off kernel for
your embedded product that getting your changes into the kernel
wouldn't be worth while. You have to have a desire to interact with
the community if you want to get your code in.
Personally, I see it useful if for no other reason that someone will
fixup my board port if/when they change something which will make my
moving to a newer kernel release that much easier.
- k
More information about the Linuxppc-dev
mailing list