All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Abramo Bagnara <abramo@alsa-project.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	"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" <sound-hackers@zabbo.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [s-h] Re: ALSA patch for 2.5.2pre9 kernel
Date: Tue, 08 Jan 2002 11:34:49 +0100	[thread overview]
Message-ID: <s5hell1gmgm.wl@alsa1.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.31.0201081116300.482-100000@pnote.perex-int.cz>
In-Reply-To: <s5hk7utgnh3.wl@alsa1.suse.de> <Pine.LNX.4.31.0201081116300.482-100000@pnote.perex-int.cz>

At Tue, 8 Jan 2002 11:18:34 +0100 (CET),
Jaroslav wrote:
> 
> On Tue, 8 Jan 2002, Takashi Iwai wrote:
> 
> >
> > > I still have some doubts about hardware specific include files:
> > > a) sound/include
> > > b) drivers/sound/{i2c,isa,pci,ppc}
> > > c) drivers/sound/include
> > >
> > > Currently my vote would go for b), but I see drawbacks for this solution
> > > (for generic chip include files, like ac97 or ak4531 ones). Perhaps it's
> > > better to have a mixed solution (partly b) and partly c)
> >
> > Agreed.  The hw specific header files should be bound with *.c code
> > together.
> 
> The problem is that we should export some header files to user space as
> well to allow access to hardware related features.

Hmm..  but such programs require the kernel tree anyway, since
/usr/include/linux is ususally no longer symlinked to /usr/src/linux.


Takashi

  reply	other threads:[~2002-01-08 10:35 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 [this message]
2002-01-08 10:36         ` Abramo Bagnara
2002-01-08 10:50           ` Jaroslav Kysela
2002-01-08 10:28       ` Abramo Bagnara
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=s5hell1gmgm.wl@alsa1.suse.de \
    --to=tiwai@suse.de \
    --cc=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=perex@suse.cz \
    --cc=sound-hackers@zabbo.net \
    --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 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.