Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Jan 2012 10:36:18 +0100
From:      =?UTF-8?B?5Zu+5r2Y?= <patula777@gmail.com>
To:        freebsd-drivers@freebsd.org
Subject:   Dear driver developer (please read)
Message-ID:  <CAASz-w01=DYeoULixc4XLv-a%2BQNO7jh1=_Tdv9-gabCoTxjHCw@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
Dear driver developer,

currently when I am trying to get information about a working device, I
visit the freebsd harware notes, check for the name and then go to the
manual page. The manual pages unfortunately only states chipsets and not
vendor/device id's and at the moment there is no clear mapping between the
two.

So this is what we are trying to establish at http://freebsd.0fees.net

One of my team mates had the idea to create an interface at the above
stated page for driver developers to submit your data directly and
correctly mapped.
The data will still be independent from user submitted data about
working/not working devices
This would create a couple of benefits:

+ if you submit data for a particular chipset (not a card) based on
vendor/device id (without the subsystem) you can see what user report about
this particular chipset on different cards and possible incompatibilities
of different cards using the same chip could be discovered more
transparently.
+ a clear mapping between chipset names and vendor/device id would evolve.
+ and possibly some more i cannot think of right now.

The question right now is:
Does it make sense to you and would you submit the data?

If yes, we would like to make it as simple as possible for you to submit
the data and create this interface based on your ideas (such as would data
you need to submit and how you want to have the actual view of the relation
between your data compared to the user submitted data.

Please feel free to discuss about this being rubbish or a good idea.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAASz-w01=DYeoULixc4XLv-a%2BQNO7jh1=_Tdv9-gabCoTxjHCw>