[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Hardware compatibility test: draft proposal

"Giacomo Catenazzi" <cate@debian.org> wrote in message [🔎] 48AE9B26.4040704@debian.org">news:[🔎] 48AE9B26.4040704@debian.org...
Wouter Verhelst wrote:

As I mentioned in my blog[1], I kindof like the suggestion that Bdale

Yes, I find the talk very interesting.

So, after more than twelve hours of boredom on an airplane and half a
night of not-being-able-to-sleep-due-to-jetlag, which is certainly
enough to think about this problem, I came up with the following things
such a system could need:

/me too

- It should support a notion of what I'll call 'profiles'. A 'server'
  profile should check for different things than a 'desktop' or 'laptop'
  profile; e.g., it's usually okay if a server doesn't have graphical
  support or wireless drivers, while the same isn't true for a laptop.

No. I don't think we should provide profiles.
The check should be:
"complete": test all hardware that it is installed on system.
If the system doesn't have the video-card or the wifi just it doesn't
test it, but it write a notice.
Listening the available hardware is pretty trivial (see i.e. my

Ok. What does the test do if it notices that a pecie of hardware exists, but cannot identify it?
Should it warn about that?

The long list of hardware not found may be a problem. Let's picture a modern desktop PC.
"No floppy drive found."
"No touchpad found."
"No webcam found."
"No firewire found."
"No modem found." (This is common enough these days, but we would definately want to test any found modem due to the proliferation of weird winmodems these days).
"No physics acellerator found."
"No PC card slot found"
"No HD-DVD drive found"
"No Blu-ray drive found"
"No RAID controller found"
"No gigabit ethernet found"
"No EFI firmware found" (This theoretical PC is not a Intel Mac.)
"No fingerprint scanner found".

(The list could go on and on).

Perhaps a few of those could be merged into other tests, like a single optical drive test, but in some of those cases it would then be important that a list of hardware that was found is printed. That way the manufacturer can be sure that both optical drives (in a two optical drive PC) were found.

If there is any hardware that cannot be tested with only a single test script due to major implementation differences between all brands of hardware (and no current unified software interface), we would want to avoid having a notice printed for each possible manufacture of the device.

Reply to: