Re: Would you like to get the working source tree ?

I finally got my x50v to boot.
It only worked once I put everything on SD (which I borrowed from my new
camera).
So I'd like to get on the same page ....

In other words what kernel versions, and modifications.
(where, tags [HEAD], versions, anything else).

Aside: Request for any kernel, initrd made available... md5sum them.

Fisherss, Richard, and others what was your original kernel source?
Mine was 2.6.11hh from CVS on handhelds.

Anyone on this list with write perms to the kernel26 tree on handhelds?

I guess co-ordinating with jamey would help, so we can tag
our questionable changes so we can use them for development without them being
used elsewhere. I don't know if he'd want another branch or not.
X50-HEAD .

http://www.handhelds.org/sources.html
The CVS tree is synced (merged) with the kernel.org (tag kernel-org)
so we get other changes too. I have no clue who is pushing things
back the other direction.
Richard was talking about 2.6.13 having desired changes for arm.

Trivial Question: why is there a kernel26/arch/arm26 directory and
a kernel26/arch/arm directory?

If you don't know what "you" built from, I can probably deduce what it,
and get it synced by date or release.

The rest of this E-mail is just gibberish mostly to myself, since my use
of CVS is a crusted.

        J.Currey

<CVS gibberish>
A plan: check-out get the (virgin) source version of your kernel.
Diff changes from "your" source tree.
(I need tags, versions etc).

Plan example:
CVSROOT=:pserver:anoncvs_at_cvs.handhelds.org:/cvs
the password is: anoncvs
cvs login

do a "cvs checkout" by tag label [-r tag] or by date [-D 1972-09-24]
cvs co -D 2005-06-15 kernel26

copy, then clean tree - copy .config off etc . make distclean
copy the cleaned tree on top of checked out version. I suggest using
"rsync --dry-run -av mycopy cocopy" to report changes, so I don't get
any ugly surprizes.

(note: new files would still need cvs add, and changes, a commit
but we can't commit... at least that what most women around here
say about men :-) )

then do an update with the new tag you want (and some option [-A] to forget the
-D checkout restriction)
something like "cvs update -r newtag"
the -d is to get new directories (cvs won't otherwise, even though it is
recursive by default)
the -A is to ditch the -D sticky tag you had from the checkout
if there are other development branches to add, use addition -j
I think K2-6-12 is already merged... so this is redundant, and the
X50-HEAD fictional but here for demonstration.
cvs update -A -d -r HEAD
if
cvs update -A -d -r HEAD -j K2-6-12 -j X50-HEAD
or
cvs update -j branch-name
is preferred for eliminating deleted files...
cvs update -A -d -r MAIN
cvs update -A -d -r MAIN -j K2-6-12 -j X50-HEAD

to see your changes, then diff down the tree
cvs diff -r newtag

If you checked out the default from cvs
then a simple
cvs update
will work in the checkout directory and can be used from now on.

Subversion is nicer in that files can be moved around without a remove
and add.
I wish that cvsweb or viewcvs would have a nice graphical view of
the branches and tags. So you can easily tell which branch(s) you
want, and if you need to -j join another branch in.

<\CVS gibberish>
Received on Wed Sep 07 2005 - 22:30:36 EDT