Hi Geert,
Now my git skills have been growing, I created two new branches:
- m68k-v2.6.29
- queue
Cool...
I had to fix a merge conflict in atari_defconfig and multi_defconfig
when pulling the m68k-v2.6.29 branch (EtherNEC builtin vs. module, which is the
correct setting?). Looks like I better restart from a fresh clone just for the
Debian stuff.
m68k-v2.6.29 contains commits from the following topic branches:
- for-2.6.30
Already taken by Linus, incl. mac-swim
- atari-aranym
- atari-ethernat
- atari-ethernec
- atari-scc
- atari-fat
Should this be dropped? Last time nobody spoke up to care about it
My problem with FAT as I remember it was the limitation on the cluster size to
be less or equal to the MMU page size in 2.6. My FAT filesystems are all
configured the wrong way... so the cluster size is too big and I could never
test the FAT modifications in a meaningful way.
I've reformatted one of the IDE disks on my Falcon in the meantime - I'll look
into that problem over Easter.
And a few things from master, the continuous development branch:
- atari mouse/keyboard fixes (are they complete? IIRC not yet)
There's a bit of Eiffel emulation code missing (mouse wheel IIRC) that I could
not test on ARAnyM at that time. My development tree has the necessary bits
already, I just need to test them. The mouse driver (input driver part) looks
incredibly messy as a result of all this, and could need a review.
If you (talking to `owners' of the stuff on the big topic branches now ;-) think
something is finished and ready for upstream, I can squash the commits together
using `git rebase -i' and submit them upstream...
Hint, hint ... what's the policy regarding driver duplication these days?
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
