From: Stephen Wille Padnos <stephen.willepadnos@verizon.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: a really annoying feature of the config menu structure
Date: Tue, 18 Feb 2003 20:31:55 -0500 [thread overview]
Message-ID: <3E52DE8B.6040002@verizon.net> (raw)
In-Reply-To: <1045619804.25795.14.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
>On Tue, 2003-02-18 at 22:33, Stephen Wille Padnos wrote:
>
>
>>[snip]
>>
>>
>>
>>> as i see it, this can only get worse. the current
>>>erratic and disorganized structure of the config menus
>>>is proof of that.
>>>
>>> comments?
>>>
>>>
>>>
>>I think the problem with the "Multimedia" menu is that it's misnamed.
>>It should actually be the "tuners" menu - it's there for audio, digital
>>video, and video tuners. The same could be said of the networking menu,
>>and presumably others.
>>
>>
>
>It covers lots of tunerless mpeg and mjpeg stuff. Eg the DVB stuff will
>eventually include the Margi PCMCIA DVD player and we already have other
>pure mpeg or pure webcam stuff in there
>
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.)
- Steve
next prev parent reply other threads:[~2003-02-19 1:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 21:28 a really annoying feature of the config menu structure 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 [this message]
2003-02-19 3:03 ` Alan Cox
2003-02-19 2:13 ` Robert P. J. Day
2003-02-19 9:49 ` Tomas Szepe
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=3E52DE8B.6040002@verizon.net \
--to=stephen.willepadnos@verizon.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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