<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] [lsb-discuss] [fedora-arm] ARM summit at Plumbers	2011
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Blsb-discuss%5D%20%5Bfedora-arm%5D%20ARM%20summit%20at%20Plumbers%0A%092011&In-Reply-To=%3C20110826213641.GA8671%40www5.open-std.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="007586.html">
   <LINK REL="Next"  HREF="007493.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] [lsb-discuss] [fedora-arm] ARM summit at Plumbers	2011</H1>
    <B>keld at keldix.com</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Blsb-discuss%5D%20%5Bfedora-arm%5D%20ARM%20summit%20at%20Plumbers%0A%092011&In-Reply-To=%3C20110826213641.GA8671%40www5.open-std.org%3E"
       TITLE="[Mageia-dev] [lsb-discuss] [fedora-arm] ARM summit at Plumbers	2011">keld at keldix.com
       </A><BR>
    <I>Fri Aug 26 23:36:41 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="007586.html">[Mageia-dev] [fedora-arm] ARM summit at Plumbers 2011
</A></li>
        <LI>Next message: <A HREF="007493.html">[Mageia-dev] Fwd: [Mageia-discuss] PROPOSAL: so,	you are already contributor, do you want to be maintainer?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#7587">[ date ]</a>
              <a href="thread.html#7587">[ thread ]</a>
              <a href="subject.html#7587">[ subject ]</a>
              <a href="author.html#7587">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>I would relly like the dscussion to go on widely as it is now.
Otherwise I would probably not follow this interesting discussion.

best regards
keld

