move marvell firmware tarballs out of OE repo?

move marvell firmware tarballs out of OE repo?

[Robert P. J. Day]

  (this is the first in a small number of postings to clarify the
purpose of some tarballs in the OE dev repository, and whether they
could be moved elsewhere.)

  the tarballs:

./recipes/firmwares/marvell-gspi-fw/9.70.3-p37.tar.gz
./recipes/firmwares/marvell-sdio-fw/9.70.3-p37.tar.gz

  are these not downloadable from somewhere, or could they be moved
into an OE repo?

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

Re: move marvell firmware tarballs out of OE repo?

[Rolf Leggewie]

Robert P. J. Day wrote:
>   (this is the first in a small number of postings to clarify the
> purpose of some tarballs in the OE dev repository

DUDE!

Why are you again wasting everybody's time?  I thought you wanted to use
git log yourself to find out and then targeting the relevant people in a
focused fashion instead of flooding the list with this junk?

BTW, re your suggestion to add READMEs.  Well, I guess that is fine.
But for people who aren't too lazy to use "git log --find-copies-harder"
the answers are often right there.

Re: move marvell firmware tarballs out of OE repo?

[Paul Menzel]

[-- Attachment #1: Type: text/plain, Size: 1706 bytes --]

Am Sonntag, den 17.01.2010, 20:44 +0100 schrieb Rolf Leggewie:
> Robert P. J. Day wrote:
> >   (this is the first in a small number of postings to clarify the
> > purpose of some tarballs in the OE dev repository
> 
> DUDE!
> 
> Why are you again wasting everybody's time?  I thought you wanted to use
> git log yourself to find out and then targeting the relevant people in a
> focused fashion instead of flooding the list with this junk?

(Very polite! ;-))

If you look at his other messages you will see that this was probably
not Robert’s intention and that he did his best.

> BTW, re your suggestion to add READMEs.  Well, I guess that is fine.
> But for people who aren't too lazy to use "git log --find-copies-harder"
> the answers are often right there.

(Again not a nice implication.)

Anyways looking at the relevant commit

        $ git log --follow recipes/firmwares/marvell-gspi-fw/9.70.3-p37.tar.gz
        commit 7ea3026aa3c216f9943711771e9245b2b6ff7c84
        Author: Marcin Juszkiewicz <marcin@buglabs.net>
        Date:   Thu Apr 23 14:01:35 2009 +0200
        
            marvel-gspi-fw: added firmware for WiFi bugmodule
            
            This is firmware for not-yet-released-into-sales wifi/bt bugmodule.

it does not explicitly say, why the firmware cannot be made public
somewhere or if it ever will be available.

Having “perfect” commit messages in OE seems to still be a current
topic, so having a README file is certainly an idea I support at least
for the files the commit messages can not be changed anymore. This would
definitely help me and lower the barrier/learning curve to get to know
OE.


Thanks,

Paul

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: move marvell firmware tarballs out of OE repo?

[Rolf Leggewie]

Paul Menzel wrote:
> Anyways looking at the relevant commit
[...]
> it does not explicitly say, why the firmware cannot be made public
> somewhere or if it ever will be available.

No, nobody was suggesting it would.  But it does list Marcin's address.
 So, he can be contacted directly instead of needlessly bothering
everybody on this list with this.

Robert continues to ignore helpful advice given to him and feels he is
entitled to immediate support.  I, for one, don't need to waste my time
for that kind.  And, yes, he is (or should I rather say, was) wasting my
time and after a while, I really don't appreciate that.

/me shuts up now

Re: move marvell firmware tarballs out of OE repo?

[Marcin Juszkiewicz]

Dnia poniedziałek, 18 stycznia 2010 o 01:31:13 Rolf Leggewie napisał(a):
> Paul Menzel wrote:
> > Anyways looking at the relevant commit

> > it does not explicitly say, why the firmware cannot be made public
> > somewhere or if it ever will be available.
 
> No, nobody was suggesting it would.  But it does list Marcin's address.
>  So, he can be contacted directly instead of needlessly bothering
> everybody on this list with this.

And Robert took the worst timing for such mails - I do not know how others but 
I do not read all mails during weekend.

His first mail was at 20:42 Saturday for most of Europe. Most of people do not 
use computers at that time but rather watch movie, goes to party etc. He did 
not got any answer during his day (he has -6h difference to Europe) so at 4 am 
on Sunday he started to send emails to ML (with proper people in Cc:) about 
that. For me it was bad choice of timing, but maybe Robert is a machine more 
then man?

On Sunday morning I sent mail with info why several tarballs are present in 
metadata. He was probably sleeping at that time. I just hope that in 6 hours 
from now Robert will be able to reply to this mail.

Regards, 
-- 
JID:      hrw@jabber.org
Website:  http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz

Re: move marvell firmware tarballs out of OE repo?

[Robert P. J. Day]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1907 bytes --]

On Mon, 18 Jan 2010, Marcin Juszkiewicz wrote:

> Dnia poniedziałek, 18 stycznia 2010 o 01:31:13 Rolf Leggewie napisał(a):
> > Paul Menzel wrote:
> > > Anyways looking at the relevant commit
>
> > > it does not explicitly say, why the firmware cannot be made public
> > > somewhere or if it ever will be available.
>
> > No, nobody was suggesting it would.  But it does list Marcin's address.
> >  So, he can be contacted directly instead of needlessly bothering
> > everybody on this list with this.
>
> And Robert took the worst timing for such mails - I do not know how
> others but I do not read all mails during weekend.

  slacker.  :-)

> On Sunday morning I sent mail with info why several tarballs are
> present in metadata. He was probably sleeping at that time. I just
> hope that in 6 hours from now Robert will be able to reply to this
> mail.

  or sooner.  in any event, i did post earlier that i understand there
will be rare and unusual circumstances where content will have to be
incorporated with the OE repo.  in cases like that, it would be handy
to have a short README file in the corresponding recipes directory
explaining the rationale for it, and perhaps even the circumstances
under which that content might someday be removed and actually
downloaded, just so anyone else might recognize when that can be done.

  that's entirely up to the people responsible for those tarballs.

  movin' on ...

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================