El 2013-03-28 a las 03:56 -0700, Luis R. Rodriguez escribió: > On Thu, Mar 28, 2013 at 3:40 AM, Camaleón <noelamac@xxxxxxxxx> wrote: > > Now you say... can you please tell me -in user's parlance terms so I can > > understand it- what's the difference between "brcmsmac" from the stock > > kernel modules and this one from "compat-drivers"? I mean, what's the > > difference from a user's POV and from kernel hacker POV. Are they > > related? Are they going to me merged somehow? What's the goal of having > > both? > > The releases annotated with a date come from linux-next. While Linus > is whipping people in shape for the RC releases in preparation for the > first official release we hounds still do some development. During the > RC cycle only regression fixes get merged into Linus' tree as well a > shiny new drivers as they do not regress. The development cycle > continues on without Linus. Stephen Rothwell maintains a tree that > sucks all development trees together daily, this is called linux-next. > We use linux-next for compat-drivers given that we backport not just > wireless but also drm. So by you using dated compat-drivers releases > you are using what's currently being developed and will likely hit > 3.10. Mmm... it resembles to me like Debian's own release cycle where the "testing" branch would be like the drivers included at stock kernel and "unstable" would be similar to what compat-drivers are aimed for → the next hit. Well, more or less :-) Thanks for the explanation. Now awaiting for "git clone" ends its job. Greetings, -- Camaleón -- 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
