For those who might be interested ...
2016/01/23 9:27 "Joel Rees" :
>
> On Sat, Jan 23, 2016 at 7:15 AM, jdd wrote:
> > Le 22/01/2016 17:34, Alberto Salvia Novella a écrit :
> >>
> >> libre hardware.
> >
> > that's far from new
> >
> > https://en.wikipedia.org/wiki/Open-source_hardware
> >
> > ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jan 23, 2016 at 11:19:35PM -0500, Stefan Monnier wrote:
> > * OpenRISC [3]
> > 32 bit (these days 64 bit). LGPL. There are a few FPGA based
> > implementations and some specialist "real silicon" implementations,
> > AFAIK one on board of
> * OpenRISC [3]
> 32 bit (these days 64 bit). LGPL. There are a few FPGA based
> implementations and some specialist "real silicon" implementations,
> AFAIK one on board of ISS. No idea whether one can buy "real
> silicon" (at least as mere mortal).
You definitely can. At least in a roun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jan 22, 2016 at 11:15:19PM +0100, jdd wrote:
> Le 22/01/2016 17:34, Alberto Salvia Novella a écrit :
> >libre hardware.
> that's far from new
>
> https://en.wikipedia.org/wiki/Open-source_hardware
>
> http://www.gnu.org/philosophy/free-hardwa
On Sat, Jan 23, 2016 at 7:15 AM, jdd wrote:
> Le 22/01/2016 17:34, Alberto Salvia Novella a écrit :
>>
>> libre hardware.
>
> that's far from new
>
> https://en.wikipedia.org/wiki/Open-source_hardware
>
> http://www.gnu.org/philosophy/free-hardware-designs.en.html
>
> I remember efforts done to ha
Le 22/01/2016 17:34, Alberto Salvia Novella a écrit :
libre hardware.
that's far from new
https://en.wikipedia.org/wiki/Open-source_hardware
http://www.gnu.org/philosophy/free-hardware-designs.en.html
I remember efforts done to have free cpu, but I don't think significant
result have been ac
Just to clarify my participation in this thread --
On Sat, Jan 23, 2016 at 1:34 AM, Alberto Salvia Novella
wrote:
> Joel Rees:
>>
>> "Modern" CPUs have plenty of spare register space, most of it
>> undocumented. Register space can be used to record something of state,
>> allowing instruction stre
Joel Rees:
"Modern" CPUs have plenty of spare register space, most of it
undocumented. Register space can be used to record something of state,
allowing instruction streams to be self-parsing.
Anyway I think this falls mostly in the hardware side. I liked microcode
to be libre too, but I'm pos
2016/01/21 2:33 "Alberto Salvia Novella" :
>
> Joel Rees:
>
>> It supports neither your peculiar assertion that microcode is not
>> executable nor your equally peculiar assertion that microcode is not
>> and has not been a cause for concern.
>
>
> Polynomial (http://tinyurl.com/hdtpa7g):
You know,
Joel Rees:
It supports neither your peculiar assertion that microcode is not
executable nor your equally peculiar assertion that microcode is not
and has not been a cause for concern.
Polynomial (http://tinyurl.com/hdtpa7g):
> Let's assume for a moment that you could overwrite microcode in a
>
On Wed, Jan 20, 2016 at 12:55 AM, Alberto Salvia Novella
wrote:
> Joel Rees:
>>
>> Just for the record, if microcode can play with the CPU internal
>> system state, say, the bits that specify whether the CPU is in
>> supervisor or user state, there's not much to stop, for instance, a
>> microcode
On Wed, Jan 20, 2016 at 12:59 AM, Anders Andersson wrote:
>>> Just for the record, if microcode can play with the CPU internal
>>> system state, say, the bits that specify whether the CPU is in
>>> supervisor or user state, there's not much to stop, for instance, a
>>> microcode update from provid
>> Just for the record, if microcode can play with the CPU internal
>> system state, say, the bits that specify whether the CPU is in
>> supervisor or user state, there's not much to stop, for instance, a
>> microcode update from providing an undocumented trap to a hidden
>> routine in the BIOS tha
Joel Rees:
Just for the record, if microcode can play with the CPU internal
system state, say, the bits that specify whether the CPU is in
supervisor or user state, there's not much to stop, for instance, a
microcode update from providing an undocumented trap to a hidden
routine in the BIOS that
2016/01/16 1:16 "Alberto Salvia Novella" :
>
> [...]
>
> Firmware is a common concern because it can be overwritten by malware, have
> malicious functionalities, or have back-doors.
>
> That has never been the case with microcode. It just declares the instruction
> set, but is not an executable.
Zlatan Todoric:
> Now you are defending them why they have closed source things that we
> need if we want to properly use their hardware?
What I am saying is microcode is more on the hardware side.
Moreover what I am interested in is to set a tendency, rather than on
things to change overnight.
On 01/15/2016 04:35 PM, Alberto Salvia Novella wrote:
> Zlatan Todoric:
>> Why just not open source it an be done with it.
>
> Because they need to support old machines that require an unchanged kernel.
>
>
> Zlatan Todoric:
>> It currently needs closed source firmware to run 3D.
>
> Not firm
Zlatan Todoric:
> Why just not open source it an be done with it.
Because they need to support old machines that require an unchanged kernel.
Zlatan Todoric:
> It currently needs closed source firmware to run 3D.
Not firmware, but microcode. It is just how the instruction set is
handled in th
Removing debian-devel@ from CC (not relevant list for this discussion)
On 01/15/2016 03:05 PM, Stefan Monnier wrote:
>>> So I think it is very important that we support AMD right now on what we
>>> can, and ask manufacturers to include AMD graphics in those products.
>> You do realize that AMD gra
Dropping debian-devel@ from CC (not relevant for discussion, someone
should do the same checking for others)
On 01/15/2016 10:57 AM, shawn wilson wrote:
> On Jan 14, 2016 5:11 PM, "Zlatan Todoric" wrote:
>>
>>
>>
>> On 01/14/2016 09:11 PM, Alberto Salvia Novella wrote:
>>> Nearly all compact Linu
Dropping debian-devel@ from CC (not relevant for discussion, don't know
for Ubuntu ones)
On 01/15/2016 02:28 AM, Michael Haney wrote:
> On Thu, Jan 14, 2016 at 4:10 PM, Zlatan Todoric wrote:
>
>>
>>
>> On 01/14/2016 09:11 PM, Alberto Salvia Novella wrote:
>>> Nearly all compact Linux computers f
On Fri, 2016-01-15 at 04:57 -0500, shawn wilson wrote:
>
> On Jan 14, 2016 5:11 PM, "Zlatan Todoric" wrote:
>
> > > So I think it is very important that we support AMD right now on what we
> > > can, and ask manufacturers to include AMD graphics in those products.
> > >
> >
> > You do realize th
On Jan 14, 2016 5:11 PM, "Zlatan Todoric" wrote:
>
>
>
> On 01/14/2016 09:11 PM, Alberto Salvia Novella wrote:
> > Nearly all compact Linux computers feasible for gaming are sold
> > exclusively using NVIDIA graphics, and that company is hostile to libre
> > software.
> >
> > So I think it is very
On Thu, Jan 14, 2016 at 2:11 PM, Alberto Salvia Novella <
es204904...@gmail.com> wrote:
> Nearly all compact Linux computers feasible for gaming are sold
> exclusively using NVIDIA graphics, and that company is hostile to libre
> software.
>
> So I think it is very important that we support AMD ri
On Thu, Jan 14, 2016 at 4:10 PM, Zlatan Todoric wrote:
>
>
> On 01/14/2016 09:11 PM, Alberto Salvia Novella wrote:
> > Nearly all compact Linux computers feasible for gaming are sold
> > exclusively using NVIDIA graphics, and that company is hostile to libre
> > software.
> >
> > So I think it is
On 01/14/2016 05:10 PM, Zlatan Todoric wrote:
On 01/14/2016 09:11 PM, Alberto Salvia Novella wrote:
Nearly all compact Linux computers feasible for gaming are sold
exclusively using NVIDIA graphics, and that company is hostile to libre
software.
So I think it is very important that we support
On 01/14/2016 09:11 PM, Alberto Salvia Novella wrote:
> Nearly all compact Linux computers feasible for gaming are sold
> exclusively using NVIDIA graphics, and that company is hostile to libre
> software.
>
> So I think it is very important that we support AMD right now on what we
> can, and as
Alberto Salvia Novella wrote:
> Nearly all compact Linux computers feasible for gaming are sold
> exclusively using NVIDIA graphics, and that company is hostile to libre
> software.
>
> So I think it is very important that we support AMD right now on what we
> can, and ask manufacturers to includ
Nearly all compact Linux computers feasible for gaming are sold
exclusively using NVIDIA graphics, and that company is hostile to libre
software.
So I think it is very important that we support AMD right now on what we
can, and ask manufacturers to include AMD graphics in those products.
Bec
29 matches
Mail list logo
