| 1 |
On 02/09/2016 07:01 AM, Michał Górny wrote: |
| 2 |
> On Tue, 9 Feb 2016 17:53:09 +0300 > agentsmith <igorsavlook@×××××.com> wrote: > >> Cool tool i create |
| 3 |
ebuild. >> >> On 02/09/2016 05:47 PM, Daniel Campbell wrote: |
| 4 |
> |
| 5 |
> > Could |
| 6 |
> |
| 7 |
> On 02/09/2016 05:55 AM, Urbain YANG wrote: |
| 8 |
> >>>> Thank you very much! |
| 9 |
> >>>> |
| 10 |
> >>>> And wish it will be merged into Portage soon. |
| 11 |
> >>>> |
| 12 |
> >>>> |
| 13 |
> >>>> Urbain YANG urbain.yang@××.com <mailto:urbain.yang@××.com> |
| 14 |
> >>>> |
| 15 |
> >>>> |
| 16 |
> |
| 17 |
> > you |
| 18 |
> |
| 19 |
> >>>> |
| 20 |
> >>>> |
| 21 |
> >>>>> 在 2016年2月9日，下午9:33，Ponomarenko Andrey |
| 22 |
> >>>>> <andrewponomarenko@××××××.ru |
| 23 |
> >>>>> <mailto:andrewponomarenko@××××××.ru>> 写道： |
| 24 |
> >>>>> |
| 25 |
> >>>>> Hello, |
| 26 |
> >>>>> |
| 27 |
> >>>>> I have released a new version of the hardware probe tool — HW |
| 28 |
> >>>>> Probe 1.0, that supports Gentoo and some other popular Linux |
| 29 |
> >>>>> distributions. The "probe" is a snapshot of the hardware state |
| 30 |
> >>>>> including a list of devices on board and system logs. The primary |
| 31 |
> >>>>> purpose of the tool is to share the probe of the computer with |
| 32 |
> >>>>> developers or other users for the collaborative debugging of |
| 33 |
> >>>>> hardware problems on it. |
| 34 |
> >>>>> |
| 35 |
> >>>>> All probes are uploaded to the central database at |
| 36 |
> >>>>> http://linux-hardware.org/ that holds probed information in a |
| 37 |
> |
| 38 |
> > please |
| 39 |
> |
| 40 |
> >>>>> structured form. You can find, for example, in which computer |
| 41 |
> >>>>> models is presented some device, what driver was used and how it |
| 42 |
> >>>>> was configured. You can check for failures in logs related to a |
| 43 |
> >>>>> problem device and so on. |
| 44 |
> >>>>> |
| 45 |
> >>>>> The source code of the tool is available here: |
| 46 |
> |
| 47 |
> > stop |
| 48 |
> |
| 49 |
> >>>>> https://github.com/linuxhw/hw-probe |
| 50 |
> >>>>> |
| 51 |
> >>>>> Thank you. |
| 52 |
> >>>>> |
| 53 |
> If nobody's already started doing the work, one could file a bug on |
| 54 |
> our tracker and request an ebuild to be written. Or one could read the |
| 55 |
> devmanual and put one together. If someone is interested in |
| 56 |
> |
| 57 |
> > replying |
| 58 |
> |
| 59 |
> maintaining that ebuild, one of our proxy-maintainers may be |
| 60 |
> interested in helping. Check it out some time. :) |
| 61 |
> |
| 62 |
> https://bugs.gentoo.org |
| 63 |
> https://devmanual.gentoo.org |
| 64 |
> |
| 65 |
> |
| 66 |
>>> > > in random positions? > |
| 67 |
|
| 68 |
No need for trolling. :P |
| 69 |
|
| 70 |
I like this idea. Having a way to check what drivers were used on a |
| 71 |
certain make/model will be helpful for me in the future. |
Archives