Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@psi.cz>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: linux-mips@oss.sgi.com
Subject: Re: [RFC][PATCH]
Date: Sun, 30 Jun 2002 23:37:50 +0200	[thread overview]
Message-ID: <20020630233750.C6248@erebor.psi.cz> (raw)
In-Reply-To: <20020630132020.GF17216@lug-owl.de>; from jbglaw@lug-owl.de on Sun, Jun 30, 2002 at 03:20:20PM +0200

On Sun, Jun 30, 2002 at 03:20:20PM +0200, Jan-Benedict Glaw wrote:
> On Sun, 2002-06-30 14:42:38 +0200, Ralf Baechle <ralf@oss.sgi.com>
> wrote in message <20020630144238.A342@dea.linux-mips.net>:
> > On Sat, Jun 29, 2002 at 08:41:29PM +0200, Jan-Benedict Glaw wrote:
> > > Please give me a comment on this patch. I'm currently tryin' to make the
> > > HAL2 driver work (yes, I've got my Indy out of the edge again and I'm
> > > going to use it as my desktop machine).
> > > 
> > > It fixes a compilation problem on dmabuf.c. There, DMA_AUTOINIT isn't
> > > defined. As ./include/asm-mips/dma.h looks like the asm-i386 file in
> > > general, I've copied the #define from the i386 port (and reformated the
> > > passus...).
> > > 
> > > If you think it'o okay, please apply it (and drop me a note:-p)
> > 
> > Sort of the right thing - why the heck does the Indy sound code have to
> > rely on code for the that antique PC DMA controller ...
> 
> Well, OSS has some 'soundbase.o', in which dmabuf.o is linked into.

you need soundcore.o and hal2.o only.

> Possibly which code path is not used at all on Indy, but the #define has
> to be there... So there's no real answer, but running 2.4.16 (from

the real answer is that you are trying to build support for OSS drivers,
which has definitely nothing to do with HAL2 driver. disable it.

> Debian installer) and 'insmod -f'ing the just compiled 2.4.19-rc1 hal2.o
> into that kernel ends up in useable sound. So this is some working way
> of doing sound.
> 
> Btw., I think I'll have a deeper look at hal2.o - the smallest load lets
> sound proceed in snail mode:-(

can you describe it better? (it has always worked for me ;-))

	ladis

      reply	other threads:[~2002-06-30 21:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29 18:41 [RFC][PATCH] Jan-Benedict Glaw
2002-06-30 12:42 ` [RFC][PATCH] Ralf Baechle
2002-06-30 13:20   ` [RFC][PATCH] Jan-Benedict Glaw
2002-06-30 21:37     ` Ladislav Michl [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=20020630233750.C6248@erebor.psi.cz \
    --to=ladis@psi.cz \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-mips@oss.sgi.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