Many architectures already have the patches for the various kernel
versions ( e.g. patches-3.0, patches-3.1, patches-3.3 ). This is why I
all I had to do was change the kernel version from 3.0.18 to 3.3.2 for
my brcm63xx target (I first did 3.3.1, but then found that 3.3.2 was
the latest)
The question I have is this: Why is the kernel version for brcm63xx set
to "3.0.18"? I suspect it just happened to be the kernel version that
seemed to be working at some point.
When was it last updated? Will it ever be updated again? Who decides?
Thanks,
Jeroen
Citeren Otto Solares Cabrera <so...@guug.org>:
Regarding the problem of users playing with config options and not
mentioning it, part of the solution could be to require users to submit
their .config files when reporting issues. In such a case, having the
kernel version in there too would actually be better than relying on
users mentioning the fact that they edited their Makefiles...
Board platform and driver files/patches *depends* on a specific
kernel version so kernel version configuration as you proposed
would depend on luck for the users unless we provide the required
patches for every kernel version.
OTOH your idea could work if all boards supported by OpenWRT
reside on the upstream kernel so we don't need to test and
patch for every kernel release.
--
Otto
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
