Bristol Digest, Vol 523, Issue 4

Send Bristol mailing list submissions to
bristol@mailman.lug.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk

You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."


Today's Topics:

1. Info: Radeon Audio over HDMI (Christopher Horler)
2. Re: Yocto (Christopher Horler)


----------------------------------------------------------------------

Message: 1
Date: Fri, 1 Nov 2013 18:25:13 +0000
From: Christopher Horler <cshorler@googlemail.com>
To: Bristol and Bath Linux User Group <Bristol@mailman.lug.org.uk>
Subject: [bristol] Info: Radeon Audio over HDMI
Message-ID:
<CAAeT8m-qq1Rq=1cjPo4FLUGzNRh-1K3EQNiAexWKDcpz=mO5Pw@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

With an openSUSE 3.11.6-3-desktop kernel and setting the module parameter
radeon.audio=1, the HDMI audio out appears to work (it never used to work
even with 3.11 rc candidates). My test platform is based on an AMD E-450
APU.

I'd guess this improvement will be the same for all radeon hardware
supporting HDMI audio, so might be worth getting a kernel upgrade if that
interests you.

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.lug.org.uk/mailman/private/bristol/attachments/20131101/3621b916/attachment-0001.html>

------------------------------

Message: 2
Date: Fri, 1 Nov 2013 20:08:54 +0000
From: Christopher Horler <cshorler@googlemail.com>
To: martinm@it-helps.co.uk, Bristol and Bath Linux User Group
<bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Yocto
Message-ID:
<CAAeT8m8J+xr+s19f2Rt8jTuq5RdbDPZ6U+s_u6XcDHL4Eihu3Q@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"

On 1 November 2013 11:55, Martin Moore <martinm@it-helps.co.uk> wrote:

> Hi all ? I?m thinking of having a play with Yocto to do some Android
> kernel stuff.****
>
> ** **
>
> Has anyone used it?****
>
> ** **
>
> Are there Any other toolchains etc. that will do it (I use Eclipse for
> Apps ? will it do kernel as well?).****
>
> ** **
>
> What hardware should I get to develop on ? I?ve heard 8 core and 64 Gb RAM
> mentioned? !!!****
>
>
>
I've not used Yocto, I think it's more of akin to buildroot than a
compilation toolchain though. For the moment I'm using buildroot, I do
want something else though as buildroot is good for building and managing
patch sets - but it doesn't seem to go further than that (considering how
to deploy and maintain). Yocto like buildroot probably supports external
toolchains (the benefit being everyone can use the same toolchain and
someone else maintains it).

For the moment I'm limited by the installed C library due to a few binary's
without source - I'm using a Linaro toolchain
(gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux). Linaro also
have an Android toolchain, which I'm assuming is similar to the one I'm
using. The toolchain I'm using is based on eglibc (rather than uclibc or
other alternatives).

I'm using the above toolchain and a locally (git repo) branched version of
buildroot for managing the software stack. Ultimately, I'd prefer a
package based approach and a more robust approach to upgrading the system.

The toolchain I'm using comes with two different compilers - I had problems
getting the 4.8 compiler to compile a usable kernel (it all compiled okay,
but the resulting binary failed to boot under QEmu). I couldn't find any
documented bugs, but using the 4.7 version of gcc worked flawlessly...
Perhaps that's why there were multiple compilers included!

There's also a Linaro version of QEmu - that seems to be maintained by the
person responsible for the Versatile Express support, which coincidentally
is a very close match for my target. Also included: GDB 7.5, debug
libraries which have been invaluable for remote debugging of the emulated
target, target ldconfig - which can be run with the user space QEmu to
update the linker cache of the target (built this into my build process).

I've rebuilt a system image from scratch with this approach (using
buildroot), having more than 60 libraries with various patches and a
reliable / repeatable build process stored in a local git repo. The target
is a Kobo Glo device (Cortex A8 + various extensions including NEON). My
emulation target is Versatile Express Cortex A9 - with the same extensions.

For what I'm trying to achieve (various library fixes, improved WebKit
rendering and MathML support -- I want to read a maths EPub ebook I've
created from patched LaTeX sources) this is a flexible approach, but I
don't think ultimately it's what I'll end up using after I get a working
build onto the target as it lacks finesse in some areas (upgrade /
deployment - even though it's very effective for building / developing).

In terms of development requirements - I don't use Eclipse. I don't need a
high powered machine, but a SMP machine certainly speeds the build process
as does solid state storage. I can't afford 64GB of ram, nor a machine to
put it in!

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.lug.org.uk/mailman/private/bristol/attachments/20131101/61b883c8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 92 bytes
Desc: not available
URL: <https://mailman.lug.org.uk/mailman/private/bristol/attachments/20131101/61b883c8/attachment-0001.gif>

------------------------------

_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol

End of Bristol Digest, Vol 523, Issue 4
***************************************