Re: Status of marvell-ipp

2014-10-08 Thread James B
On Wed, 8 Oct 2014 16:19:19 +1100
James Cameron qu...@laptop.org wrote:

 
 The marvell-ipp binaries we host for Fedora builds are not public.
 
 olpc-os-builder can be configured to pull private resources, and the
 Wiki page describes how that is done.

Thank you for the explanation.

 
 The marvell-ipp binaries we host for Android builds are public, as Ben
 has said.  There's a license file in the same directory.
 

Thank you. Android drivers are interesting but they aren't usable directly, we 
have to go a roundabout way to use it (using libhybris and whatnot). It's 
something of last resort if we don't have access to the Linux version; which in 
this case, we do (or do not, depending on the license... ).

 
 I doubt if the Fedora marvell-ipp binaries are distributable, given
 how they are currently hosted, and the text of the Wiki page.  These
 are closed source libraries provided by Marvell.

Well, closed-source does not always mean not-redistributable. For example, the 
Vivante 3D driver is a also another closed source drop from Marvell, but it is 
available in rpmdropbox (and I assume its licensing allows it so). Perhaps 
re-distributable (and being stored in public repository) is a too-strong word. 
The question really boils down to this: can the marvell-ipp be used in 
alternative distributions (that runs on OLPC) other than the official Fedora? 
And if yes, which whom (email address) can I ask to get them? 

 
 No, I work for OLPC in Miami, in the United States, not OLPC
 Australia.  I just happen to live in Australia.  ;-)  Confusing, I
 know.

Haha, yeah. Thanks for the explanation :)

 
 Good to know.
 
 Are there H.264 codecs and the like you can obtain from other places?

Well yes, ffmpeg or libav provides software decoder for h.264. I already have 
this in my current build, so it's not a problem really a problem, except for 
one thing: software decoding is slow. That's why I would like to get the 
hardware to do the decoding, and the only way to do hardware decoding is 
through marvell-ipp - there is no alternative, unfortunately.

cheers!

-- 
James B jamesbond3...@gmail.com
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Status of marvell-ipp

2014-10-08 Thread James Cameron
On Wed, Oct 08, 2014 at 08:42:26PM +0700, James B wrote:
 On Wed, 8 Oct 2014 16:19:19 +1100
 James Cameron qu...@laptop.org wrote:
 
  
  The marvell-ipp binaries we host for Fedora builds are not public.
  
  olpc-os-builder can be configured to pull private resources, and the
  Wiki page describes how that is done.
 
 Thank you for the explanation.
 
  
  The marvell-ipp binaries we host for Android builds are public, as Ben
  has said.  There's a license file in the same directory.
  
 
 Thank you. Android drivers are interesting but they aren't usable directly, 
 we have to go a roundabout way to use it (using libhybris and whatnot). It's 
 something of last resort if we don't have access to the Linux version; which 
 in this case, we do (or do not, depending on the license... ).
 
  
  I doubt if the Fedora marvell-ipp binaries are distributable, given
  how they are currently hosted, and the text of the Wiki page.  These
  are closed source libraries provided by Marvell.
 
 Well, closed-source does not always mean not-redistributable. For example, 
 the Vivante 3D driver is a also another closed source drop from Marvell, but 
 it is available in rpmdropbox (and I assume its licensing allows it so). 
 Perhaps re-distributable (and being stored in public repository) is a 
 too-strong word. The question really boils down to this: can the marvell-ipp 
 be used in alternative distributions (that runs on OLPC) other than the 
 official Fedora? And if yes, which whom (email address) can I ask to get 
 them? 

Your speculation is reasonable, and your questions are understood.
However, we don't have the resources to answer these questions, there
are other more important things for us to do, sorry.

If you can't determine a useful answer from what you have available,
then I suggest you stick with software decoders.

 
  
  No, I work for OLPC in Miami, in the United States, not OLPC
  Australia.  I just happen to live in Australia.  ;-)  Confusing, I
  know.
 
 Haha, yeah. Thanks for the explanation :)
 
  
  Good to know.
  
  Are there H.264 codecs and the like you can obtain from other places?
 
 Well yes, ffmpeg or libav provides software decoder for h.264. I already have 
 this in my current build, so it's not a problem really a problem, except for 
 one thing: software decoding is slow. That's why I would like to get the 
 hardware to do the decoding, and the only way to do hardware decoding is 
 through marvell-ipp - there is no alternative, unfortunately.
 
 cheers!
 
 -- 
 James B jamesbond3...@gmail.com

