linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Christof Petig <christof.petig@wtal.de>
Cc: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
	"Halfmann, Klaus" <khalfmann@libra.de>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: AW: Sound on an iBook?
Date: Fri, 08 Dec 2000 15:36:18 +0000	[thread overview]
Message-ID: <200012081601.QAA31117@hyperion.valhalla.net> (raw)


Christof Petig wrote:

>[...]
>
> The link is dead, but
> http://www.micronas.com/products/documentation/consumer/dac3550a/index.php
> works for me well.

thanks for the update.

> Thank you very much for this information!

OK.  I think my first reply may have gone astray (it never showed up here
anyway)...

This is what I (think) I know about the "problem".

1/  The output uses dmdma same as the other chips - so fixing up init() to
recognise the iBook and do the necessary register assignments from the OF
tree should be an OK solution (i.e. no more ugly than any other version of
the dmasound driver)... except for:

2/  There is *no* mixer abstraction - because the chip is driven through i2c
(like the sound control chip on the G3/beige - which I *have* played with -
unfortunately a different i2c bus).  Which is why you get whatever OF
leaves..

I suspect that 'freezing' has got nothing to do with the chip per se... but
probably more to do with invalid mixer abstraction code being called.

========

So you will need to:

Fix up the init code - and maybe the register map. although I suspect this
has been done in the hack to which Klaus referred.. don't know which hack
(it's not in mine ;-).

write a mixer abstraction modelled on the ones for awacs and burgundy.  A
little nasty 'cos the code has evolved into something with many arms... ;-)

also there are many bodges to represent the Apple hardware under OSS - which
doesn't really have the API for the resources...  I have an idea to address
this as well - but it will have to wait for a few more weeks.

I have a request...

when I get back on line with the dmasound driver (expect Jan 01) I want to
continue with a code tidy - basically partitioning the source so that one
chip set is dealt with in one file (leaving the common dbdma abstraction
aside).

There are many issues (not least of which is maintaining a common base
across the 68k stuff as well) to address in this split-up but I think it's
long overdue.

So, if you have a go (and think there *are* some bits of useful code in
Darwin)... it would help me if the daca-specific mixer abstraction was
clearly separated from the other stuff.  (better still in a separate source
file from the start ;-)

thanks,
Iain.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-12-08 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08 15:36 Iain Sandoe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-08 19:34 AW: Sound on an iBook? Iain Sandoe
2000-12-12 19:01 ` Michel Lanners
2000-12-08 17:19 D.J. Barrow
2000-12-08 12:05 Iain Sandoe
2000-12-08 15:01 ` Christof Petig
2000-12-08 11:56 Iain Sandoe
2000-12-08  8:38 Halfmann, Klaus
2000-12-08 11:35 ` Michael Schmitz
2000-12-08 12:12 ` Benjamin Herrenschmidt
2000-12-08 14:36 ` Christof Petig

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=200012081601.QAA31117@hyperion.valhalla.net \
    --to=iain@sandoe.co.uk \
    --cc=christof.petig@wtal.de \
    --cc=khalfmann@libra.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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).