From: Matt Sealey <matt@genesi-usa•com>
To: Grant Likely <grant.likely@secretlab•ca>
Cc: ppc-dev <linuxppc-dev@ozlabs•org>
Subject: Re: Missing patch for MPC5200B register definitions?
Date: Fri, 28 Mar 2008 12:36:54 +0000 [thread overview]
Message-ID: <47ECE666.7030001@genesi-usa.com> (raw)
In-Reply-To: <fa686aa40803270627r5c83f373kf5055a9c44d37300@mail.gmail.com>
Grant Likely wrote:
> On Wed, Mar 26, 2008 at 10:15 AM, Matt Sealey <matt@genesi-usa•com> wrote:
>> I've just been looking into the MPC5200B AC97 driver breakage with the
>> latest Git kernel, and found the following patch;
>>
>> http://ozlabs.org/pipermail/linuxppc-dev/2007-May/035952.html
>>
>> Is not in the latest tree. As such anything which uses the new MPC5200B
>> registers (especially important on AC97 and probably not used otherwise)
>> has not or was not applied.
>>
>> Since the latest kernel source from git actually includes the MPC5121E
>> differences, I assume this is a regression?
>>
>> How do we go about fixing this?
>
> Write a patch to apply that change in arch/powerpc and post it to the
> list. If it looks good, I'll pick it up.
I'll make one now. The AC97 driver needs it anyway, later, plus some
definitions are missing for PSC control.. also only used by the AC97
driver for now, but still probably quite important (or just hardcoded
elsewhere).
> BTW, did you figure out if the AC97 driver is being picked up by the
> ALSA maintainers?
We just worked around a crash bug (somehow..) but now we get no audio.
I'm not going to submit it to them until we can actually get sound
out of the damn thing..
--
Matt Sealey <matt@genesi-usa•com>
Genesi, Manager, Developer Relations
prev parent reply other threads:[~2008-03-28 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 16:15 Missing patch for MPC5200B register definitions? Matt Sealey
2008-03-26 16:48 ` Matt Sealey
2008-03-27 13:25 ` Grant Likely
2008-03-27 13:27 ` Grant Likely
2008-03-28 12:36 ` Matt Sealey [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=47ECE666.7030001@genesi-usa.com \
--to=matt@genesi-usa$(echo .)com \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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