Hi,
So, rather than working with the head of the repo, we are working with
a specific snapshot. It would have been nice to have noted that,
rather than give a bunch of steps with no real explanation of the
goal.
Yeah, the head is always in flux. For best odd's stay with branches
tagged like: v2.6.28-omap1
Why not just pull the desired branch directly, rather than all of
these gyrations?
You could do that, I'm just not a git expert.
I see a large amount of video patches, logo patches, and things OTHER
than USB here. While those things may be needed, they do complicate
trying to work out "what I need" vs. "other random stuff I don't care
about".
That diff is just all the patches the openembedded group applied to
that git checkout to create 2.6.28-r17.
For reference v2.6.28-79d042a-oer17 is Commit:
http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=df49f5e7f5a14c6736806f3163787608c958f4c9
Which contains this for linux-omap_2.6.28.bb :
http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/recipes/linux/linux-omap_2.6.28.bb&id=df49f5e7f5a14c6736806f3163787608c958f4c9
Note: (in linux-omap_2.6.28.bb)
"SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git;branch=omap-2.6.28;protocol=git
\" -> git tree your using
"SRCREV = "79d042a081d3e467c735bb0d9569ed6296f85a3c" " -> git checkout 79d042a
Then all the patches listed: which i've combined for my own purposes
into a single diff.
Too work out what you need vs random stuff, start with that checkout
and only apply some of the patches listed in the linux-omap_2.6.28.bb
file.
I'm just keeping things compatible to hopefully some day have sgx/dsp
on debian/ubuntu/etc.
wgethttp://rcn-ee.homeip.net:81/dl/omap/beagle/v2.6.28-79d042a-oer17/defc…
OK, now we are getting what I asked for - a configuration set to
compare to my configuration.
------
Now, looking at the patch set, it would seem to me that the fact that
big chunks of the USB drivers are being patched would indicate that
the current linux-omap-2.6 tip DOES NOT support the hardware on the
Beagleboard Rev C by default, and that a set of patches are needed to
support the BeagleBoard Rev C vs. the BeagleBoard Rev B.
Is that a correct summary?
Current linux-omap-2.6 tip is to volatile to say either statement.
But for the time being "full or 100%" support of the beagle's isn't in
this tree yet.
Regards,