9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dante <subscriptions@posteo.eu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] PWM and audio drivers for Raspberry Pi
Date: Sat, 23 Aug 2014 11:52:04 +0200	[thread overview]
Message-ID: <4da1f6793b81ec9012a55b338fc20a0a@posteo.de> (raw)
In-Reply-To: <CA+wNSKZ6NM7u85wf1+c0EX8POsu=MPVFVg9GNWZGCpX433V8mg@mail.gmail.com>

Hi Pedro,

That's super-cool, thanks!

Please consider submitting the patch through the right channels.
Since I'm new here, I am not sure if this is correct, but here is what
I found out:

1. as a patch(1) to the contributors. No idea if geoff or jmk are still
working there:
     http://plan9.bell-labs.com/wiki/plan9/How_to_contribute/

2. ask David du Colombier to accept and publish your patch:
     http://www.9legacy.org

Cheers,
Dante

On 23.08.2014 11:32, Pedro Coutin wrote:
> Hello everyone,
>
> I made a working audio driver for the Raspberry Pi by using the
> chipset's
> PWM device directly.
>
> The sound quality seems pretty acceptable to me.  I managed to play
> music
> and the Doom port from 9front with it.
>
> Since it uses the PWM device, it only works for the TRS stereo jack.
> I
> believe that the most sensible way to make HDMI audio work is to
> make a VCHI(Q) driver, and then an audio driver that interfaces with
> that. There's very little, if any, documentation available on this and
> the Linux kernel code for it is pretty huge.
>
> Tarball with changed files:
> http://acsweb.ucsd.edu/~pcoutin/bcm-audio.tgz
>
> Repository:
> https://bitbucket.com/pcoutin/9pi-audio
>
> Man page for PWM device:
> http://acsweb.ucsd.edu/~pcoutin/bcmpwm.html
>
> I guess I could extend the PWM driver so that the two channels can be
> enabled/disabled separately.



      reply	other threads:[~2014-08-23  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23  9:32 Pedro Coutin
2014-08-23  9:52 ` dante [this message]

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=4da1f6793b81ec9012a55b338fc20a0a@posteo.de \
    --to=subscriptions@posteo.eu \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).