what is the proper tree to be using these days for a 2.6 kernel on
8xx? for the longest time, i've used the "bk" checkout from
bkbits.net, but i see others now working with what looks like the
latest stock 2.6.x release.
what's the status on patches that were submitted against the bk
tree? have they been pushed upstream? etc, etc.
rday
On Mar 25, 2005, at 4:19 PM, Robert P. J. Day wrote:
what is the proper tree to be using these days for a 2.6 kernel on
8xx? for the longest time, i've used the "bk" checkout from
bkbits.net, but i see others now working with what looks like the
latest stock 2.6.x release.
I just use the latest kernel.org tree for everything. If I'm submitting
a patch, or working with someone else, I use the bk tree just to
be that little more up to date.
-- Dan
On Fri, 25 Mar 2005, Dan Malek wrote:
On Mar 25, 2005, at 4:19 PM, Robert P. J. Day wrote:
quoted
what is the proper tree to be using these days for a 2.6 kernel
on 8xx? for the longest time, i've used the "bk" checkout from
bkbits.net, but i see others now working with what looks like the
latest stock 2.6.x release.
I just use the latest kernel.org tree for everything. If I'm
submitting a patch, or working with someone else, I use the bk tree
just to be that little more up to date.
i just downloaded the 2.6.11-5 kernel source and was a bit nonplussed
to discover that "8xx" wasn't in the list of choices for processor,
until i noticed in the Kconfig file that 8xx depends on "BROKEN". oh,
my. :-) live and learn.
rday