hardware solutions and other one-off

[Robert M. Albrecht]

Hi,

I am interessted.

It should be both:

- manual
- automatic

I don`t think smolt is enough. There are several other places:
gutenprints test page, sound-card-detection,  xsane, ...

Has smolt an API, so other apps like digikam, sane, ... could send
information about non-working scanner, digital-cameras, 1394 camcorders ?

I have a tft-display that does screw up x.orgs autodetection because of
faulty ddc-readouts. Such devices should be possible to add manually.

And we could add the inform-vendor-button for non-supported devices we
talked about:

https://www.redhat.com/archives/fedora-marketing-list/2007-April/msg00087.html
https://www.redhat.com/archives/fedora-advisory-board/2007-March/msg00139.html

cu romal


Rahul Sundaram schrieb:
> Karsten Wade wrote:
>> Below is an example of a request that we haven't been able to fill, to
>> support a community-based set of content about hardware compatibility
>> and solutions.  I think a knowledgebase solution (kbase) is the best way
>> to tackle this, and it has been discussed here before.  We can get this
>> specified, planned, and put into a queue for deployment by Fedora
>> Infrastructure.
>>
>> Anyone interested in moving ahead on this?  A post Fedora 7 project, to
>> be sure.  Sam Folk-Williams, iirc, was interested ... who else?
>>
> 
> Any manual solution like Kbase won't scale. Look at
> 
> http://wtogami.livejournal.com/16659.html for something more automated.
> 
> Rahul
>