All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathaniel McCallum <nathaniel@natemccallum.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: Exposing device ids and driver names
Date: Thu, 01 Oct 2009 14:28:48 -0400	[thread overview]
Message-ID: <4AC4F4E0.7050404@natemccallum.com> (raw)
In-Reply-To: <4AC4F3B0.6080202@s5r6.in-berlin.de>

On 10/01/2009 02:23 PM, Stefan Richter wrote:
> Nathaniel McCallum wrote:
>> On 10/01/2009 01:47 PM, Stefan Richter wrote:
>>> Nathaniel McCallum wrote:
> [...]
>>>> The second tool, related to the first, is a program which runs on
>>>> Windows and scans for a user's hardware and tells them which distro will
>>>> best support their hardware.
> [...]
>>> Hardware support also depends on userland:  Udev rules, libraries,
>>> application programs.
>>>
>>> Even if you ignore that for now and only look at the kernel part of
>>> hardware support:  Beyond "doesn't have a matching driver" and "does
>>> have", there is a large and impossible to track grey area of "has a
>>> poorly working driver" and "has a perfectly working driver".
>
> There are even more factors for how well something works or even whether
> it works at all:  It may even depend on combinations of two pieces of
> hardware, e.g. bus adapter and device on that bus.  It may depend on
> device firmware revisions.
>
>> Yes, I'm aware of this and will account for it as best as I am able.
> [...]
>> you are correct that we cannot predict 100% of user
>> experience.  But 70% is a huge improvement over 0%.
>
> So, this 2nd tool can't literally say which distribution supports a
> device best.  It can mostly just list which distributions contain a
> matching kernel driver.

I never said that.  What I said is that I will "do my best." This will 
include using other data sources, such as Xorg drivers, libusb drivers, 
user feedback, etc.

Nathaniel

      reply	other threads:[~2009-10-01 18:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 16:40 Exposing device ids and driver names Nathaniel McCallum
2009-10-01 16:42 ` Greg KH
2009-10-01 17:01   ` Nathaniel McCallum
2009-10-01 18:05     ` Greg KH
2009-10-01 18:35       ` Nathaniel McCallum
2009-10-01 18:40         ` Greg KH
2009-10-01 18:56           ` Nathaniel McCallum
2009-10-01 19:07             ` Greg KH
2009-10-01 19:17               ` Nathaniel McCallum
2009-10-01 21:36           ` Nathaniel McCallum
2009-10-01 17:47 ` Stefan Richter
2009-10-01 18:02   ` Nathaniel McCallum
2009-10-01 18:23     ` Stefan Richter
2009-10-01 18:28       ` Nathaniel McCallum [this message]

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=4AC4F4E0.7050404@natemccallum.com \
    --to=nathaniel@natemccallum.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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.