LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Matt Sealey" <matt@genesi-usa.com>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Missing patch for MPC5200B register definitions?
Date: Thu, 27 Mar 2008 07:27:08 -0600	[thread overview]
Message-ID: <fa686aa40803270627r5c83f373kf5055a9c44d37300@mail.gmail.com> (raw)
In-Reply-To: <47EA7687.5000102@genesi-usa.com>

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.

BTW, did you figure out if the AC97 driver is being picked up by the
ALSA maintainers?

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  parent reply	other threads:[~2008-03-27 13:27 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 [this message]
2008-03-28 12:36   ` Matt Sealey

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=fa686aa40803270627r5c83f373kf5055a9c44d37300@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    /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