On Fri, Aug 26, 2011 at 10:02:09PM +0100, Luke Kenneth Casson Leighton wrote:
&gt;<i> russell, good to hear from you.
</I>&gt;<i> 
</I>&gt;<i> can i recommend, that although this is a really wide set of
</I>&gt;<i> cross-posting on a discussion that underpins pretty much everything
</I>&gt;<i> (except gnu/hurd and minix) because it's linux kernel, that, just as
</I>&gt;<i> steve kindly advised, we keep this to e.g.
</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">cross-distro at lists.linaro.org</A>?  i'll be doing that from now on [after
</I>&gt;<i> this] perhaps including arm-netbooks as well, but will be taking off
</I>&gt;<i> all the distros.
</I>&gt;<i> 
</I>&gt;<i> so - folks, let's be clear: please move this discussion to
</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">cross-distro at lists.linaro.org</A>, and, if it's worthwhile discussing in
</I>&gt;<i> person, please do contact steve, so he can keep the slot open at the
</I>&gt;<i> Plumbers 2011 summit.
</I>&gt;<i> 
</I>&gt;<i> On Fri, Aug 26, 2011 at 5:35 PM, Russell King - ARM Linux
</I>&gt;<i> &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">linux at arm.linux.org.uk</A>&gt; wrote:
</I>&gt;<i> &gt; On Fri, Aug 26, 2011 at 11:11:41AM -0500, Bill Gatliff wrote:
</I>&gt;<i> &gt;&gt; As such refactoring consolidated larger and larger chunks of kernel
</I>&gt;<i> &gt;&gt; code, new designs would gravitate towards those consolidated
</I>&gt;<i> &gt;&gt; implementations because they would be the dominant references.
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; Don't bet on it. ??That's not how it works (unfortunately.)
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; Just look at the many serial port inventions dreamt up by SoC designers -
</I>&gt;<i> &gt; everyone is different from each other. ??Now consider: why didn't they use
</I>&gt;<i> &gt; a well established standard 16550A or later design?
</I>&gt;<i> 
</I>&gt;<i>  *sigh* because they wanted to save power.  or pins.  or... just be
</I>&gt;<i> bloody-minded.
</I>&gt;<i> 
</I>&gt;<i> &gt; This &quot;need to be different&quot; is so heavily embedded in the mindset of the
</I>&gt;<i> &gt; hardware people that I doubt &quot;providing consolidated implementations&quot;
</I>&gt;<i> &gt; will make the blind bit of difference.
</I>&gt;<i> 
</I>&gt;<i>  i think... russell... after they are told, repeatedly, &quot;no, you can't
</I>&gt;<i> have that pile of junk in the mainline linux kernel, Get With The
</I>&gt;<i> Programme&quot;, you'd think that, cumulatively if they end up having to
</I>&gt;<i> maintain a 6mb patch full of such shit, they _might_ get with the
</I>&gt;<i> programme?
</I>&gt;<i> 
</I>&gt;<i>  and if they don't, well.... who honestly cares?  if they don't, it's
</I>&gt;<i> not *your* problem, is it?  _they_ pay their employees to continue to
</I>&gt;<i> main a pile of junk, instead of spongeing off of _your_ time (and
</I>&gt;<i> linus's, and everyone else's in the Free Software Community).
</I>&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i> &gt; ??I doubt that hardware people
</I>&gt;<i> &gt; coming up with these abominations even care one bit about what's in
</I>&gt;<i> &gt; the kernel.
</I>&gt;<i> 
</I>&gt;<i>  then don't f******g make it _your_ problem, or anyone else's, upstream!! :)
</I>&gt;<i> 
</I>&gt;<i>  this is the core of the proposal that i have been advocating: if it's
</I>&gt;<i> &quot;selfish&quot;, i.e. as bill and many many others clearly agree with &quot;if
</I>&gt;<i> the bang-per-buck ratio is on the low side&quot; then keep it *out* the
</I>&gt;<i> mainline linux kernel...
</I>&gt;<i> 
</I>&gt;<i>  ... and that really is the end of the matter.
</I>&gt;<i> 
</I>&gt;<i> the sensible people that i've been talking to about this are truly
</I>&gt;<i> puzzled as to why the principles of &quot;cooperation and collaboration&quot;
</I>&gt;<i> behind free software are just being... completely ignored, in
</I>&gt;<i> something as vital as The Linux Kernel, and they feel that it's really
</I>&gt;<i> blindingly obvious that the &quot;bang-per-buck&quot; ratio of patches to
</I>&gt;<i> mainline linux kernel need to go up.
</I>&gt;<i> 
</I>&gt;<i>  so the core of the proposal that is the proposed
</I>&gt;<i> &quot;selfish-vs-cooperation patch policy&quot; is quite simple: if the patch
</I>&gt;<i> has _some_ evidence of collaboration, cooperation, refactoring,
</I>&gt;<i> sharing - *anything* that increases the bang-per-buck ratio with
</I>&gt;<i> respect to the core fundamental principles of Free Software - it goes
</I>&gt;<i> to the next phase [which is technical evaluation etc. etc.].
</I>&gt;<i> otherwise, it's absolutely out, regardless of its technical
</I>&gt;<i> correctness, and that's the end of it.
</I>&gt;<i> 
</I>&gt;<i>  the linux kernel mainline source tree should *not* be a
</I>&gt;<i> dumping-ground for a bunch of selfish self-centred pathological
</I>&gt;<i> profit-mongering corporations whose employees end up apologising in
</I>&gt;<i> sheer embarrassment as they submit time-pressured absolutely shit
</I>&gt;<i> non-cooperative and impossible-to-maintain code.
</I>&gt;<i> 
</I>&gt;<i>  you're not the only one, russell, who is pissed off at having to tidy
</I>&gt;<i> up SoC vendors' patches.  there's another ARM-Linux guy, forget his
</I>&gt;<i> name, specialises in samsung: two years ago he said that he was
</I>&gt;<i> getting fed up with receiving yet another pile of rushed junk... and
</I>&gt;<i> that's *just* him, specialising in samsung ARM SoCs!
</I>&gt;<i> 
</I>&gt;<i> we're just stunned that you, the recipient of _multiple_ SoC vendors
</I>&gt;<i> piles of shite, have tolerated this for so long!
</I>&gt;<i> 
</I>&gt;<i> anyway - i've endeavoured to put together some examples, in case
</I>&gt;<i> that's not clear: i admit it's quite hard to create clear examples,
</I>&gt;<i> and would greatly appreciate help doing so.  i've had some very much
</I>&gt;<i> appreciated help from one of the openwrt developers (thanks!)
</I>&gt;<i> clarifying by creating another example that's similar to one which
</I>&gt;<i> wasn't clear.
</I>&gt;<i> 
</I>&gt;<i>    <A HREF="http://lkcl.net/linux/linux-selfish.vs.cooperation.html">http://lkcl.net/linux/linux-selfish.vs.cooperation.html</A>
</I>&gt;<i> 
</I>&gt;<i> this should be _fun_, guys.  it shouldn't be a chore.  if you're not
</I>&gt;<i> enjoying it, and not being paid, tell the people who are clearly
</I>&gt;<i> taking the piss to f*** off!
</I>&gt;<i> 
</I>&gt;<i>  but - i also would like to underscore this with another idea: &quot;lead
</I>&gt;<i> by example&quot; (which is why i've kept the large cross-distro list)  we -
</I>&gt;<i> the free software community - are seeing tons of nice lovely android
</I>&gt;<i> tablets, tons of nice lovely expensive bits of big iron and/or x86
</I>&gt;<i> laptops, and only in very small areas (OpenRD Ultimate, GuruPlug,
</I>&gt;<i> Pandaboard, IMX53QSB, Origen) are our needs for actual hardware which
</I>&gt;<i> _we_ want (and i'm *not* being presumptious here - i'm inviting people
</I>&gt;<i> to *say* what they want) just aren't being met.
</I>&gt;<i> 
</I>&gt;<i>  who wants a bloody 800x600 VIA VunnnderMedia ARM9 350mhz tablet, to
</I>&gt;<i> do linux kernel and gnu/linux distribution development on, _anyway_???
</I>&gt;<i>   and who the hell wants only 512mb of RAM (iMX51).  and who in their
</I>&gt;<i> right fucking mind dreamed up that 1024x600 LCD panel size?
</I>&gt;<i> 
</I>&gt;<i>  so here's what i propose:
</I>&gt;<i> 
</I>&gt;<i>  we, The Free Software Community, want Our Figureheads (linus, bruce,
</I>&gt;<i> alan, russell) to call us to arms (so to speak), to band together a la
</I>&gt;<i> KickStarter <A HREF="http://kickstarter.org">http://kickstarter.org</A> (or other), so that we can create
</I>&gt;<i> the hardware platform(s) that *we* want, and, in the process, can take
</I>&gt;<i> the opportunity to sort out the Linux Kernel mainline tree in the
</I>&gt;<i> process (learning by doing, doing by leading, leading by example etc.
</I>&gt;<i> etc.)
</I>&gt;<i> 
</I>&gt;<i>  apart from anything - and this goes to you, linus and russell - i
</I>&gt;<i> think that you would be much happier taking a break from doing git
</I>&gt;<i> patch conflict management, _actually_ getting down and dirty with some
</I>&gt;<i> real device driver writing, and i think you'd be much happier doing
</I>&gt;<i> that knowing that the device you were writing those kernel drivers for
</I>&gt;<i> was something that actual real free software developers really really
</I>&gt;<i> wanted.
</I>&gt;<i> 
</I>&gt;<i>  now, as i said above: i don't _dare_ to presume that i know what
</I>&gt;<i> actual real free software developers want, in terms of hardware, but
</I>&gt;<i> there's a small sampling on the debian-arm mailing list... let me drop
</I>&gt;<i> you roughly in the middle of it, here:
</I>&gt;<i> <A HREF="http://lists.debian.org/debian-arm/2011/08/msg00045.html">http://lists.debian.org/debian-arm/2011/08/msg00045.html</A>  mostly that
</I>&gt;<i> was focussed around those little engineering boards (panda, IMX53QSB,
</I>&gt;<i> origen etc.) but my aim here is to get people to think:
</I>&gt;<i> 
</I>&gt;<i>  what hardware, which is fully free-software-compliant, that you would
</I>&gt;<i> buy and recommend to others, that could also be attractive in
</I>&gt;<i> mass-volume, do _you_ want to see, that would be useful to _you_?
</I>&gt;<i> 
</I>&gt;<i>  i'm getting fed up of seeing stuff come out of factories that's
</I>&gt;<i> completely useless.  or gpl-violating.  and/or requires
</I>&gt;<i> reverse-engineering.
</I>&gt;<i> <A HREF="http://lkcl.net/linux/ideal-vs-reality.of.product.development.html">http://lkcl.net/linux/ideal-vs-reality.of.product.development.html</A> for
</I>&gt;<i> some background.
</I>&gt;<i> 
</I>&gt;<i>  as a free software developer, what hardware do YOU want?
</I>&gt;<i> 
</I>&gt;<i>  answers on this one to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">arm-netbooks at lists.phcomp.co.uk</A> (subscription
</I>&gt;<i> required, please remember)
</I>&gt;<i> 
</I>&gt;<i>  and, lastly - linus, russell, alan, bruce: there are people out there
</I>&gt;<i> who would really appreciate if you could take up this call.  not just
</I>&gt;<i> me.  we'd like to see you using your skills, and actually be happy and
</I>&gt;<i> enjoy doing nitty-gritty linux kernel development, to the benefit of
</I>&gt;<i> the free software community, instead of turning into patch
</I>&gt;<i> junkies^H^H^H^H^H^Hmonkeys^H^H^H^H^H^H^Hmanagers.
</I>&gt;<i> 
</I>&gt;<i>  l.
</I>&gt;<i> _______________________________________________
</I>&gt;<i> lsb-discuss mailing list
</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">lsb-discuss at lists.linux-foundation.org</A>
</I>&gt;<i> <A HREF="https://lists.linux-foundation.org/mailman/listinfo/lsb-discuss">https://lists.linux-foundation.org/mailman/listinfo/lsb-discuss</A>
</I></PRE>






<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="007586.html">[Mageia-dev] [fedora-arm] ARM summit at Plumbers 2011
</A></li>
	<LI>Next message: <A HREF="007493.html">[Mageia-dev] Fwd: [Mageia-discuss] PROPOSAL: so,	you are already contributor, do you want to be maintainer?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#7587">[ date ]</a>
              <a href="thread.html#7587">[ thread ]</a>
              <a href="subject.html#7587">[ subject ]</a>
              <a href="author.html#7587">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>