on top of v3.2.0 before you patch the local directories..
Nice, ugly mess isn't it?
I'm bound to screw this up 10 ways. Is the 3.6 patching process any
better/cleaner/easier?
Alternatively, if I use patch.sh, can I stay on top of updates without
doing a full download each time? In other words, would running
patch.sh twice in a row result in very little being downloaded?
on top of v3.2.0 before you patch the local directories..
Nice, ugly mess isn't it?
I'm bound to screw this up 10 ways. Is the 3.6 patching process any
better/cleaner/easier?
Yes, it's less of a massive un-maintable fork, as it's based on v3.6..
But much less support for Capes at this exact moment in time.
Alternatively, if I use patch.sh, can I stay on top of updates without
doing a full download each time? In other words, would running
patch.sh twice in a row result in very little being downloaded?
Once you run "./patch.sh" the first time it will "git clone" linus'
tree (1) so if you've already cloned that before, just do (exactly)
(i wasn't thinking when i named the directory "kernel" in a repo name
"kernel" opps, too late to ever fix that. )
and it'll pull your git objects from your already cloned directly,
instead via the internet.. (note, as this point, don't remember the
other clone, as your objects are shared)
If you DON'T have a previous clone.. Find some free-wifi, as you'll
need to download around 500-700Mb on the initial running of
"./patch.sh" but afterwards it'll just pull in the git objects..
(i wasn't thinking when i named the directory "kernel" in a repo name
"kernel" opps, too late to ever fix that. )
and it'll pull your git objects from your already cloned directly,
instead via the internet.. (note, as this point, don't remember the
other clone, as your objects are shared)
If you DON'T have a previous clone.. Find some free-wifi, as you'll
need to download around 500-700Mb on the initial running of
"./patch.sh" but afterwards it'll just pull in the git objects..
(i wasn't thinking when i named the directory "kernel" in a repo name
"kernel" opps, too late to ever fix that. )
and it'll pull your git objects from your already cloned directly,
instead via the internet.. (note, as this point, don't remember the
other clone, as your objects are shared)
If you DON'T have a previous clone.. Find some free-wifi, as you'll
need to download around 500-700Mb on the initial running of
"./patch.sh" but afterwards it'll just pull in the git objects..
I ran patch.sh for 3.6, but when it completed I realized there is no
.config file in kernel/ and 'make am335x_evm_config' doesn't work as
it did for 3.1. Am I supposed to import my 3.1 .config and 'make
oldconfig'?