[Arm-netbook] Flashing the NAND

[Siarhei Siamashka]

On Mon, 9 Dec 2013 09:13:04 +0000
joem <joem at martindale-electric.co.uk> wrote:

> > on it. But after finally going public, instantly venting out
> > your frustration and spitting in the well you are drinking from
> > does not look very civilized. I guess here is one more related
> > rant from you:
> > 
> >     https://plus.google.com/u/0/+AaronSeigo/posts/JDdvLDJESm5
> 
> That is not what I class as a rant.

Well, according to one of the definitions at
    https://www.vocabulary.com/dictionary/rant

"A rant is an argument that is fueled by passion, not shaped by facts."

The use of foul language in that G+ post indicates some sort of
passion. But fine, let's consider it not a rant.

> This below is what I call a rant:
> 
> > So far I can see that it is you, who is having issues with poor
> > communication 

Then this is not a rant either. What exactly is wrong with this
statement? Aaron himself admitted that the improvements of
communication are needed. This was all your nice and friendly internal
arm-netbook eoma68 talk about improving your software development
processes.

Except that it also touched linux-sunxi wiki, linux-sunxi defconfigs
and the mali400 graphics drivers support on sunxi hardware. And kinda
implied that a poor job is also being done there.

Was there even any effort made to communicate with the linux-sunxi
community? The kernel sources are available on github (and the
Improv is already using them):
    https://github.com/linux-sunxi/linux-sunxi

The github page links to the linux-sunxi wiki:
    http://linux-sunxi.org/Linux

The linux-sunxi wiki has a link to the mailing list among
other information:
    http://linux-sunxi.org/Mailing_list

For the OpenGL ES support in X11 on sunxi hardware, I have a project
page here, which happens to list some contact information and
describes the process of reporting issues:
    https://github.com/ssvb/xf86-video-fbturbo

Yes, the OpenGL ES issue has been successfully communicated via IRC.
Nice job. Still Aaron described dealing with this particular issue
using WTF word. Now I'm really curious what was my fault and how we
can improve from this point?


Joem, if you have nothing really constructive to say, please just don't
get in the way. And I actually have nothing more to add to this topic.
What had to be said, had already been said. Cheers.

-- 
Best regards,
Siarhei Siamashka