>Hi,
>
>NAK, we wont merge a huge pile of random patch churn in one big blob.
>please read the "submitting patches" guidelines
>
> John
What huge pile? Like I earlierly said, this is NOT dependant of _any_ of my
previous patches and this is 5K patch patching the following 4 files:
target/linux/brcm2708/Makefile b/target/linux/brcm2708/Makefile
target/linux/brcm2708/patches-3.12/001-change-version.patch
b/target/linux/brcm2708/patches-3.12/001-change-version.patch
target/linux/generic/config-3.12 b/target/linux/generic/config-3.12
target/linux/generic/patches-3.12/880-gateworks_system_controller.patch
b/target/linux/generic/patches-3.12/880-gateworks_system_controller.patch
If patch is unreadable because my mail program has sent it with incompatible
way, you can fetch the patch from:
https://sites.google.com/site/variousopenwrt/rpi-patch
Yeah, I have readed submitting patches, and I am lazy when submitting patches.
But I've been working few months now _alone_ trying to make OpenWrt on
Raspberry Pi
a distribution that really works; instead of being broken, also, I have taken
steps to build a package feed for OpenWrt on Raspberry Pi that would make
OpenWrt a distribution
for rpi that would be on a same level with other available distributions
available for rpi.
I know OpenWrt doesn't like native compilation, but it's enabled for x86 target
and I think rpi's got enough juice so it could also have native compilation
environment (optionally), but you don't like it, therefore I never have
suggested any of you to include my feed in the tree.
What my tree contains is pretty much listed here:
https://groups.google.com/forum/#!topic/raspberrypi-openwrt-dev/XR8sEP0WOCI
All my work consists of building this feed, compatibility patches, _working_
kernel, building of root fs(ext4) with populatefs I provided earlierly..
Some packages are my own hand writing, like rpi-update which is.. Well
rpi-update for OpenWrt, not dependant on git and.. My lighter weight version.
rpi-extendfs: like raspi-config, used to extend root filesystem.
populatefs: used for creating ext4 image for rpi(or any other arch) - allows
setting of desired ext4 flags and doesn't make a broken filesystem that starts
to loose it after 5500 occupied inodes..
It's been a lot of work and sometimes I see when _official_ openwrt developers
bug about that "they" rarely contribute to openwrt.. They can be anything from
dd-wrt to openwrt-rOOter.. Well, I gave OpenWrt support for usb dongles in
similar way that rOOter does (my work with ncm support) about a month, that
never got to mainstream.
It was a problem when I "first" published my kernel patch for rpi.. Now I
tryied to learn from it and send you a "better"- eh, smaller one. Re-shrunk it
even more. Still it seems to be a problem. I never take credit of these
contributions, only if I have truly written a app, I only add there my name and
sometimes not even there, only rpi-extendfs has my name on it's
about screen, and all this is for free, so I think I'm very humble..
So, I think that my contribution to OpenWrt fails since it doesn't gather
enough interest and I feel that all this is for nothing.
Let's forget it then if it's useless.. Can't be very important if a 5K patch is
considered as a churn of one big blob.
Real motivator, 2 lines of text for someone who has been working for months to
just contribute namelessly to a project so
it would be better, and for free. Well, no worries, now I'll find something
else to use my free time for.
-Oskari Rauta
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
