From: Wolfgang Denk <wd@denx.de>
To: "Eric N. Johnson (ACD)" <ejohnson@acdstar.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC5200 I2S driver
Date: Wed, 13 Apr 2005 01:40:05 +0200 [thread overview]
Message-ID: <20050412234010.82DF1C108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 12 Apr 2005 17:46:03 CDT." <6.2.1.2.1.20050412173010.02adaaa0@mail.int.acdstar.com>
In message <6.2.1.2.1.20050412173010.02adaaa0@mail.int.acdstar.com> you wrote:
>
> Humm, any pointers on writing our own driver then then? Digging through
> the source for other drivers, bestcomm seems to be a real house of
> cards. We just want simple audio output capability. No need to make it
> work with the standard Linux/OSS sound API.
User the i2s_ring.c driver as model.
> Where can we keep track of the eratta/bugs in bestcomm? Browsing through
> the mailing list, I've found references that:
> IDE and Ethernet DMA can't work at the same time
> I2S TX and RX DMA can't work at the same time
> AC-97 is terminally broken (no way to handle the slot tags properly
> for variable sampling rates)
> Are these all still true?
This probably depends on your definition of "can't work". If you
allow for a failure every now and then under certain (more or less
exotic) usage conditions ... ;-)
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
I have been over into the future, and it works.
- Lincoln Steffens in _Letters_ (1938) vol. 1, p. 463
next prev parent reply other threads:[~2005-04-13 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 19:38 (no subject) Eric N. Johnson (ACD)
2005-04-12 21:13 ` Wolfgang Denk
2005-04-12 22:46 ` MPC5200 I2S driver Eric N. Johnson (ACD)
2005-04-12 23:40 ` Wolfgang Denk [this message]
2005-04-13 20:23 ` Hans Thielemans
-- strict thread matches above, loose matches on Subject: below --
2005-11-05 19:22 Frank Bennett
2005-11-06 20:42 ` Wolfgang Denk
2005-11-07 21:04 ` Eric N. Johnson (ACD)
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=20050412234010.82DF1C108D@atlas.denx.de \
--to=wd@denx.de \
--cc=ejohnson@acdstar.com \
--cc=linuxppc-embedded@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.