-- 
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Write-95 segmentation fault on Fedora 20 (OLPC:#12809)

2014-10-08 Thread James Cameron
Thanks, wasn't aware of repo.

Yes, at least one not upstream, dereference of NULL pointer in
XAP_UnixFrameImpl::_imRetrieveSurrounding_cb
(avoid-maliit-crash.patch).

There may be more.

Check my understanding; Write activity depends on abiword and
libabiword RPMs, and for OLPC OS 13.2 we used our own RPMs.

I shall review whether to reuse RPMs or port patches to the Fedora 20
RPMs.  Depending on user experience.

On Wed, Oct 08, 2014 at 04:44:58PM -0300, Gonzalo Odiard wrote:
 Looks like I will not have time to work on Write for a while..
 If anybody want to check, the spec and patches used in the F18 rpm are here 
 [1]
 In theory, all the patches should be already on abiword upstream,
 but would be good check.
 
 Gonzalo 
 
 [1] [1]https://git.sugarlabs.org/olpc-abiword-rpm/olpc-abiword-rpm
 
 On Fri, Oct 3, 2014 at 9:50 AM, Gonzalo Odiard [2]godi...@sugarlabs.org
 wrote:
 
  Ok, then I can do the release, the problem is not related with the
  changes. 
 
 Yes.
 
 How's Write going?  ;-)
 
 Nothing on that front. 
 
 --
 Gonzalo Odiard
 
 SugarLabs - Software for children learning 
 
 References:
 
 [1] https://git.sugarlabs.org/olpc-abiword-rpm/olpc-abiword-rpm
 [2] mailto:godi...@sugarlabs.org

-- 
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Write-95 segmentation fault on Fedora 20 (OLPC:#12809)

2014-10-08 Thread Gonzalo Odiard
On Wed, Oct 8, 2014 at 6:50 PM, James Cameron qu...@laptop.org wrote:

 Thanks, wasn't aware of repo.

 Yes, at least one not upstream, dereference of NULL pointer in
 XAP_UnixFrameImpl::_imRetrieveSurrounding_cb
 (avoid-maliit-crash.patch).

 There may be more.

 Check my understanding; Write activity depends on abiword and
 libabiword RPMs, and for OLPC OS 13.2 we used our own RPMs.


Yes. Is just one spec file and create both rpms.


 I shall review whether to reuse RPMs or port patches to the Fedora 20
 RPMs.  Depending on user experience.


Thanks!

Gonzalo


 On Wed, Oct 08, 2014 at 04:44:58PM -0300, Gonzalo Odiard wrote:
  Looks like I will not have time to work on Write for a while..
  If anybody want to check, the spec and patches used in the F18 rpm are
 here [1]
  In theory, all the patches should be already on abiword upstream,
  but would be good check.
 
  Gonzalo
 
  [1] [1]https://git.sugarlabs.org/olpc-abiword-rpm/olpc-abiword-rpm
 
  On Fri, Oct 3, 2014 at 9:50 AM, Gonzalo Odiard [2]godi...@sugarlabs.org
 
  wrote:
 
   Ok, then I can do the release, the problem is not related with
 the
   changes.
 
  Yes.
 
  How's Write going?  ;-)
 
  Nothing on that front.
 
  --
  Gonzalo Odiard
 
  SugarLabs - Software for children learning
 
  References:
 
  [1] https://git.sugarlabs.org/olpc-abiword-rpm/olpc-abiword-rpm
  [2] mailto:godi...@sugarlabs.org

 --
 James Cameron
 http://quozl.linux.org.au/




-- 
Gonzalo Odiard

SugarLabs - Software for children learning
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Status of marvell-ipp

2014-10-08 Thread James B
On Thu, 9 Oct 2014 07:17:03 +1100
James Cameron qu...@laptop.org wrote:

  
  Well, closed-source does not always mean not-redistributable. For example, 
  the Vivante 3D driver is a also another closed source drop from Marvell, 
  but it is available in rpmdropbox (and I assume its licensing allows it 
  so). Perhaps re-distributable (and being stored in public repository) is a 
  too-strong word. The question really boils down to this: can the 
  marvell-ipp be used in alternative distributions (that runs on OLPC) other 
  than the official Fedora? And if yes, which whom (email address) can I ask 
  to get them? 
 
 Your speculation is reasonable, and your questions are understood.
 However, we don't have the resources to answer these questions, there
 are other more important things for us to do, sorry.
 
 If you can't determine a useful answer from what you have available,
 then I suggest you stick with software decoders.
 

I understand. Thank you James.

cheers!

-- 
James B jamesbond3...@gmail.com
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel