[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] Hardware database
From:       Matthew Marchese <maffblaster () gentoo ! org>
Date:       2016-02-29 7:26:21
Message-ID: 56D3F29D.4020706 () gentoo ! org
[Download RAW message or body]

On 02/09/2016 07:01 AM, Michał Górny wrote:
> On Tue, 9 Feb 2016 17:53:09 +0300 > agentsmith <igorsavlook@gmail.com> wrote: > >> Cool tool i create
ebuild. >> >> On 02/09/2016 05:47 PM, Daniel Campbell wrote:
>
> > Could
>
> On 02/09/2016 05:55 AM, Urbain YANG wrote:  
> >>>> Thank you very much!
> >>>>
> >>>> And wish it will be merged into Portage soon.
> >>>>
> >>>>
> >>>> Urbain YANG urbain.yang@qq.com <mailto:urbain.yang@qq.com>
> >>>>
> >>>>
>
> > you
>
> >>>>
> >>>>  
> >>>>> 在 2016年2月9日,下午9:33,Ponomarenko Andrey
> >>>>> <andrewponomarenko@yandex.ru
> >>>>> <mailto:andrewponomarenko@yandex.ru>> 写道:
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> I have released a new version of the hardware probe tool — HW
> >>>>> Probe 1.0, that supports Gentoo and some other popular Linux
> >>>>> distributions. The "probe" is a snapshot of the hardware state
> >>>>> including a list of devices on board and system logs. The primary
> >>>>> purpose of the tool is to share the probe of the computer with
> >>>>> developers or other users for the collaborative debugging of
> >>>>> hardware problems on it.
> >>>>>
> >>>>> All probes are uploaded to the central database at
> >>>>> http://linux-hardware.org/ that holds probed information in a
>
> > please
>
> >>>>> structured form. You can find, for example, in which computer
> >>>>> models is presented some device, what driver was used and how it
> >>>>> was configured. You can check for failures in logs related to a
> >>>>> problem device and so on.
> >>>>>
> >>>>> The source code of the tool is available here:
>
> > stop
>
> >>>>> https://github.com/linuxhw/hw-probe
> >>>>>
> >>>>> Thank you.
> >>>>>  
> If nobody's already started doing the work, one could file a bug on
> our tracker and request an ebuild to be written. Or one could read the
> devmanual and put one together. If someone is interested in
>
> > replying
>
> maintaining that ebuild, one of our proxy-maintainers may be
> interested in helping. Check it out some time. :)
>
> https://bugs.gentoo.org
> https://devmanual.gentoo.org
>
>
>>>  > > in random positions? >

No need for trolling. :P

I like this idea. Having a way to check what drivers were used on a
certain make/model will be helpful for me in the future.

