From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [RFC] Dropping rivatv from sensors-detect
Date: Mon, 28 Aug 2006 11:46:58 +0000 [thread overview]
Message-ID: <20060828134658.c4d0ae3c.khali@linux-fr.org> (raw)
Hi all,
Is there any objection to me dropping rivatv detection from
sensors-detect? My reasons are:
* rivatv is still not in mainline after 3 years. I wonder if it will
ever be.
* rivatv is only one of the several drivers which can provide I2C/SMBus
access to nVidia adapters. nvidiafb and rivafb do it as well (although
I did not check if access to the same busses was provided) and they
are in mainline. And nVidia's proprietary X driver does also in recent
versions, even though it won't work at the moment due to improperly
set i2c functionality flags (and we won't provide support for it, but
that's a different point.)
* Most PCI drivers will autoload in recent Linux 2.6 kernels (in
particular nvidiafb and rivafb do). So I'd rather let the user pick the
driver he/she wants. sensors-detect will scan all available busses
anyway, whether they were detected or not.
* There are many many different nVidia graphics adapters. We already
have 22 entries, representing 20% of the total list of known PCI
adapters. Given that the last ones were added over 2 years ago, the list
is certainly incomplete. I don't even know which devices are supported
by rivatv (or the other drivers mentioned above), and I don't want to
spend time tracking this.
So unless someone finds a good reason I missed, I plan to remove all
references to rivatv from sensors-detect soon.
Thanks,
--
Jean Delvare
next reply other threads:[~2006-08-28 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 11:46 Jean Delvare [this message]
2006-08-28 16:56 ` [lm-sensors] [RFC] Dropping rivatv from sensors-detect Steven Karatnyk
2006-09-03 14:18 ` Jean Delvare
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=20060828134658.c4d0ae3c.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.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.