From: Tomas Szepe <szepe@pinerecords.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Stephen Wille Padnos <stephen.willepadnos@verizon.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: a really annoying feature of the config menu structure
Date: Wed, 19 Feb 2003 10:49:39 +0100 [thread overview]
Message-ID: <20030219094939.GB10698@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302182110070.25342-100000@dell>
> [rpjday@mindspring.com]
>
> > > It seems that the mjpeg stuff will be in the wrong place when it starts
> > > being used by non-DVB modules. I see the two (DVB and mjpeg) as
> > > distinct entities - like ethernet drivers and ipv4. (DVB drivers should
> > > let you change channels and whatnot, mjpeg drivers should allow you to
> > > decode data streams from any available source.)
> >
> > Its more by API than by hardware. One driver sometimes covers cards with
> > and without tuners, with and without mpeg hardware and so on. Classification
> > is nice, but like biology its never neat
>
> true enough -- there's no perfect solution, but i'm convinced that
> it can certainly be much more intuitive and organized that it is now.
Please wait until Roman Zippel pushes the "menuconfig" grammar extension.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-02-19 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 21:28 Robert P. J. Day
2003-02-18 22:33 ` Stephen Wille Padnos
2003-02-19 1:04 ` Robert P. J. Day
2003-02-19 1:24 ` Stephen Wille Padnos
2003-02-19 2:09 ` Robert P. J. Day
2003-02-19 1:56 ` Alan Cox
2003-02-19 1:31 ` Stephen Wille Padnos
2003-02-19 3:03 ` Alan Cox
2003-02-19 2:13 ` Robert P. J. Day
2003-02-19 9:49 ` Tomas Szepe [this message]
2003-02-19 13:19 ` Helge Hafting
2003-02-19 13:31 ` Robert P. J. Day
2003-02-19 14:35 ` John Bradford
2003-02-19 13:33 ` Robert P. J. Day
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=20030219094939.GB10698@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=stephen.willepadnos@verizon.net \
/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
all inboxes | Powered by JetHome®