[Attachment #3 (text/html)]

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 02/09/2016 07:01 AM, Michał Górny wrote:<br>
    <span style="white-space: pre;">&gt; On Tue, 9 Feb 2016 17:53:09 +0300
&gt; agentsmith <a class="moz-txt-link-rfc2396E" \
href="mailto:igorsavlook@gmail.com">&lt;igorsavlook@gmail.com&gt;</a> wrote: &gt;
&gt;&gt; Cool tool i create ebuild.
&gt;&gt;
&gt;&gt; On 02/09/2016 05:47 PM, Daniel Campbell wrote:</span><br>
    <blockquote type="cite"><br>
      &gt; Could<br>
      <br>
      On 02/09/2016 05:55 AM, Urbain YANG wrote:  <br>
      &gt;&gt;&gt;&gt; Thank you very much!<br>
      &gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt; And wish it will be merged into Portage soon.<br>
      &gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt; Urbain YANG <a class="moz-txt-link-abbreviated" \
                href="mailto:urbain.yang@qq.com">urbain.yang@qq.com</a>
      <a class="moz-txt-link-rfc2396E" \
href="mailto:urbain.yang@qq.com">&lt;mailto:urbain.yang@qq.com&gt;</a><br>  \
&gt;&gt;&gt;&gt;<br>  &gt;&gt;&gt;&gt;<br>
      <br>
      &gt; you<br>
      <br>
      &gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt;  <br>
      &gt;&gt;&gt;&gt;&gt; 在 2016年2月9日,下午9:33,Ponomarenko Andrey<br>
      &gt;&gt;&gt;&gt;&gt; &lt;<a class="moz-txt-link-abbreviated" \
href="mailto:andrewponomarenko@yandex.ru">andrewponomarenko@yandex.ru</a><br>  \
                &gt;&gt;&gt;&gt;&gt;
      <a class="moz-txt-link-rfc2396E" \
href="mailto:andrewponomarenko@yandex.ru">&lt;mailto:andrewponomarenko@yandex.ru&gt;</a>&gt; \
写道:<br>  &gt;&gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt;&gt; Hello,<br>
      &gt;&gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt;&gt; I have released a new version of the hardware
      probe tool — HW<br>
      &gt;&gt;&gt;&gt;&gt; Probe 1.0, that supports Gentoo and some
      other popular Linux<br>
      &gt;&gt;&gt;&gt;&gt; distributions. The "probe" is a snapshot of
      the hardware state<br>
      &gt;&gt;&gt;&gt;&gt; including a list of devices on board and
      system logs. The primary<br>
      &gt;&gt;&gt;&gt;&gt; purpose of the tool is to share the probe of
      the computer with<br>
      &gt;&gt;&gt;&gt;&gt; developers or other users for the
      collaborative debugging of<br>
      &gt;&gt;&gt;&gt;&gt; hardware problems on it.<br>
      &gt;&gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt;&gt; All probes are uploaded to the central
      database at<br>
      &gt;&gt;&gt;&gt;&gt; <a class="moz-txt-link-freetext" \
href="http://linux-hardware.org/">http://linux-hardware.org/</a> that holds probed  \
information in a<br>  <br>
      &gt; please<br>
      <br>
      &gt;&gt;&gt;&gt;&gt; structured form. You can find, for example,
      in which computer<br>
      &gt;&gt;&gt;&gt;&gt; models is presented some device, what driver
      was used and how it<br>
      &gt;&gt;&gt;&gt;&gt; was configured. You can check for failures in
      logs related to a<br>
      &gt;&gt;&gt;&gt;&gt; problem device and so on.<br>
      &gt;&gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt;&gt; The source code of the tool is available
      here:<br>
      <br>
      &gt; stop<br>
      <br>
      &gt;&gt;&gt;&gt;&gt; <a class="moz-txt-link-freetext" \
href="https://github.com/linuxhw/hw-probe">https://github.com/linuxhw/hw-probe</a><br>
  &gt;&gt;&gt;&gt;&gt;<br>
      &gt;&gt;&gt;&gt;&gt; Thank you.<br>
      &gt;&gt;&gt;&gt;&gt;  <br>
      If nobody's already started doing the work, one could file a bug
      on<br>
      our tracker and request an ebuild to be written. Or one could read
      the<br>
      devmanual and put one together. If someone is interested in<br>
      <br>
      &gt; replying<br>
      <br>
      maintaining that ebuild, one of our proxy-maintainers may be<br>
      interested in helping. Check it out some time. :)<br>
      <br>
      <a class="moz-txt-link-freetext" \
                href="https://bugs.gentoo.org">https://bugs.gentoo.org</a><br>
      <a class="moz-txt-link-freetext" \
href="https://devmanual.gentoo.org">https://devmanual.gentoo.org</a><br>  <br>
      <br>
    </blockquote>
    <span style="white-space: pre;">&gt;&gt;&gt;  
&gt;
&gt; in random positions?
&gt;</span><br>
    <br>
    No need for trolling. :P<br>
    <br>
    I like this idea. Having a way to check what drivers were used on a
    certain make/model will be helpful for me in the future.<br>
  </body>
</html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic