public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Konstantinos Margaritis <markos@debian•gr>
To: Hollis Blanchard <hollis@penguinppc•org>,
	Linas Vepstas <linas@austin•ibm.com>,
	Matt Sealey <matt@genesi-usa•com>
Cc: 'Olof Johansson' <olof@lixom•net>,
	'linuxppc-dev list' <linuxppc-dev@ozlabs•org>,
	'Paul Mackerras' <paulus@samba•org>,
	Konstantinos Margaritis <markos@debian•org>
Subject: Re:Re: AltiVec in the kernel
Date: Sat, 22 Jul 2006 02:38:13 -0700 (PDT)	[thread overview]
Message-ID: <16081441.1153561129049.JavaMail.flurry@flurry4.flurrymail.com> (raw)
In-Reply-To: 11187

(Writing this on a wap mobile phone)

actually, i knew about steve's effort as i am subscribed to glibc-ports. the problem is i am doing my military service this whole period (right now i am a sentry guard at an oupost somewhere in rhodes :-). the good news is that in about a month or less i'll return close to my home and i intend to get back to work asap. but till then i'm stuck here.
 
konstantinos

_____________________________
I sent this message from my cell phone using flurry.
Click here to get your email and news on your cell phone for free: 
http://www.flurry.com

--- Original Message ---
Date: Fri Jul 21 14:30:56 PDT 2006
From: Hollis Blanchard <hollis@penguinppc•org>
To: Linas Vepstas <linas@austin•ibm.com>, Matt Sealey <matt@genesi-usa•com>
Subject: Re: AltiVec in the kernel
---


On Fri, 21 Jul 2006 11:51:30 -0500, "Linas Vepstas"
<linas@austin•ibm.com> said:
> On Fri, Jul 21, 2006 at 09:42:32AM -0500, Matt Sealey wrote:
> > http://www.freevec.org/ 
> > 
> > Been there for months, before the glibc thing. Most of the functions
> > are ready. Anyone can bugfix this. The beauty of GPL. The ugly part
> > is.. we've had this there for months. Nobody has contributed a single
> > update or bugfix or even a performance test as far as I know.
> 
> Sounds like a problem of advertising and communications.  This is
> kind of "under the radar" for most users and developers. It needs to
> work out-of-the-box, most people, even those with interest in
> performance, will not even be aware of the possibility to tne this.

It is difficult to make sure every OSS developer is notified of all work
they may be interested in...

However, I have noticed a trend where Genesi people seem to think
everybody pays attention to their websites (and the same could be said
for Debian and other subcultures). In this case there actually have been
other people aware of this project, but not very many. Considering all
the traffic about it on ppczone.org, people looking for exposure for
their project may want to look beyond PPCZone.

> It should be folded into glibc. It is up to the altivec product vendor
> to nag the glibc folks into folding it in. This task could be as hard
> as writing the code in the first place.

Konstantinos is aware of Steve's glibc project and has indicated he'll
try to contribute to it.

To be fair, probably not many people have heard of Steve's project
either. I doubt Konstantinos would have heard of it if I hadn't
mentioned it.

-Hollis

                 reply	other threads:[~2006-07-22 10:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16081441.1153561129049.JavaMail.flurry@flurry4.flurrymail.com \
    --to=markos@debian$(echo .)gr \
    --cc=hollis@penguinppc$(echo .)org \
    --cc=linas@austin$(echo .)ibm.com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=markos@debian$(echo .)org \
    --cc=matt@genesi-usa$(echo .)com \
    --cc=olof@lixom$(echo .)net \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox