[FSFLA] h-node hardware

[willi uebelherr]

Dear Quiliro,

i know, that you have no experience in hardware design and construction, 
But i know, you are a very open and intelligent boy and if you start, 
you will create in short time the deep understanding.

If we check, can we use a "free-only" software system for our hardware 
system, small or big, we are oriented to the chips. The family and the 
specific members with specific environments.

Independent of PCI or any other form of memory mapping, the actors are 
the installed chips. On the way of identification of our existing 
hardware system we can use tools like "lspci" or "lsusb" or any other, 
depend what software system is running.

Then the task is starting to find the solution for this chips in the 
documentation of free GNU/Linux systems. And it is not enough to say, 
yes, it works. We have to know, how it works.

If we go with this information and information requests to h-node, i 
will say, it is a terrible environment. Maybe, some is helpful. But 
better is to use a search machine to find "linux drivers" for this chip 
and the existing experience with this drivers.

Maybe, it is not helpful in general to create such a restricted page 
like h-node. More important is to use the time to create a documentation 
base for the different chip drivers, her benchmarks and critical 
reflections.

many greetings, willi


Am 26/5/2017 um 17:39 schrieb Quiliro:
> El Fri, 26 May 2017 16:31:43 -0400
> willi uebelherr <willi.uebelherr at riseup.net> escribió:
> 
>> Based on specific chips, we can create a link-net between
>> chip/cards/systems in both direction. Then the user or interested people
>> can check.
> 
> lspci shows the chips. h-node shows lspci.
> _______________________________________________
> Discusion mailing list
> Discusion at fsfla.org
> http://www.fsfla.org/cgi-bin/mailman/listinfo/discusion
>