From owner-freebsd-hardware@FreeBSD.ORG Mon Jan 9 08:40:11 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8F051065675 for ; Mon, 9 Jan 2012 08:40:11 +0000 (UTC) (envelope-from patula777@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7D5B58FC0C for ; Mon, 9 Jan 2012 08:40:11 +0000 (UTC) Received: by dakp5 with SMTP id p5so2767192dak.13 for ; Mon, 09 Jan 2012 00:40:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LQJiZLbF1LwZYwSNWdKr5PjsPMTa0OTJZFJZyUyCVpE=; b=HJ9VD/Ce+kddu2xBVca02rd3JmIzIAapVyCD4oF8dszURyttgbTsdM29W78fQ2sdvD 77qLg4Fve7OErrjBDwDEqVZpnx8n0b75k6Kus7ISdQpVGy1VEOEE3BI6ric6LCM/aU2r w63NZ+GyyNBMphpmYCH/qPHAiZ0dcWYG1fgoc= MIME-Version: 1.0 Received: by 10.68.115.17 with SMTP id jk17mr25507358pbb.47.1326098411020; Mon, 09 Jan 2012 00:40:11 -0800 (PST) Received: by 10.143.17.2 with HTTP; Mon, 9 Jan 2012 00:40:10 -0800 (PST) In-Reply-To: References: <4f097a9f.a833440a.141e.3332SMTPIN_ADDED@mx.google.com> Date: Mon, 9 Jan 2012 09:40:10 +0100 Message-ID: From: =?UTF-8?B?5Zu+5r2Y?= To: Subbsd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: new low level hardware support list X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 08:40:11 -0000 This sounds like a good idea in terms of automation. Currently we still have not fully figured out how to extract good and valid information from dmesg, pciconf, kldstat (and dmidecode). As long as this is not solved clearly we have to rely on manual user input, as we do not want too many false positives. (at least for driver support) For mapping notebook devices, it would be a good way to gather data more quickly than to actually get the vendors to do this thanks for the info and keep suggesting :-) On Mon, Jan 9, 2012 at 7:09 AM, Subbsd wrote: > Hi > > On Sun, Jan 8, 2012 at 4:10 PM, =E5=9B=BE=E6=BD=98 = wrote: > > Thanks for pointing out the site. > > >From a first look I would say bsdstats.org is interesting for vendors > > (stats about who is using what device on system X) whereas our project = is > > interesting for users (showing what device is supported on system X). > > Nevertheless, You can try to add support of your project into the port > sysutils/bsdstats ( with a permission of the author) > Gathering of the information and periodic post there are already > realized. So if will be in one port it must be wonderful - > project bsdstats receive alternative and another way issued site, and > you get users of port after updating bsdstats version. > > > > > On Sun, Jan 8, 2012 at 11:53 AM, Ivan Klymenko wrote: > > > >> > >> Thank you for your work! > >> > >> What's the fundamental difference your resurs with respect to > bsdstats.org > >> ? > >> > >> Thanks. > >> _______________________________________________ > >> freebsd-hardware@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > >> To unsubscribe, send any mail to " > freebsd-hardware-unsubscribe@freebsd.org > >> " > >> > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to " > freebsd-hardware-unsubscribe@freebsd.org" >