All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Jon Mason <jdmason@us.ibm.com>, Muli Ben-Yehuda <mulix@mulix.org>,
	Jiri Slaby <slaby@liberouter.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Prevent trident driver from grabbing pcnet32 hardware
Date: Thu, 12 Jan 2006 17:55:44 -0500	[thread overview]
Message-ID: <1137106544.2370.97.camel@mindpipe> (raw)
In-Reply-To: <20060112225205.GZ29663@stusta.de>

On Thu, 2006-01-12 at 23:52 +0100, Adrian Bunk wrote:
> > I'm still not sure that just adding it to the ALSA driver and hoping it
> > works is the best solution.  Would we rather users see right away that
> > their hardware isn't supported, or have the driver load and get no sound
> > or hang the machine?
> > 
> > I think the best approach might just be to drop it in lieu of a tester.
> > It will be trivial to add support later if someone finds one of these
> > boxes.
> 
> Agreed.
> 

OK I'm just going to close that bug, the one person who seemed to know
anything about it had this to say:

"The cyberpro 5050 is an old combined video+audio controller - and
is/was used in some settop boxes (German Siemens Activity and also
Loewe).

There will be no "desktop users" around.
And because I don't work for Loewe anymore: I don't have access to
hardware.

If you ask me: leave it out!"

Anyone who finds one of these is free to reopen it.

Lee


  reply	other threads:[~2006-01-12 22:55 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 17:50 [PATCH] Prevent trident driver from grabbing pcnet32 hardware Jon Mason
2006-01-12 19:28 ` Jiri Slaby
2006-01-12 19:34   ` Jiri Slaby
2006-01-12 20:07   ` Muli Ben-Yehuda
2006-01-12 21:15     ` Lee Revell
2006-01-12 21:58       ` Adrian Bunk
2006-01-12 22:06         ` Lee Revell
2006-01-12 22:11           ` Jon Mason
2006-01-12 22:46           ` Adrian Bunk
2006-01-12 21:47     ` Jon Mason
2006-01-12 22:00       ` Adrian Bunk
2006-01-12 22:09         ` Jan Engelhardt
2006-01-12 22:20         ` Jon Mason
2006-01-12 22:42         ` Lee Revell
2006-01-12 22:52           ` Adrian Bunk
2006-01-12 22:55             ` Lee Revell [this message]
2006-01-13 10:16               ` Alan Cox
2006-01-12 23:32             ` Old hardware (was Re: [PATCH] Prevent trident driver from grabbing pcnet32 hardware) Lee Revell
2006-01-12 23:52               ` Bob Copeland
2006-01-13 10:28           ` [PATCH] Prevent trident driver from grabbing pcnet32 hardware Alan Cox
2006-01-13 17:55             ` Lee Revell
2006-01-13 11:37           ` Muli Ben-Yehuda
2006-01-13 12:23             ` Adrian Bunk
2006-01-13 12:32               ` Muli Ben-Yehuda
2006-01-13 15:24                 ` Adrian Bunk
2006-01-13 15:36                   ` Muli Ben-Yehuda
2006-01-12 22:08     ` Jon Mason
2006-01-12 20:49 ` pcnet32 devices with incorrect trident vendor ID Daniel Drake
2006-01-12 20:57   ` Matthew Wilcox
2006-01-12 21:03     ` Daniel Drake
2006-01-12 21:05     ` Matthew Wilcox
2006-01-12 21:22       ` Bill Nottingham
2006-01-12 21:24         ` Bill Nottingham
2006-01-12 22:23           ` Don Fry
2006-01-12 22:33             ` Jon Mason
2006-01-12 21:05   ` Lennart Sorensen

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=1137106544.2370.97.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=bunk@stusta.de \
    --cc=jdmason@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mulix@mulix.org \
    --cc=slaby@liberouter.org \
    /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.