public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Abramo Bagnara <abramo@alsa-project.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Jaroslav Kysela <perex@suse.cz>,
	"J.A. Magallon" <jamagallon@able.es>, Alan Cox <alan@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Christoph Hellwig <hch@ns.caldera.de>,
	sound-hackers@zabbo.net, linux-sound@vger.rutgers.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [s-h] Re: ALSA patch for 2.5.2pre9 kernel
Date: Tue, 08 Jan 2002 11:28:09 +0100	[thread overview]
Message-ID: <3C3AC9B9.B854859D@alsa-project.org> (raw)
In-Reply-To: <20020108102833.A2927@werewolf.able.es> <20020108103046.A3545@werewolf.able.es> <3C3AC150.BE4FFAFE@alsa-project.org> <s5hk7utgnh3.wl@alsa1.suse.de>

Takashi Iwai wrote:
> 
> At Tue, 08 Jan 2002 10:52:16 +0100,
> Abramo wrote:
> >
> >
> > So we'd have:
> > sound/
> > sound/oss_native
> > sound/oss_emul
> > sound/synth
> > sound/include
> > drivers/sound/i2c
> > drivers/sound/isa
> > drivers/sound/pci
> > drivers/sound/ppc
> 
> On the list above, to where OSS (hw specific) codes come?  Into a
> single directory, sound/oss_native?

Yes

> Or both ALSA and OSS drivers are
> mixed into drivers/sound/*?
> I'd like to see ALSA and OSS codes are separated into different
> directories...  Otherwise it's too confusing.

I think that in this way they are separated enough. Do you agree?

> 
> And how about drivers/sound/generic for generic hardware codes such as
> ac97_codec.c?

Currently Jaroslav has put that in alsa-kernel/pci/ac97. If we follow
this guideline they go in drivers/pci/ac97 (although I'm not sure
whether ac97 is PCI only).

-- 
Abramo Bagnara                       mailto:abramo@alsa-project.org

Opera Unica                          Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy

ALSA project               http://www.alsa-project.org
It sounds good!

  parent reply	other threads:[~2002-01-08 10:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020108102833.A2927@werewolf.able.es>
2002-01-08  9:30 ` [s-h] Re: ALSA patch for 2.5.2pre9 kernel J.A. Magallon
2002-01-08  9:52   ` Abramo Bagnara
2002-01-08 10:12     ` Takashi Iwai
2002-01-08 10:18       ` Jaroslav Kysela
2002-01-08 10:34         ` Takashi Iwai
2002-01-08 10:36         ` Abramo Bagnara
2002-01-08 10:50           ` Jaroslav Kysela
2002-01-08 10:28       ` Abramo Bagnara [this message]
2002-01-08 10:41         ` Jaroslav Kysela
2002-01-07 23:44 J.A. Magallon
2002-01-08  2:01 ` [s-h] " Alan Cox
2002-01-08  5:12   ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2002-01-07 20:51 Steven Walter
2002-01-07 19:03 Dimitrie Paun
2002-01-07 18:10 Arnaldo Carvalho de Melo
2002-01-08  2:13 ` [s-h] " Alan Cox
2002-01-08 12:47   ` Arnaldo Carvalho de Melo
2002-01-07 18:00 Linus Torvalds
2002-01-07 18:19 ` [s-h] " Abramo Bagnara
2002-01-07 18:29   ` Linus Torvalds
2002-01-07 18:39     ` Abramo Bagnara
2002-01-07 18:47       ` Linus Torvalds
2002-01-07 19:09         ` Abramo Bagnara
2002-01-07 19:21         ` Pozsar Balazs
2002-01-07 20:29         ` Jauder Ho
2002-01-14  3:10         ` Pavel Machek
2002-01-07 21:25   ` Christoph Hellwig
2002-01-08  1:16     ` Timothy Covell
2002-01-08  2:53     ` Miles Lane

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=3C3AC9B9.B854859D@alsa-project.org \
    --to=abramo@alsa-project.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=hch@ns.caldera.de \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.rutgers.edu \
    --cc=perex@suse.cz \
    --cc=sound-hackers@zabbo.net \
    --cc=tiwai@suse.de \
    --cc=torvalds@transmeta.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